-
Notifications
You must be signed in to change notification settings - Fork 69
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
Joining cluster fails #17
Comments
It's really hard to troubleshoot this. Sometimes there's 2 out fo 3 master nodes that are working, while the 3rd one does not have a |
For me, I found that the /var/lib/cloud/instance/scripts/00_download.sh file that gets populated needs to be tweaked. The scenario is that awscli already exists and it is failing on the install. [root@ip-10-2-5-28 ~]# /var/lib/cloud/instance/scripts/00_download.sh
Loaded plugins: amazon-id, search-disabled-repos
Package unzip-6.0-21.el7.x86_64 already installed and latest version
Nothing to do
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 33.5M 100 33.5M 0 0 47.0M 0 --:--:-- --:--:-- --:--:-- 47.0M
Found preexisting AWS CLI installation: /usr/local/aws-cli/v2/current. Please rerun install script with --update flag.
[root@ip-10-2-5-28 ~]# echo $?
1 I'll try and figure out how to modify the population of the /var/lib/cloud/instance/scripts/00_download.sh script but if anyone knows already please let me know. :) |
Issues with preexisting awscli installations were resolved via this commit: |
Hi guys,
I'm having an issue running more than a single node control plane as nodes doesn't seem to be joining the cluster, here's the error I am seeing
and if I try to run the script manually afterwords, I do get the following
I am also looking into that right now so I will share more insights unless you guys have any ideas? Not sure if important, but I am not using spot instances.
Thanks!
The text was updated successfully, but these errors were encountered: