Red Hat Bugzilla – Bug 1512832
[3.7] Registry console pod meets CrashLoopBackOff
Last modified: 2017-12-18 08:23:56 EST
The same issue also happened with 3.7. registry-console:v3.7 (40b6aa5bee20) Change image to v3.7.6 (5ef578189d02), registry console pod is running now. +++ This bug was initially created as a clone of Bug #1512826 +++ Description of problem Registry console pod meets CrashLoopBackOff Version-Release number of selected component (if applicable): Registry console v3.6, image id 920c98e806f1 (The image 3.6.173.0.63-10 attached in errata advisory 31024 has same id) How reproducible: Always Steps to Reproduce: 1. Install 3.6 OCP env that would deploy registry console 2. Check the registry console pod Actual results: 2. Check the pod, it shows CrashLoopBackOff # oc get pod registry-console-1-qn7hw 0/1 CrashLoopBackOff 2 30s # oc describe pod registry-console-1-qn7hw Image: brew...:8888/openshift3/registry-console:v3.6 ... 1m 26s 6 kubelet, openshift-14...redhat.com spec.containers{registry-console} Warning BackOff Back-off restarting failed container ... 1m 9s 7 kubelet, openshift-14...redhat.com Warning FailedSync Error syncing pod # oc logs registry-console-1-qn7hw 2017/11/14 08:29:38 Could't link /container/registry-brand to /container/os-release: exit status 1: ln: failed to create symbolic link '/container/os-release': Permission denied # Expected results: 2. Pod should be Running Additional info:
This has been fixed in dist-git and a new container image should be available soon.
Now v3.7.8 tag is available (v3.7 tag points to it) in brew registry # docker images | grep registry-console brew-...:8888/openshift3/registry-console v3.7 2bcaa0ada9cd 4 hours ago 375.8 MB brew-...:8888/openshift3/registry-console v3.7.8 2bcaa0ada9cd 4 hours ago 375.8 MB Tested it, registry console pod can be Running. Also did some regression test of registry console, basic function has no issue, project/IS creation, members adding/removing works well
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-2017:3464