-
Notifications
You must be signed in to change notification settings - Fork 31
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
Time to provision? #4
Comments
Hi! Thanks for the issue! Unfortunately, sometimes the install script might get stuck downloading the CoreOS image file. From my experience, it should take no more than 15 minutes. If it takes longer, try restarting the script for now and the script will try to reinstall again. Thanks for filing the issue! I've been experiencing this issue intermittently as well, might be due to the CoreOS install script curling with no timeout, and I'll try to investigate it when I find time. Thanks for raising this up! :) |
Sorry I just realized it's stuck in creating disk from stackscript, which I've not encountered before. Could I get the parameters that you passed into the script that might replicate this error? (I.e. data center, plans) . is it always stuck at that stage? |
Thank you for the quick response! I just checked the instance I left running earlier, and it's still spinning on the same step that it has stopped at each time for me. Looks like it has been about 5.5 hours! Here is the relevant info from my
|
I tried it a couple more times with different settings, and each combination stayed spinning on the same step. I tried creating them in the Fremont, CA datacenter ( |
Sorry I just tried Newark, NJ, and it seems to be booting. Could I ask what OS you are running this script on? I'm sorry I'm not sure what really happened so I can't really offer much help at this point, but if you'd like could you run You can also try filing a Linode support ticket to verify that it is not a Linode infra issue. Thanks, and sorry for the trouble! |
Thank you for the update! I'm running it on an up-to-date install of Arch Linux. I'll try it on some other distros to see if that helps and update this issue with any findings. |
Ah im sorry, it might have failed at some point because I was placing |
I just ran it in an Arch Linux VM and im facing the same issue, I'll debug it further and let you know once its fixed :) |
I found a bug with the I made some notes on how to get the dependencies set up in Arch Linux, and I'll paste it here if its helpful to you :) # Run Arch Linux in Docker
docker run --tty --interactive --rm hoverbear/archlinux /bin/bash
# Update dependencies
pacman -Syu
pacman --noconfirm -S apache jq git base-devel openssh bc
# Add new user
useradd -m -s /bin/bash USERNAME
passwd USERNAME
su - USERNAME
# Install kubectl
git clone https://aur.archlinux.org/kubectl-bin.git
cd kubectl-bin
makepkg -s
exit
#As root
pacman -U /home/USERNAME/kubectl-bin/kubectl-bin-*.pkg.tar.xz
#Run kube-linode
su - USERNAME
#To install
curl -s https://raw.githubusercontent.com/kahkhang/kube-linode/master/install.sh | bash
## Run kube-linode
~/.kube-linode/kube-linode.sh
tput cnorm
stty sane |
Fantastic! It got past the "Disk Create From StackScript" stage! Thank you thank you! This is exactly why OSX drives me nuts--it gives you the illusion that you're basically working with Linux under the hood...until you run into a situation like this. The behavior of most standard BSD commands is generally identical to their GNU counterparts, but you occasionally run into these subtle difference that break things in weird ways. /rant Anyway, thank you for taking the time to figure this out! It looks like the script is happily moving along now! |
Thanks @codekoala for the update! Yep I haven't been careful enough in ensuring BSD/GNU compatibility, will keep that in mind from now onwards :) |
Hi, this project looks fabulous. Thank you for putting it together!
I tried to use it a couple times today, but I feel like it's a bit stuck. Do you have an estimate for about how long it should take to provision each linode? I let it run twice, each time for over an hour, with no end in sight simply setting up the master node.
I'll leave it running a bit longer this time just to see if I'm too impatient.
The text was updated successfully, but these errors were encountered: