-
Notifications
You must be signed in to change notification settings - Fork 34
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
Image refresh for fedora-rawhide-boot #4551
Image refresh for fedora-rawhide-boot #4551
Conversation
image-refresh fedora-rawhide-boot done: https://github.com/cockpit-project/bots/commits/image-refresh-fedora-rawhide-boot-20230321-100623 |
a0d8518
to
479c2fc
Compare
This will likely fail due to new pykickstart commands not being wired in in anaconda, which would be resolved in rhinstaller/anaconda#4561. No idea how fast this would get here, though... |
lol a deadlock :D |
Nope it is a different issue:
|
@jkonecny12 @VladimirSlavik this fails exactly the same way that it failed on rhinstaller/anaconda#4624 where I see that it was merged with red tests. |
Sorry, but the rest of our tests were red before merging that, so it was picking one of the two. The "pick one" situation needs more discussion, I think. |
if I get a bit better understanding on why the tests were failing in the first place, without the PR which broke the webui tests, I might be able to help improve the workflow. Is pykickstart updates the problem?
So the pykickstart PR broke the webui part in a way that you understand? @jkonecny12 @VladimirSlavik Because to me it's not clear still why webui broke (which deterministically did according to tests) with rhinstaller/anaconda#4624 |
It seems during boot we are not able to download updates image. Not sure what happens there but I'm starting to blame "Rawhide issues"... |
Yes. In a nutshell, anaconda infra uses nightly pykickstart builds, while cockpit tests take it from the official image where it needs to get from a finished tagged release, build, and propagation to mirrors. This helps fast iteration, which in turn helps the actual import and version mismatches. Whatever kickstart merges, the next day we can merge the anaconda part and all works again.
Retroactively, yes, it's pretty clear. The changes I merged required a newer version of pykickstart, which was already tagged so available for our CI, but wasn't in the (older) image that cockpit tests used. Also, the pykickstart version that we need is two versions ahead of what was in the image, so the chance it propagated far enough to be picked up here is lower. |
Is this https://bodhi.fedoraproject.org/updates/FEDORA-2023-eecd218040 the pykickstart version that you want to have in this image in order for the tests to be fixed? |
Yup, the 47 one. |
I just booted from the ISO from #4551 how can I check the pykickstart version? |
@KKoukiou you can do that by reading |
But I already verified that the new image is what we are looking for but for some reason it seems that Anaconda is not able to apply updates-image. Not sure why... |
@KKoukiou normally |
thanks! So i just checked and the pykickstart is the exact same version as you expect. |
The issue was at the end again on my side. Fixed and made improvement to avoid that again in the future here: rhinstaller/anaconda@d7070a4 Testing what really happens now. |
I'm working on more stable fix but we merged this rhinstaller/anaconda#4633 so the result should be green now. |
Needs pixel tests updates because new fonts are shipped - to be done shortly by @jkonecny12 |
PR created: rhinstaller/anaconda#4634 |
Image refresh for fedora-rawhide-boot
This needs work on the anaconda side.