You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
The following error occurs when I try to convert a cluster node to Edgenode using yurtctl convert edgenode :
[root@masteropenyurt]# _output/bin/yurtctl convert edgenode --edge-nodes node73 --kubeadm-conf-path /usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf --v=5
I0426 16:31:30.35353628855 edgenode.go:174] the server version is valid
I0426 16:31:30.35362728855 util.go:122] get nodename err: failed to read file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf, open /etc/systemd/system/kubelet.service.d/10-kubeadm.conf: no such file or directory
F0426 16:31:30.35364228855 edgenode.go:82] fail to covert the kubernetes node to a yurt node: open /etc/systemd/system/kubelet.service.d/10-kubeadm.conf: no such file or directory
I have specified the value of the --kubeadm-conf-path flag, but according to the log, the default path /etc/systemd/system/kubelet.service.d/10-kubeadm.conf is still used. What you expected to happen:
When user specify the value of the --kubeadm-conf-path flag, the program can use the path that user specify to find information.
How to reproduce it (as minimally and precisely as possible):
when the kubeadm-conf-path is not /etc/systemd/system/kubelet.service.d/10-kubeadm.conf and in the other path, and if you want to execute yurtctl convert edgenode and specify the --kubeadm-conf-path flag's value, this error will appear. For example:
# if 10-kubeadm.conf is not in the default path
$ cat /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
cat: /etc/systemd/system/kubelet.service.d/10-kubeadm.conf: No such file or directory
# And execute the command, the error will appear
$ _output/bin/yurtctl convert edgenode --edge-nodes node73 --kubeadm-conf-path /usr/lib/systemd/system/kubelet.service.d/10-kubeadm.conf --v=5
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
What happened:
The following error occurs when I try to convert a cluster node to Edgenode using
yurtctl convert edgenode
:I have specified the value of the
--kubeadm-conf-path
flag, but according to the log, the default path/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
is still used.What you expected to happen:
When user specify the value of the
--kubeadm-conf-path
flag, the program can use the path that user specify to find information.How to reproduce it (as minimally and precisely as possible):
when the kubeadm-conf-path is not
/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
and in the other path, and if you want to executeyurtctl convert edgenode
and specify the--kubeadm-conf-path
flag's value, this error will appear. For example:Anything else we need to know?:
Environment:
kubectl version
):cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: