Bug 1697644 - image pull secret is not in the right location
Summary: image pull secret is not in the right location
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.1.0
Assignee: Abhinav Dahiya
QA Contact: Roshni
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-08 21:59 UTC by Derek Carr
Modified: 2019-06-04 10:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-04 10:47:18 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0758 0 None None None 2019-06-04 10:47:29 UTC

Description Derek Carr 2019-04-08 21:59:50 UTC 
Description of problem:
coreos-pull-secret is in kube-system


Expected results:
the secret should be in openshift-config and named "openshift-pull-secret"
Comment 1 Derek Carr 2019-04-08 22:01:01 UTC 
well, let's shorten it to "pull-secret" in "openshift-config"
Comment 2 Abhinav Dahiya 2019-04-08 22:04:16 UTC 
https://github.com/openshift/installer/pull/1554
https://github.com/openshift/origin/pull/22508
https://github.com/openshift/machine-config-operator/pull/609
Comment 3 Abhinav Dahiya 2019-04-09 18:20:11 UTC 
updated more consumers of kube-system/coreos-pull-secret

https://github.com/openshift/cluster-monitoring-operator/pull/315
https://github.com/openshift/cluster-samples-operator/pull/130
Comment 4 Abhinav Dahiya 2019-04-16 17:29:44 UTC 
dropped the kube-system/coreos-pull-secret https://github.com/openshift/installer/pull/1567
Comment 6 Roshni 2019-04-23 10:46:03 UTC 
Using 4.0.0-0.nightly-2019-04-23-054921 and 4.1.0-0.nightly-2019-04-23-054919 I am able to verify that coreos-pull-secret has been removed from kube-system and pull-secret exists under openshift-config namespace.
Comment 8 errata-xmlrpc 2019-06-04 10:47:18 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-2019:0758
Note You need to log in before you can comment on or make changes to this bug.