Bug 1513356

Summary: [3.4] Registry console pod meets CrashLoopBackOff
Product: OpenShift Container Platform Reporter: XiaochuanWang <xiaocwan>
Component: Registry ConsoleAssignee: Martin Pitt <mpitt>
Status: CLOSED WONTFIX QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: high    
Version: 3.4.1CC: aos-bugs, erich, jialiu, trankin, wmeng, xxia, yanpzhan, yapei
Target Milestone: ---Keywords: Regression
Target Release: 3.4.z   
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: 2019-11-12 19:24:34 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:
Bug Depends On: 1512826    
Bug Blocks: 1512832    

Comment 1 Peter 2017-11-15 14:55:41 UTC
Updated in dist-git. Waiting for rebuild.

Comment 4 Yanping Zhang 2018-01-26 07:47:45 UTC
Tested env version:
openshift v3.4.1.44.50
kubernetes v1.4.0+776c994

The bug still exists on OCP 3.4, the registry-console pod cann't start with image v3.4
# oc logs registry-console-2-3mp3r
2018/01/26 07:23:32 Could't link /container/registry-brand to /container/os-release: exit status 1: ln: failed to create symbolic link '/container/os-release': Permission denied

Comment 6 Eric Rich 2019-11-12 19:24:34 UTC
This was fixed in 3.6 and never backported, to 3.4 which is no longer in Maintenance, Closing to reflect this.