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:
When using CentOS (7.7) to provision kubeone cluster, apply steps fails on missing two files on the system (/etc/sysconfig/selinux, /etc/selinux/config):
...
[136.144.48.169] + sudo setenforce 0
[136.144.48.169] setenforce: SELinux is disabled
[136.144.48.169] + true
[136.144.48.169] + sudo sed -i s/SELINUX=enforcing/SELINUX=permissive/g /etc/sysconfig/selinux
[136.144.48.169] sed: can't read /etc/sysconfig/selinux: No such file or directory
ERRO[08:44:19 UTC] failed to install kubeadm: Process exited with status 2 node=136.144.48.169
WARN[08:44:19 UTC] Task failed, error was: at least one of the tasks has encountered an error
...
[136.144.48.169] + sudo sed -i s/SELINUX=enforcing/SELINUX=permissive/g /etc/sysconfig/selinux
[136.144.48.169] + sudo sed -i s/SELINUX=enforcing/SELINUX=permissive/g /etc/selinux/config
[136.144.48.169] sed: can't read /etc/selinux/config: No such file or directory
ERRO[08:49:49 UTC] failed to install kubeadm: Process exited with status 2 node=136.144.48.169
WARN[08:49:49 UTC] Task failed, error was: at least one of the tasks has encountered an error
What is the expected behavior: kubeone apply works smoothly without touching the instances at all, if files does not exist, it may safely continue in this case because selinux is disabled
How to reproduce the issue:
Get the instances with CentOS 7.7, use the static controlPlane setup and run kubeone apply -m kubeone.yaml
What happened:
When using CentOS (7.7) to provision kubeone cluster,
apply
steps fails on missing two files on the system (/etc/sysconfig/selinux
,/etc/selinux/config
):What is the expected behavior:
kubeone apply
works smoothly without touching the instances at all, if files does not exist, it may safely continue in this case because selinux is disabledHow to reproduce the issue:
Get the instances with CentOS 7.7, use the static controlPlane setup and run
kubeone apply -m kubeone.yaml
Anything else we need to know?
Can be workaround by creating empty files on the system:
Information about the environment:
KubeOne version (
kubeone version
):1.3.0-alpha.0
Operating system: CentOS
Provider you're deploying cluster on: Equinix bare-metal
Operating system you're deploying on: CentOS
The text was updated successfully, but these errors were encountered: