Bug 1710293

Summary: Wrong storage prefix for kubernetes resources in etcd
Product: OpenShift Container Platform Reporter: Maciej Szulik <maszulik>
Component: MasterAssignee: Michal Fojtik <mfojtik>
Status: CLOSED ERRATA QA Contact: Xingxing Xia <xxia>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.1.0CC: aos-bugs, gblomqui, jokerman, mmccomas, sponnaga, vlaad
Target Milestone: ---Keywords: BetaBlocker
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:48:48 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:

Comment 3 Xingxing Xia 2019-05-16 06:47:37 UTC
First check the issue in old payload env 4.1.0-0.nightly-2019-05-14-202907:
Check /etc/kubernetes/static-pod-resources/configmaps/config/config.yaml, there is "storagePrefix":"openshift.io".
Then check etcd resources:
$ oc rsh -n openshift-etcd etcd-member-ip-10-0-140-235.ap-south-1.compute.internal
sh-4.2# export ETCDCTL_API=3 ETCDCTL_CACERT=/etc/ssl/etcd/ca.crt ETCDCTL_CERT=`ls /etc/ssl/etcd/*etcd-peer*crt` ETCDCTL_KEY=`ls /etc/ssl/etcd/*etcd-peer*key`
sh-4.2# etcdctl get / --endpoints 127.0.0.1:2379 --prefix --keys-only | grep "^/kubernetes.io/" # get nothing

Then check the issue in latest payload 4.1.0-0.nightly-2019-05-16-001402, /etc/kubernetes/static-pod-resources/configmaps/config/config.yaml doesn't have "storagePrefix":"openshift.io", `etcdctl get / --endpoints 127.0.0.1:2379 --prefix --keys-only` shows both /kubernetes.io/ resources and /openshift.io/ resources correctly.

Comment 5 errata-xmlrpc 2019-06-04 10:48:48 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