Bug 1304101

Summary: 3.1.0.4->3.1.1.6 registry health check not updated
Product: OpenShift Container Platform Reporter: Wesley Hearn <whearn>
Component: Cluster Version OperatorAssignee: Brenton Leanhardt <bleanhar>
Status: CLOSED DUPLICATE QA Contact: Anping Li <anli>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.1.0CC: aos-bugs, bleanhar, jokerman, mmccomas, whearn
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-04 18:23:29 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:

Description Wesley Hearn 2016-02-02 21:47:52 UTC 
Description of problem:
With 3.1.1.6 the health check for the registry changed from /healthz to /
During the upgrade the DC did not get updated and caused the registry to get restarted every 10 secs.

Version-Release number of selected component (if applicable):
3.1.1.6

How reproducible:
Often

Steps to Reproduce:
1. Install 3.1.0.4-1.git.15.5e061c3.el7aos
2. Upgrade cluster
3. Watch oc get events -w and see registry get restarted

Actual results:
registry gets restarted every health check

Expected results:
registry to stay up

Additional info:
Comment 1 Scott Dodson 2016-02-03 20:54:33 UTC 
For what it's worth, when I tried to reproduce this based on our IRC discussions I found that I had no liveness probes created under v3.1.0.4 and v3.1.1.6 worked fine in the default config.

Is your registry secured? If so it's probably a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1302956
Comment 2 Wesley Hearn 2016-02-03 21:33:23 UTC 
It is secured. We may gave flipped it to secure when we upgraded so it would have had the 3.1.0.4 data that is there when a new 3.1.1.6 cluster is built.
Comment 3 Scott Dodson 2016-02-04 18:23:29 UTC 
The registry had to have been re-created under v3.1.1.6 and then secured which would've caused the health check to start failing because the documentation at the time lacked a step to switcht he liveness probe from HTTP to HTTPS.

*** This bug has been marked as a duplicate of bug 1302956 ***