-
Notifications
You must be signed in to change notification settings - Fork 2
Anaconda installation failed since centos-bootc-dev stream9.20240216.0
image
#30
Comments
Hmm, I'm not reproducing this in a quick test here. What's the Anaconda version in use? The real failure BTW is above those lines. |
The anaconda version is anaconda-34.25.4.6-1.el9.x86_64.rpm. I had a brief research:
So I suspect the composefs + transient change. |
If you can get the full journal logs, that'd be really helpful. For reference, I tested with this kickstart:
Using You linked to an Anaconda RPM, but presumably you're really testing with an Anaconda PXE/ISO setup from the corresponding compose, right? |
For reference based on the evidence I'd agree, and it seems quite possible that there's a bug here. I consider resolving this issue a blocker for merging CentOS/centos-bootc#356 so let's get to the bottom of it. Also, was this an automated test failure? Can you link the job if so? Also if so, let's ensure that we're gathering full information from Anaconda. |
This is kickstart file the test is using. https://github.com/virt-s1/bootc-workflow-test/blob/main/anaconda.sh#L119
RHEL 9.4 has same issue before until the
Yes. test fetches the compose ID from image and use that compose in test. https://github.com/virt-s1/bootc-workflow-test/blob/0be2d9517772485ddccf3a4a90af20d19b0c5b87/anaconda.sh#L58 |
Yes. it's automation test failure, log is here. Installation does not have issue, but failed at first boot. The vm console log can be found from here. I'll add kernel arguments to access emergency shell from console and get full journal log. |
OK yeah, we need the journal from the target system indeed. Hmm, it'd also help a bit to stash the generated qcow2 as an artifact or so too. I should be able to reproduce this using https://github.com/virt-s1/bootc-workflow-test/tree/main?tab=readme-ov-file#run-centos-stream-test right? |
This command line to run anaconda test. I'm re-producing this issue now. I'll post you updated. |
@cgwalters I think I found the root cause. All the failed tests are all have |
More results:
But the upgrade failure appears again |
Right, yes.
What are we upgrading from and to in this scenario? |
The upgrade image has one more |
I've reproduced the failure...should have been testing upgrades via anaconda. A core problem here is we aren't shipping ostree-grub2 so ostreedev/ostree@c281da8 isn't relevant. |
ostreedev/ostree#3205 should fix this |
The latest quay.io/centos-bootc/centos-bootc-dev:stream9 (sha256:cef521bb29d819325d39491eb91752fc35aa3d196437f06f108409ba5d28b83f) has the changes from that PR, let's see if it fixes things in CI? |
Verified on All anaconda (x86_64) tests passed on CI: virt-s1/bootc-workflow-report#95 |
Since centos-bootc-dev image version
![Screenshot from 2024-02-20 09-43-32](https://private-user-images.githubusercontent.com/672230/306121398-94fdd8e2-7c20-42b5-bed8-a49559159c57.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ0NjI1MzQsIm5iZiI6MTcyNDQ2MjIzNCwicGF0aCI6Ii82NzIyMzAvMzA2MTIxMzk4LTk0ZmRkOGUyLTdjMjAtNDJiNS1iZWQ4LWE0OTU1OTE1OWM1Ny5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODI0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyNFQwMTE3MTRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT02YjdkNWIzMmI4MTk1NGJkYjkxOTZmN2RkZTQ0NmEzNmQ2YzIxZmRiMzExNTZkMmJiNDdmYjFiMWNjYjE0OTA1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.NrxbdPt8pnmzMS7sDHFCabKtvqCPI1NBUCraA7ATTPo)
![Screenshot from 2024-02-20 10-58-19](https://private-user-images.githubusercontent.com/672230/306121418-43117a83-81d1-49c9-b9d4-35d6ee0cfd4a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ0NjI1MzQsIm5iZiI6MTcyNDQ2MjIzNCwicGF0aCI6Ii82NzIyMzAvMzA2MTIxNDE4LTQzMTE3YTgzLTgxZDEtNDljOS1iOWQ0LTM1ZDZlZTBjZmQ0YS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODI0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyNFQwMTE3MTRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yNjFhYmU1NTkyZGI4ZGUxZTMwMjA2MzdkZjg0ZDIyZGJlY2ZkMDhlZDcxYmJlMDg1MDMwNDAzYTJhZGEzNzNlJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.va2CIKWjWkZU7QmXmqtyFrP85e4BgU9AmrDOogmVJQU)
stream9.20240216.0
, all anaconda installation tests failed. The system will enter into emergency mode after reboot from anaconda installation.The issue might be related with PR #27 .
The text was updated successfully, but these errors were encountered: