Bug 1090398 - kubelet starts with errors: Fail to get rootfs information unable to find data for container
kubelet starts with errors: Fail to get rootfs information unable to find da...
Status: NEW
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Containers
Current
Other Other
: P2 - High : Normal (vote)
: ---
Assigned To: Flavio Castelli
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-20 14:48 UTC by Panagiotis Georgiadis
Modified: 2018-05-29 06:46 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Panagiotis Georgiadis 2018-04-20 14:48:48 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.
Comment 1 Flavio Castelli 2018-05-09 14:41:52 UTC
This is happening also with SUSE CaaS Platform v3
Comment 2 Valentin Rothberg 2018-05-28 08:03:01 UTC
@Flavio: Do you know if the issue has been fixed in the meantime?
Comment 3 Flavio Castelli 2018-05-28 12:08:03 UTC
Yes, this is still happening. Though everything is working fine (conformance tests are passing), I'll change severity to "normal".