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.

Sign up for GitHub

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

Jump to bottom

building next major Fedora content can lead to failure in buildextend-live #1761

Closed
dustymabe opened this issue Oct 5, 2020 · 1 comment · Fixed by #1774
Closed

building next major Fedora content can lead to failure in buildextend-live #1761

dustymabe opened this issue Oct 5, 2020 · 1 comment · Fixed by #1774

Comments

@dustymabe
Copy link
Member

In cosa buildextend-live we use the coreos-installer bits from the built artifact. Currently I'm building Fedora 33 using a Fedora 32 based cosa and hitting an issue because a newer glibc is needed:

+ /sysroot/ostree/deploy/fedora-coreos/deploy/cf40be708d3f0751a098ca8c219641e4d3c8e21bd6f24835452c9f8644707f9b.0/usr/bin/coreos-installer osmet pack /dev/disk/by-id/virtio-osmet --description 'Fedora CoreOS 33.20201005.dev.0' --checksum c546d3c34a30f535cb5f3d32cd1d5f0d682a8b99bcb1846459915d344bacc887 --output /srv/tmp/tmp-osmet-pack/osmet.bin
/sysroot/ostree/deploy/fedora-coreos/deploy/cf40be708d3f0751a098ca8c219641e4d3c8e21bd6f24835452c9f8644707f9b.0/usr/bin/coreos-installer: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /sysroot/ostree/deploy/fedora-coreos/deploy/cf40be708d3f0751a098ca8c219641e4d3c8e21bd6f24835452c9f8644707f9b.0/usr/bin/coreos-installer)
Error running command /usr/lib/coreos-assembler/osmet-pack

Perhaps in the future we can figure out a better way to run this so that we don't have to match exactly the Fedora major version in COSA and in the target.
jlebon added a commit to jlebon/coreos-assembler that referenced this issue Oct 5, 2020
@jlebon
buildextend-live: add osmet-pack-with-cosa-coreinst
f5d3637 
This is a temporary hack to unblock the f33 rebase in next.

See coreos#1761 for details.
jlebon added a commit to jlebon/coreos-assembler that referenced this issue Oct 5, 2020
@jlebon
buildextend-live: support osmet-pack-with-cosa-coreinst key in image.…
a70e373 
…yaml

When that key is on, we use the coreos-installer from cosa instead of
the target system. This is a temporary hack to unblock the f33 rebase in
next.

See coreos#1761 for details.
jlebon added a commit to jlebon/coreos-assembler that referenced this issue Oct 5, 2020
@jlebon
buildextend-live: add osmet-pack-with-cosa-coreinst image.yaml key
a43e5af 
When that key is on, we use the coreos-installer from cosa instead of
the target system. This is a temporary hack to unblock the f33 rebase in
next.

See coreos#1761 for details.
@jlebon jlebon mentioned this issue Oct 5, 2020
Merged
jlebon added a commit to jlebon/coreos-assembler that referenced this issue Oct 5, 2020
@jlebon
buildextend-live: add osmet-pack-with-cosa-coreinst image.yaml key
ed6b99b 
When that key is on, we use the coreos-installer from cosa instead of
the target system. This is a temporary hack to unblock the f33 rebase in
next.

See coreos#1761 for details.
openshift-merge-robot pushed a commit that referenced this issue Oct 5, 2020
@jlebon @openshift-merge-robot
buildextend-live: add osmet-pack-with-cosa-coreinst image.yaml key
33fa7e0 
When that key is on, we use the coreos-installer from cosa instead of
the target system. This is a temporary hack to unblock the f33 rebase in
next.

See #1761 for details.
dustymabe added a commit to dustymabe/fedora-coreos-config that referenced this issue Oct 5, 2020
@dustymabe
image.yaml: set osmet-pack-with-cosa-coreinst to true
e735ecc 
For now, temporarily use the coreos-installer from COSA in order
to work around coreos/coreos-assembler#1761
when building F33 based FCOS.
@dustymabe dustymabe mentioned this issue Oct 5, 2020
Merged
dustymabe added a commit to dustymabe/fedora-coreos-config that referenced this issue Oct 5, 2020
@dustymabe
image.yaml: set osmet-pack-with-cosa-coreinst to true
80aea54 
For now, temporarily use the coreos-installer from COSA in order
to work around coreos/coreos-assembler#1761
when building F33 based FCOS.
dustymabe added a commit to coreos/fedora-coreos-config that referenced this issue Oct 6, 2020
@dustymabe
image.yaml: set osmet-pack-with-cosa-coreinst to true
8382692 
For now, temporarily use the coreos-installer from COSA in order
to work around coreos/coreos-assembler#1761
when building F33 based FCOS.
jlebon added a commit to jlebon/coreos-assembler that referenced this issue Oct 6, 2020
@jlebon
osmet-pack: run coreos-installer in target rootfs
b65cf9f 
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
@jlebon jlebon mentioned this issue Oct 6, 2020
Merged
@jlebon
Copy link
Member

jlebon commented Oct 6, 2020

Fix for this in #1774.

jlebon added a commit to jlebon/coreos-assembler that referenced this issue Oct 6, 2020
@jlebon
osmet-pack: run coreos-installer in target rootfs
79d16fc 
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
jlebon added a commit to jlebon/coreos-assembler that referenced this issue Oct 6, 2020
@jlebon
osmet-pack: run coreos-installer in target rootfs
c9fec17 
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
jlebon added a commit to jlebon/coreos-assembler that referenced this issue Oct 6, 2020
@jlebon
osmet-pack: run coreos-installer in target rootfs
e43ea7f 
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
openshift-merge-robot pushed a commit that referenced this issue Oct 8, 2020
@jlebon @openshift-merge-robot
osmet-pack: run coreos-installer in target rootfs
3beedb8 
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
kelvinfan001 pushed a commit to kelvinfan001/fedora-coreos-config that referenced this issue Dec 14, 2020
@dustymabe @kelvinfan001
image.yaml: set osmet-pack-with-cosa-coreinst to true
d9b9976 
For now, temporarily use the coreos-installer from COSA in order
to work around coreos/coreos-assembler#1761
when building F33 based FCOS.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

osmet-pack: run coreos-installer in target rootfs jlebon/coreos-assembler
2 participants
@dustymabe @jlebon