-
Notifications
You must be signed in to change notification settings - Fork 21
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
CI: Add upgrade tests #869
Conversation
2ad5b7f
to
7995bf1
Compare
Adds two upgrade test jobs: Ubuntu Jammy OVS and Rocky 9 OVN. These jobs reuse the existing aio reusable workflow, which has a new 'upgrade' input parameter. When testing an upgrade, the previous release is first deployed, then the aio is upgraded to the current release before running RefStack tests.
7995bf1
to
4c67cf3
Compare
Is it SMS capacity limits that are motivating just adding two tests? I'm wondering how big of an issue it would be to not cover OVN/OVS on both distributions. We do have customers on OVN Ubuntu for example, so issues could slip through the cracks here. |
Correct - ideally we would cover all cases. There may be an argument for nightly runs covering all combinations, if we can report the results somewhere sensible. |
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.
couple of nits otherwise LGTM
Co-authored-by: Alex-Welsh <[email protected]>
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.
Might be worth an update to release train so it's a required check
Adds two upgrade test jobs: Ubuntu Jammy OVS and Rocky 9 OVN.
These jobs reuse the existing aio reusable workflow, which has a new 'upgrade' input parameter. When testing an upgrade, the previous release is first deployed, then the aio is upgraded to the current release before running RefStack tests.