Bug 1303118 - registry command sets up liveness/readiness probes that do not work for secure registries
Summary: registry command sets up liveness/readiness probes that do not work for secur...
Keywords:
Status: CLOSED DUPLICATE of bug 1302956
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Fabiano Franz
QA Contact: Wei Sun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-29 15:37 UTC by Jordan Liggitt
Modified: 2016-01-29 17:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-29 17:33:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1302956 0 unspecified CLOSED LivenessProbe Fails for Secured Integrated Registry 2021-02-22 00:41:40 UTC

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 ***


Note You need to log in before you can comment on or make changes to this bug.