Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1628436

Summary: docker-registry pod cannot startup after running redeploy-certificates.yml playbook
Product: OpenShift Container Platform Reporter: Wenjing Zheng <wzheng>
Component: MasterAssignee: Stefan Schimanski <sttts>
Status: CLOSED WONTFIX QA Contact: Wenjing Zheng <wzheng>
Severity: low Docs Contact:
Priority: medium    
Version: 3.11.0CC: aos-bugs, bparees, jokerman, mmccomas
Target Milestone: ---Keywords: Regression
Target Release: 3.11.z   
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: 2020-05-05 15:10:55 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:
Attachments:
Description Flags
Master api log
none
History event list none

Description Wenjing Zheng 2018-09-13 03:30:48 UTC 
Description of problem:
docker-registry pod cannot startup after running redeploy-certificates.yml playbook for master service got restart while docker-regsitry is re-deploying. 
# oc logs pods/docker-registry-2-deploy
--> Scaling up docker-registry-2 from 0 to 1, scaling down docker-registry-1 from 1 to 0 (keep 1 pods available, don't exceed 2 pods)
    Scaling docker-registry-2 up to 1
--> Error listing events for replication controller docker-registry-2: Get https://172.30.0.1:443/api/v1/namespaces/default/events?fieldSelector=involvedObject.namespace%3Ddefault%2CinvolvedObject.kind%3DReplicationController%2CinvolvedObject.uid%3D0e1d56c7-b6f7-11e8-a43d-0e9bd6442c18%2CinvolvedObject.name%3Ddocker-registry-2: dial tcp 172.30.0.1:443: connect: connection refused
--> Error listing events for replication controller docker-registry-1: Get https://172.30.0.1:443/api/v1/namespaces/default/events?fieldSelector=involvedObject.name%3Ddocker-registry-1%2CinvolvedObject.namespace%3Ddefault%2CinvolvedObject.kind%3DReplicationController%2CinvolvedObject.uid%3D64d79bc5-b6f3-11e8-8fe9-0e9bd6442c18: dial tcp 172.30.0.1:443: connect: connection refused
The connection to the server 172.30.0.1:443 was refused - did you specify the right host or port?

But if trigger deploy again, it will become running.

Version-Release number of selected component (if applicable):
openshift-ansible-3.11.0-0.32.0.git.0.b27b349.el7.noarch

How reproducible:
always

Steps to Reproduce:
1.Set up a 3.11 env 
2.Run redeploy-certificates.yml playbook
/usr/share/ansible/openshift-ansible/playbooks/redeploy-certificates.yml
3.Check docker-registry pod

Actual results:
docker registry pod is error.

Expected results:
docker registry pod is running.

Additional info:
1. History event will be provided in attachment;
2. Master api log will be in attachment too;
Comment 1 Wenjing Zheng 2018-09-13 03:40:03 UTC 
Created attachment 1482926 [details]
Master api log
Comment 2 Wenjing Zheng 2018-09-13 03:41:03 UTC 
Created attachment 1482927 [details]
History event list