#15 atomic install kubernetes-sig-kubelet error code 1
Opened 6 years ago by rares. Modified 6 years ago

I have a CentOS Atomic on bare metal. I started with the 2018-01-09 image and then upgraded. When I install kubernetes-sig-kubelet the installation returns error code 1 but no error message. The service does not work.

# atomic install --system --system-package=no --name kubelet registry.centos.org/centos/kubernetes-sig-kubelet:latest
Extracting to /var/lib/containers/atomic/kubelet.0
Created file /etc/kubernetes/kubelet
Created file /etc/kubernetes/config
systemctl daemon-reload
systemctl enable kubelet

# Notice the error code 1
<1># systemctl -l status kubelet.service 
Failed to get properties: Access denied
<1># systemctl daemon-reexec
# systemctl -l status kubelet.service 
Unit kubelet.service could not be found.
<4>#

I tried the non-sig kubelet package and the result is the same:

# atomic install --system --system-package=no --name kubelet registry.centos.org/centos/kubernetes-kubelet:latest
Extracting to /var/lib/containers/atomic/kubelet.0
Created file /etc/kubernetes/kubelet
Created file /etc/kubernetes/config
systemctl daemon-reload
systemctl enable kubelet

<1>#  systemctl -l status kubelet.service 
Failed to get properties: Access denied
<1># systemctl daemon-reexec
# systemctl -l status kubelet.service 
Unit kubelet.service could not be found.
#

I'm not able to reproduce this. I'm running centos atomic 7.1804.

I started with 7.1803 and upgraded to 7.1804 using atomic host upgrade. After that I ran into the issue.

# atomic host status
State: idle
Deployments:
● centos-atomic-host:centos-atomic-host/7/x86_64/standard
                   Version: 7.1803 (2018-04-03 12:35:38)
                    Commit: cbb9dbf9c8697e9254f481fff8f399d6808cecbed0fa6cc24e659d2f50e05a3e
             PendingCommit: 0d1581533e65756a0822c691cc9ee846bffe4629604bc213b09e175a86c01d6d
            PendingVersion: 7.1804 (2018-05-21 20:57:24)
              GPGSignature: Valid signature by 64E3E7558572B59A319452AAF17E745691BA8335

  centos-atomic-host:centos-atomic-host/7/x86_64/standard
                   Version: 7.1804 (2018-05-21 20:57:24)
                    Commit: 0d1581533e65756a0822c691cc9ee846bffe4629604bc213b09e175a86c01d6d
              GPGSignature: Valid signature by 64E3E7558572B59A319452AAF17E745691BA8335

On the other hand, I did a clean install of 7.1804 and atomic install... works as expected. My guess is that it has something to do with upgrading from 7.1803

I upgraded to the latest and the Kubernetes services are still not installed properly:

# rpm-ostree status
State: idle
Deployments:
● ostree://centos-atomic-host:centos-atomic-host/7/x86_64/standard
                   Version: 7.1805 (2018-06-11 11:03:09)
                    Commit: 6275caab694c56515c57f5e5ef923d999e16e8fb1241992d155ff03cfb528261
              GPGSignature: Valid signature by 64E3E7558572B59A319452AAF17E745691BA8335

  ostree://centos-atomic-host:centos-atomic-host/7/x86_64/standard
                   Version: 7.1803 (2018-04-03 12:35:38)
                    Commit: cbb9dbf9c8697e9254f481fff8f399d6808cecbed0fa6cc24e659d2f50e05a3e
              GPGSignature: Valid signature by 64E3E7558572B59A319452AAF17E745691BA8335
# systemctl -l status kubelet.service kube-proxy.service 
Unit kubelet.service could not be found.
Unit kube-proxy.service could not be found.
# atomic install --system --system-package=no --name kubelet registry.centos.org/centos/kubernetes-sig-kubelet:latest

Extracting to /var/lib/containers/atomic/kubelet.0
File /etc/kubernetes/config already exists
File /etc/kubernetes/kubelet already exists
systemctl daemon-reload
systemctl enable kubelet

<1># 
# atomic install --system --system-package=no --name kube-proxy registry.centos.org/centos/kubernetes-sig-proxy:latest

Extracting to /var/lib/containers/atomic/kube-proxy.0
File /etc/kubernetes/config already exists
File /etc/kubernetes/proxy already exists
systemctl daemon-reload
systemctl enable kube-proxy

<1># 
# systemctl -l status kubelet.service kube-proxy.service 
Unit kubelet.service could not be found.
Failed to get properties: Access denied

Log in to comment on this ticket.

Metadata