Bugzilla – Bug 1090398
kubelet starts with errors: Fail to get rootfs information unable to find data for container
Last modified: 2018-05-29 06:46:00 UTC
> systemctl start kubelet
> E0420 16:41:48.326293 8350 container_manager_linux.go:583] [ContainerManager]: Fail to get rootfs information unable to find data for container /
I guess this the reason that a couple of milliseconds later it skips the pod syncing:
> I0420 16:41:48.426334 8350 kubelet.go:1789] skipping pod synchronization - [container runtime is down]
There's also a warning afterwards (dunno if this related to this bug though)
> W0420 16:41:48.476056 8350 container.go:393] Failed to create summary reader for "/system.slice/systemd-fsck-root.service": none of the resources are being tracked.
This is happening also with SUSE CaaS Platform v3
@Flavio: Do you know if the issue has been fixed in the meantime?
Yes, this is still happening. Though everything is working fine (conformance tests are passing), I'll change severity to "normal".