-
Notifications
You must be signed in to change notification settings - Fork 315
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
[BUG] Can't install Harvester cloud provider in Rancher v2.7-head guest cluster configuration page #3506
Comments
Same as an issue 3389. The Harvester cloud provider can not select issue is caused by the version setting check:
The workaround is to change the Harvester server-version setting to v1.1.2. |
@n313893254 doesn't the upstream PR rancher/dashboard#8081 already address the issue? |
@guangbochen This PR is valid for official versions like v1.1.2, but no judgment is made for RC versions that have a suffix. The workaround is to change the Harvester server-version setting to v1.1.2. |
Pre Ready-For-Testing Checklist
|
@n313893254 thanks for the workaround 😄 Validated on:
With the workaround of:
Then import Harvester to Rancher.
|
@irishgordo This problem has been fixed in the rancher 2.7-head, and it does not need to use the workaround method to test. Can you help me use the latest rancher to test it? thank you |
I'll reopen this issue, thank you |
@WuJun2016 - I can help validate with Rancher v2.7-head 😄 and not implementing the previous workaround - I'll work on validating this now |
@WuJun2016 Should I go ahead and close this out 😄 ? |
@irishgordo Yes, you can close the issue. Thank you for your verification. |
You're welcome! Glad I could help! 😄 Thanks again for pre-release comparison logic fix @WuJun2016 ! |
This will be fixed in the upcoming Rancher v2.7.2, as a temp workaround, you can modify the related setting in the Harvester via:
|
Describe the bug
On rancher v2.7-head, in the RKE2 cluster provisioning page, we can't select Harvester cloud provider for the given Kubernetes version of
v1.25.6
,v1.24.10
andv1.23.6
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should be able to select Harvester cloud provider for the given Kubernetes version
Support bundle
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: