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 1513356 - [3.4] Registry console pod meets CrashLoopBackOff
Summary: [3.4] Registry console pod meets CrashLoopBackOff
Keywords:
Status: ASSIGNED
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: 2018-04-17 18:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1512826
Environment:
Last Closed:


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


Note You need to log in before you can comment on or make changes to this bug.