-
Notifications
You must be signed in to change notification settings - Fork 54
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
Improved upgrade test #1960
Improved upgrade test #1960
Conversation
Signed-off-by: Fredrik Lönnegren <[email protected]>
ee9cdd0
to
a5e4e92
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1960 +/- ##
=======================================
Coverage 72.04% 72.04%
=======================================
Files 72 72
Lines 8019 8019
=======================================
Hits 5777 5777
Misses 1779 1779
Partials 463 463 ☔ View full report in Codecov by Sentry. |
This commit uses podman to run the latest version of the elemental-cli to run the update command. Signed-off-by: Fredrik Lönnegren <[email protected]>
Signed-off-by: Fredrik Lönnegren <[email protected]>
6e388da
to
e7d6926
Compare
Signed-off-by: Fredrik Lönnegren <[email protected]>
Got a green upgrade run at https://github.com/rancher/elemental-toolkit/actions/runs/7917180349/job/21613080610?pr=1960 going back to |
e7d6926
to
80f862f
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.
I am a bit lost with these changes... Shouldn't it be a new test, so we test both directions:
- from current head downgrade to a names tag/version
- from a named/tag version upgrade to current head
1 is what we already had, we are missing 2.
I guess this also apply to the recovery tests which in fact is just an upgrade test executed from recovery system.
I can add back the old upgrade test and call it downgrade instead, then we get both tests named correctly 👍 |
Signed-off-by: Fredrik Lönnegren <[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.
Nice! LGTM 👍
The upgrade test will now prepare a VM with an older (v1.1.4) version and then run the upgrade in podman to upgrade to the current PR container.
This will make sure we can upgrade from v1.1.4 to current and also that the correct version of the upgrade command is tested (the new one, not the old installed one).
Fixes #1928