-
Notifications
You must be signed in to change notification settings - Fork 72
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
Bump Rancher to v2.8.1 and RKE2 to v1.26.12+rke2r1 (backport #605) #646
Conversation
Signed-off-by: PoAn Yang <poan.yang@suse.com>
Signed-off-by: PoAn Yang <poan.yang@suse.com>
bfaebf1
to
503002a
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.
LGTM!
@FrankYang0529 should we consider also use v1.26.12 or v1.26.13 (currently on rc3)? |
I tested the upgrade from v1.2.1, after the upgrade the system-upgrade-controller is gone (local-managed-system-upgrade-controller ManagedChart is gone). Rancher keep complaining:
I did changed my local RKE2 version to |
@bk201 i assume the error is because |
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.
lgtm. we need the PR harvester/harvester#5103 to be merged and backported to v1.2 branch for the cluster.provisioning object to be successfully reconciled.
Signed-off-by: PoAn Yang <poan.yang@suse.com>
I update v1.26.12. Thanks. |
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.
LGTM, tested with harvester/harvester#5057
upgrade path from v1.2.1 -> v1.2-head (this PR) -> master-head
verified the VM can be migrated (w/o vlan due to harvester/harvester#5076)
And all basic operations work well.
This is an automatic backport of pull request #605 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com