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.

Sign up for GitHub

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

Jump to bottom

Running nodeadm init on already inited machine errors out #68

Open

puneetguptanitj opened this issue Oct 29, 2018 · 0 comments

Assignees

Labels

bug

Contributor

puneetguptanitj commented Oct 29, 2018

Take a machine which is already part of a cluster

coreos-puneet-556-10-105-16-89platform9 bin # ./cctl get machine
Machine Information
------- -----------
Machine IP             Creation Timestamp                      Role
10.105.16.89           2018-10-23 07:33:18 +0000 UTC           [Master]
10.105.16.72           2018-10-23 07:34:31 +0000 UTC           [Master]
10.105.16.76           2018-10-23 07:35:35 +0000 UTC           [Node]

Run nodeadm init again on the same machine. It fails trying to create /opt/bin/kubelet as the file is currently being used.

File already exists /var/cache/nodeadm/flannel/v0.10.0/kube-flannel.yml
cp: cannot create regular file '/opt/bin/kubelet': Text file busy
FATA[0019]

The text was updated successfully, but these errors were encountered:

dlipovetsky self-assigned this

dlipovetsky added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment