Use different foremanctl versions when testing upgrades#586
Merged
Conversation
evgeni
force-pushed
the
upgrade-differently
branch
from
c17aa48 to
07c105a
Compare
Member
Author
archanaserver
approved these changes
Jun 23, 2026
arvind4501
approved these changes
Jun 23, 2026
arvind4501
left a comment
arvind4501
left a comment
Contributor
There was a problem hiding this comment.
Impressive, i now can foresee upgrade_from being extended to 3.y.stable and so on thanks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why are you introducing these changes? (Problem description, related links)
Instead of testing different container images using the same foremanctl version, actually deploy an older foremanctl version (and the images it is configured for), then upgrade to the "latest"
What are the changes introduced in this pull request?
2.y-stablebranch, use that for the initial deployment, then switch to the PR/main branchHow to test this pull request
Steps to reproduce:
Checklist