Bug 1513356 - [3.4] Registry console pod meets CrashLoopBackOff
Summary: [3.4] Registry console pod meets CrashLoopBackOff
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Registry Console
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.4.z
Assignee: Martin Pitt
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On: 1512826
Blocks: 1512832
TreeView+ depends on / blocked
 
Reported: 2017-11-15 09:41 UTC by XiaochuanWang
Modified: 2019-11-12 19:24 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1512826
Environment:
Last Closed: 2019-11-12 19:24:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.