Bug 1721546
Summary: | Openshift-on-OpenStack Add protection from a docker/K8s bug | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jon Uriarte <juriarte> |
Component: | Installer | Assignee: | Michał Dulko <mdulko> |
Installer sub component: | openshift-ansible | QA Contact: | Jon Uriarte <juriarte> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | unspecified | CC: | itbrown, ltomasbo |
Version: | 3.11.0 | Keywords: | Triaged |
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-09-03 15:56:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jon Uriarte
2019-06-18 14:07:53 UTC
Adding correct logs when the issue is reproduced: $ oc -n kuryr logs -f kuryr-cni-ds-s65sh -c kuryr-cni container_linux.go:247: starting container process caused "process_linux.go:364: container init caused \"rootfs_linux.go:54: mounting \\\"/var/lib/origin/openshift.local.volumes/pods/0b1d0cd7-8ec1-11e9-a55c-fa163ee3d6f8/volume-subpaths/config-volume/kuryr-cni/2\\\" to rootfs \\\"/var/lib/docker/overlay2/400ab2b1ad7563404e51d04959ce6dfb2ce51df0a3d4c168eb42822ef52ff862/merged\\\" at \\\"/var/lib/docker/overlay2/400ab2b1ad7563404e51d04959ce6dfb2ce51df0a3d4c168eb42822ef52ff862/merged/etc/kuryr/kuryr.conf\\\" caused \\\"no such file or directory\\\"\"" I switched this to medium as this only happens when Kuryr's ConfigMap gets edited. This is now fixed, so I guess ON_QA is the correct status. Verified with: openshift v3.11.136 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2580 |