Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

osmet-pack: run coreos-installer in target rootfs #1774

Merged
merged 2 commits into from
Oct 8, 2020

Conversation

jlebon
Copy link
Member

@jlebon jlebon commented Oct 6, 2020

Otherwise, we might get linking issues if the target system has newer
e.g. glibc. We could use bwrap here instead of chroot, but meh this
is easier and the block device itself is read-only anyway.

I was initially trying to get this code to use the qemu image directly,
but we have a bunch of issues there with our systemd services getting
confused by the metal disk containing identical boot and root
partitions (which... we should circle back to eventually).

Closes: #1761

Copy link
Contributor

@darkmuggle darkmuggle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

This seems sane.

jlebon added 2 commits October 6, 2020 17:15
Otherwise, we might get linking issues if the target system has newer
e.g. glibc. We could use `bwrap` here instead of `chroot`, but meh this
is easier and the block device itself is read-only anyway.

I was initially trying to get this code to use the qemu image directly,
but we have a bunch of issues there with our systemd services getting
confused by the metal disk containing identical boot and root
partitions (which... we should circle back to eventually).

Closes: coreos#1761
…l key"

This reverts commit ed6b99b.

We don't need this anymore now that osmet packing uses the rootfs of the
target system.
@jlebon jlebon force-pushed the pr/fcos-qemu-osmet branch from 2812d86 to 7984439 Compare October 6, 2020 21:16
@openshift-ci-robot
Copy link

New changes are detected. LGTM label has been removed.

@jlebon
Copy link
Member Author

jlebon commented Oct 7, 2020

(This one just needs another restamp.)

@darkmuggle
Copy link
Contributor

/lgtm (again)

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: darkmuggle, jlebon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@darkmuggle darkmuggle added the lgtm label Oct 8, 2020
@openshift-merge-robot openshift-merge-robot merged commit 510dbec into coreos:master Oct 8, 2020
jlebon added a commit to jlebon/fedora-coreos-config that referenced this pull request Oct 8, 2020
This reverts commit 8382692.

We don't need this anymore now that coreos-assembler correctly uses the
target rootfs directly to run coreos-installer (see
coreos/coreos-assembler#1774).
dustymabe pushed a commit to coreos/fedora-coreos-config that referenced this pull request Oct 8, 2020
This reverts commit 8382692.

We don't need this anymore now that coreos-assembler correctly uses the
target rootfs directly to run coreos-installer (see
coreos/coreos-assembler#1774).
kelvinfan001 pushed a commit to kelvinfan001/fedora-coreos-config that referenced this pull request Dec 14, 2020
This reverts commit 8382692.

We don't need this anymore now that coreos-assembler correctly uses the
target rootfs directly to run coreos-installer (see
coreos/coreos-assembler#1774).
@jlebon jlebon deleted the pr/fcos-qemu-osmet branch April 22, 2023 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

building next major Fedora content can lead to failure in buildextend-live
4 participants