-
Notifications
You must be signed in to change notification settings - Fork 94
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
bootc install to-existing-root failure tracker #1053
Comments
Can you link to a log file for this job with more information? Like, what are the versions of the host system, bootc, what's in the base image etc.?
Looks like this image is missing a But still though, we should work here obviously...and I don't think this could really be platform-specific; it must have something to do with how the container image is built. Is this reproducible? Can you push the |
Yeah, I was working on this issue yesterday and tried on different platform to see what's different between those platforms. I think I need collect more information for debugging. All those tests are running on the same machine (Fedora 41 VM) and test comes from https://gitlab.com/fedora/bootc/tests/bootc-workflow-test/-/blob/main/os-replace.sh?ref_type=heads script. The base image is NOTE: The test workflow is
|
Note that unless you're using We should definitely track down this bug, because what we're doing here should work but, this will look cleaner using heredocs and it may work around this:
I know we should be updating some of our examples to use heredocs. One thing that has bit me is that the default podman in GitHub actions is too old for it, which is super annoying (ref containers/podman#17362 ) |
Anyways OK I couldn't reproduce this in a quick test...have you reproduced this in an interactive run? Oh hmm...I notice we may have qemu emulation going on in some builds? That might be related. Note also that this issue should be independent of the host version because we're using That said, this type of failure is also likely to occur when doing e.g. a |
Right. |
CS10, bootc 1.1.3 on libvirt has error Log: https://artifacts.osci.redhat.com/testing-farm/ce9e7a5b-9a74-4c2d-a090-539ee208b936/ RHEL 9.6, bootc 1.1.4 all platforms has error Log: https://artifacts.osci.redhat.com/testing-farm/06574185-504b-43d7-a8b3-d65ce35d582e/ |
fedora-bootc:41 and 42 test passed. |
That's...bizarre. How could it only be broken in that way on c10s but not other streams? I have no idea what's going on there.
If strema9 works but 9.6 is failing then in theory there is some skew between the two that should otherwise be the same, so we'll need to chase this. I know others have hit this, but I have no idea why this specific bit again could fail in just one stream but not others. |
Boot openstack VM with package mode and run
podman run --rm --tls-verify=false --privileged --pid=host quay.io/redhat_emp1/bootc-workflow-test:bhpq bootc install to-existing-root
failed.Error:
Same test passed on AWS ec2 instance (both x86_64 and aarch64).
The text was updated successfully, but these errors were encountered: