Bug 1578088 – [3.9] Secret created by `oc create secret docker-registry` cannot pull image from external private registry

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1578088 - [3.9] Secret created by `oc create secret docker-registry` cannot pull image from external private registry

Summary:	[3.9] Secret created by `oc create secret docker-registry` cannot pull image ...

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Pod (Show other bugs)
Sub Component:
Version:	3.9.0
Hardware:	Unspecified Unspecified

Priority	urgent Severity high
Target Milestone:	---
Target Release:	3.9.z
Assigned To:	Seth Jennings
QA Contact:	DeShuai Ma
Docs Contact:

URL:
Whiteboard:
Keywords:	Regression

Depends On:	1561989 1600539
Blocks:	1561996
	Show dependency tree / graph

Reported:	2018-05-14 15:04 EDT by Seth Jennings
Modified:	2018-07-12 09:01 EDT (History)
CC List:	17 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Fixes an issue pulling images from a private docker hub registry
Story Points:	---
Clone Of:	1561989
Environment:
Last Closed:	2018-06-06 11:46:21 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:1796	None	None	None	2018-06-06 11:46 EDT

Groups: None (edit)

Comment 3 weiwei jiang 2018-05-30 02:26:47 EDT

Checked with 
# oc version 
oc v3.9.30
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://ip-172-18-3-197.ec2.internal:8443
openshift v3.9.30
kubernetes v1.9.1+a0ce1bc657

And the issue can not be reproduced.

Comment 5 errata-xmlrpc 2018-06-06 11:46:21 EDT

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-2018:1796

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