Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1512832

Summary: [3.7] Registry console pod meets CrashLoopBackOff
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: Registry ConsoleAssignee: Peter <pvolpe>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: high    
Version: 3.7.0CC: aos-bugs, jialiu, pvolpe, xtian, xxia, yapei
Target Milestone: ---Keywords: Regression
Target Release: 3.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1512826 Environment:
Last Closed: 2017-12-18 13:23:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 1513356, 1512826    
Bug Blocks:    

Description Johnny Liu 2017-11-14 08:59:04 UTC
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:

Comment 1 Peter 2017-11-14 19:19:17 UTC
This has been fixed in dist-git and a new container image should be available soon.

Comment 2 Xingxing Xia 2017-11-15 07:58:54 UTC
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

Comment 6 errata-xmlrpc 2017-12-18 13:23:56 UTC
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