Bug 1303118

Summary: registry command sets up liveness/readiness probes that do not work for secure registries
Product: OpenShift Container Platform Reporter: Jordan Liggitt <jliggitt>
Component: ocAssignee: Fabiano Franz <ffranz>
Status: CLOSED DUPLICATE QA Contact: Wei Sun <wsun>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: aos-bugs, jlee, jokerman, mmccomas
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-01-29 17:33:37 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 Jordan Liggitt 2016-01-29 15:37:36 UTC 
Description of problem:

The liveness/readiness probes set up by the `oadm registry` command fail if the registry is serving over TLS. There needs to be a way to indicate the HTTPS scheme should be used when creating the probes.

When the readiness/liveness probes fail, that triggers regular restarts of the registry.


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


How reproducible:
Always


Steps to Reproduce:
1. Run 
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 jooho lee 2016-01-29 17:33:26 UTC 
Duplicate bugzilla : 1302956
Comment 2 Jordan Liggitt 2016-01-29 17:33:37 UTC 

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