-
Notifications
You must be signed in to change notification settings - Fork 75
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
tests: give jammy->noble upgrade its own test #3313
Conversation
PR ChecklistHow to use this checklistHow to use this checklistPR AuthorFor each section, check a box when it is true. PR ReviewerCheck that the PR checklist action did not fail. Bug ReferencesNone. Confirm
How to properly reference fixed bugs
Test UpdatesUnit Tests
Integration Tests
Documentation
Does this PR require review from someone outside the core ubuntu-pro-client team?
|
These tests rely on a systemd service running, either ua-timer.service or esm-cache.service, but they cannot run on bionic wsl without systemd.
b465c81
to
376f7f9
Compare
@lucasmoura I added a comment and also removed some bionic wsl tests in accordance with our discussion a while back (and also bumped cloudlib - that was necessary for azure noble pro) |
Why is this needed?
This PR solves all of our problems because...
jammy -> noble needs special treatment now that do-release-upgrade disables -proposed. We need a special step to ensure that the package is actually upgraded to the noble version. We also need to mask the apparmored services so that they don't cause denials during the upgrade to the noble version.
Test Steps
Run the new test