Bug 1508561

Summary: After running the config playbook invalid certificate for docker-registry.default.svc
Product: OpenShift Container Platform Reporter: Javier Ramirez <javier.ramirez>
Component: Cluster Version OperatorAssignee: Kenny Woodson <kwoodson>
Status: CLOSED ERRATA QA Contact: Weihua Meng <wmeng>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: aos-bugs, dsundqvi, erjones, javier.ramirez, jokerman, jrosenta, meggen, mmccomas, sdodson, wmeng
Target Milestone: ---   
Target Release: 3.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1554481 1554483 (view as bug list) Environment:
Last Closed: 2018-03-28 14:09:47 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:
Bug Depends On:    
Bug Blocks: 1554481, 1554483    

Comment 8 Scott Dodson 2018-01-25 15:28:56 UTC
David, Javier,

Can you help me understand what all has been done to the environment to necessistate this change? Upgraded environments should not switch to push via dns yet.  Just trying to make a decision as to whether or not we call this a 3.9 or 3.10 target release.

Comment 11 Scott Dodson 2018-01-30 21:14:18 UTC
https://github.com/openshift/openshift-ansible/pull/6851 WIP

Comment 12 Scott Dodson 2018-02-02 18:50:32 UTC
This has been fixed by checking for a cert that lacks the proper signing and regenerating it if needed so that we can complete the transition to push via DNS.

Comment 17 Weihua Meng 2018-02-07 18:28:44 UTC
Fixed.
openshift-ansible-3.9.0-0.38.0.git.0.57e1184.el7.noarch

Steps:
1. setup OCP v3.5 cluster
2. upgrade to OCP v3.6
3. migrate etcd
4. upgrade to OCP v3.7
5. upgrade to OCP v3.9
6. check imagestream
# oc new-project test1
# oc new-app nodejs-mongodb-example
# oc describe imagestreams/nodejs-mongodb-example | grep Docker
before fix
Docker Pull Spec:	172.31.14.93:5000/wmeng39/nodejs-mongodb-example
after fixed
Docker Pull Spec:	docker-registry.default.svc:5000/wmeng39/nodejs-mongodb-example

Comment 18 Weihua Meng 2018-02-09 08:43:57 UTC
Got same error.
Pushing image docker-registry.default.svc:5000/wmeng391/nodejs-mongodb-example:latest ...
Registry server Address: 
Registry server User Name: serviceaccount
Registry server Email: serviceaccount
Registry server Password: <<non-empty>>
error: build error: Failed to push image: Get https://docker-registry.default.svc:5000/v1/_ping: x509: certificate is valid for docker-registry-default.apps.0206-meb.qe.rhcloud.com, docker-registry.default.svc.cluster.local, 172.31.112.208, not docker-registry.default.svc

Comment 21 Weihua Meng 2018-02-09 08:49:09 UTC
Steps:
1. setup OCP v3.5 cluster
2. upgrade to OCP v3.6
3. migrate etcd
4. upgrade to OCP v3.7
5. upgrade to OCP v3.9
6. check build log
# oc new-project wmeng391
# oc new-app nodejs-mongodb-example
# oc logs po/nodejs-mongodb-example-1-build

Comment 22 Scott Dodson 2018-02-22 14:23:34 UTC
https://github.com/openshift/openshift-ansible/pull/7121 fixed this and it merged a few days ago

Comment 23 Weihua Meng 2018-02-25 09:51:20 UTC
Not fixed.
openshift-ansible-3.9.0-0.51.0.git.0.e26400f.el7.noarch

Steps:
1. setup OCP v3.5 cluster
2. upgrade to OCP v3.6
3. migrate etcd
4. upgrade to OCP v3.7
5. upgrade to OCP v3.9
6. check build log
# oc new-project wmeng39051
# oc new-app nodejs-mongodb-example
# oc logs po/nodejs-mongodb-example-1-build

Pushing image docker-registry.default.svc:5000/wmeng39051/nodejs-mongodb-example:latest ...
Registry server Address: 
Registry server User Name: serviceaccount
Registry server Email: serviceaccount
Registry server Password: <<non-empty>>
error: build error: Failed to push image: Get https://docker-registry.default.svc:5000/v1/_ping: x509: certificate is valid for docker-registry-default.apps.0224-l86.qe.rhcloud.com, docker-registry.default.svc.cluster.local, 172.31.92.27, not docker-registry.default.svc

Comment 26 Kenny Woodson 2018-02-27 17:16:12 UTC
Proposed fix: https://github.com/openshift/openshift-ansible/pull/7314

Comment 27 Weihua Meng 2018-03-04 09:45:49 UTC
Fixed.
openshift-ansible-3.9.2-1.git.0.1a855b3.el7.noarch

Steps:
1. setup OCP v3.5 cluster
2. upgrade to OCP v3.6
3. migrate etcd
4. upgrade to OCP v3.7
5. upgrade to OCP v3.9
6. check build log
# oc new-project wmeng392
# oc new-app nodejs-mongodb-example
# oc logs po/nodejs-mongodb-example-1-build

Pushing image docker-registry.default.svc:5000/wmeng392/nodejs-mongodb-example:latest ...
Pushed 0/6 layers, 2% complete
Pushed 1/6 layers, 27% complete
Pushed 2/6 layers, 44% complete
Pushed 3/6 layers, 58% complete
Pushed 4/6 layers, 71% complete
Pushed 4/6 layers, 100% complete
Pushed 5/6 layers, 100% complete
Pushed 6/6 layers, 100% complete
Push successful

Comment 30 errata-xmlrpc 2018-03-28 14:09:47 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-2018:0489