-
Notifications
You must be signed in to change notification settings - Fork 153
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
Deploying rke cluster fails on provider version 1.3.2 #355
Comments
|
|
Aransh
changed the title
deploying rke cluster on provider version 1.3.2
deploying rke cluster fails on provider version 1.3.2
Jul 31, 2022
Update - this is still happening with version 1.3.3 |
facing same issue - do we have a solution yet ? |
Same issue here on provider version 1.3.4 using AWS EC2s. |
a-blender
changed the title
deploying rke cluster fails on provider version 1.3.2
Deploying rke cluster fails on provider version 1.3.2
Oct 30, 2023
@a-blender posted this over a year ago 😅 No longer working at where this was a problem, maybe @johnhpatton or @richiesebastian can assist? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am unable to deploy an rke cluster using version 1.3.2 of the provider (with either k8s v1.23.6-rancher1-1 or v1.21.7-rancher1-1).
Downgrading to provider version 1.3.1 works (but of course, means k8s 1.23 is not supported).
The main error I'm receiving is 'Failed running cluster err:[ "master-ip-address" not found]'
Again, the same exact configuration works just fine with provider version 1.3.1, so I doubt it's an infrastructure issue.
Also, I've been able to reproduce the issue on version 1.3.2 10 out of 10 times, while on 1.3.1 (and older versions) it worked every time for months.
Commenting the full error log (as it's longer than github's limit)
The text was updated successfully, but these errors were encountered: