Worker not deployed about kube-linode HOT 11 CLOSED

Is it due to #17? Can have more information regarding your OS version / the terminal screen when the workers are being deployed?

from kube-linode.

Hi, It still happens after #17 fix.

My Info:

ProductName:	Mac OS X
ProductVersion:	10.12.5

Terminal screen:

No error was reported.

from kube-linode.

Can I see the disks/boot configuration of your worker linode? What happens if you delete those 2 worker nodes and run kube-linode again?

from kube-linode.

I set 10GB for coreos partition.
Same thing happen if I delete & recreate 2 workers.

from kube-linode.

Could you click on one the worker nodes in your first screenshot, then screenshot the details of the Linode (i.e. list of disks, list of configurations, jobs)? That will give me more information to diagnose the issue. Thanks!

from kube-linode.

See:

from kube-linode.

Hmm this is strange since the initial portion of the script for the worker node is the same as the master one, and it seems like it is not getting any jobs after the initial configuration, which means some portion of the commands failed silently. Could I ask if you are using the default bash version or some other shell (e.g. zsh)? I'll probably need to add a verbose mode for the script so problems like this can be more easily diagnosed. Thanks for reporting the issue!

from kube-linode.

I use fish shell. As your suggestion, I currently try to run again on zsh. Will keep updating.

from kube-linode.

Ah ok thanks! I'm not sure of the behavior of fish since I've only used this in bash / zsh currently. I highly suspect it might be failing here: https://github.com/kahkhang/kube-linode/blob/master/utilities.sh#L317. Will investigate more, thanks for the information!

from kube-linode.

same issue with zsh. I guess it's not shell-specific issue. It would be great if you can add --verbose option. In the mean time I'll dig further into the source code when I've time. Thanks for the fast response :)

from kube-linode.

Thanks for raising the issue @tuannvm! I think I've found a bug which has been fixed. Please reopen again if the problem is still not solved, or update if it has been solved :)

from kube-linode.