-
Notifications
You must be signed in to change notification settings - Fork 35
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
images: Move ubuntu-stable to noble devel series #6048
Conversation
openssh install is broken. Need to report to launchpad (didn't find it quickly), and block. |
108f9ef
to
b0b951a
Compare
b0b951a
to
dacd919
Compare
image-refresh ubuntu-stable done: https://github.com/cockpit-project/bots/commits/image-refresh-ubuntu-stable-20240311-074439 |
machines failures: Most are due to a single AppArmor denial:
This wasn't reported yet, so I sent https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2056739 . The other failures are because ubuntu-stable now supports external snapshots. I'll think about how to adjust the tests to work without a lockstep change. |
In cockpit-project/bots#6048 we are moving the "ubuntu-stable" image from 23.04 to 24.04 LTS. Until that lands, our tests need to get along with both releases to avoid a lockstep PR. Therefore, temporarily introduce a dynamic runtime check which release we are running on, and thus whether it supports external snapshots. Once that bots PR lands, we can re-simplify this to a static name condition again.
In cockpit-project/bots#6048 we are moving the "ubuntu-stable" image from 23.04 to 24.04 LTS. Until that lands, our tests need to get along with both releases to avoid a lockstep PR. Therefore, temporarily introduce a dynamic runtime check which release we are running on, and thus whether it supports external snapshots. Once that bots PR lands, we can re-simplify this to a static name condition again.
Cockpit fails very often on
which is very similar to https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2056739. Filed as https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2056747 Others are known naughties. This leaves just two specific failures:
|
77e2f88
to
b465e9b
Compare
The current devel series will become 24.04 LTS, thus a major/important release again. Let's avoid repeating a regression catastrophe like 23.10 mantic, and start testing on it early, so that we have a chance to fix up everything by the final release. Disable -proposed for noble, as that has all the broken bits. Add message filters for AppArmor regressions, and copy naughties which now apply to 24.04.
Known issue cockpit-project#6064 Downstream report: https://launchpad.net/bugs/2056768
b465e9b
to
a661211
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
The current devel series will become 24.04 LTS, thus a major/important release again. Let's avoid repeating a regression catastrophe like 23.10 mantic, and start testing on it early, so that we have a chance to fix up everything by the final release.
I created a calendar reminder for me on Apr 25 to revert the hack and enable -proposed.