Red Hat Bugzilla – Bug 1304101
184.108.40.206->220.127.116.11 registry health check not updated
Last modified: 2016-02-04 13:23:29 EST
Description of problem:
With 18.104.22.168 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):
Steps to Reproduce:
1. Install 22.214.171.124-1.git.15.5e061c3.el7aos
2. Upgrade cluster
3. Watch oc get events -w and see registry get restarted
registry gets restarted every health check
registry to stay up
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 v126.96.36.199 and v188.8.131.52 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
It is secured. We may gave flipped it to secure when we upgraded so it would have had the 184.108.40.206 data that is there when a new 220.127.116.11 cluster is built.
The registry had to have been re-created under v18.104.22.168 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 ***