Bug 1380342
Summary: | Cannot deploy docker-registry "Readiness probe failed: HTTP probe failed with statuscode: 403" | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Miheer Salunke <misalunk> |
Component: | Networking | Assignee: | Phil Cameron <pcameron> |
Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.2.1 | CC: | aos-bugs, bbennett, mfojtik, misalunk, tdawson |
Target Milestone: | --- | ||
Target Release: | 3.4.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
PR 3405 documented the work
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-05-18 09:27:04 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: |
Description
Miheer Salunke
2016-09-29 11:05:57 UTC
Miheer, is some kind of network filtering proxy running on the host? The readiness probe receives (from node.log): <HTML><HEAD><TITLE>Access Denied</TITLE></HEAD> <BODY> <FONT face="Helvetica"><big><strong></strong></big><BR></FONT> <blockquote> <TABLE border=0 cellPadding=1 width="80%"> <TR><TD><FONT face="Helvetica"><big>Access Denied (policy_denied)</big><BR><BR></FONT></TD></TR> <TR><TD><FONT face="Helvetica">Your system policy has denied access to the requested URL.</FONT></TD></TR> <TR><TD><FONT face="Helvetica"></FONT></TD></TR> <TR><TD><FONT face="Helvetica" SIZE=2><BR>For assistance, contact your network support team.</FONT></TD></TR> </TABLE> </blockquote> </FONT> </BODY> </HTML> Which means the request didn't event make it to the registry. ping? ping? I have changed the "Working with HTTP Proxies" documentation https://github.com/openshift/openshift-docs/pull/3405 Please take a look. I can make further edits. PR#3405 MERGED This should have gone to QA a while ago, moving it on. The doc looks good to me. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1235 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |