Description of problem:
Cannot deploy docker-registry. The registry pod after getting created gets killed in sometime.
Readiness probe failed: HTTP probe failed with statuscode: 403
Liveness probe failed: HTTP probe failed with statuscode: 403
Version-Release number of selected component (if applicable):
Always on customer end
Steps to Reproduce:
1.Create a registry
The registry pod gets created and the again gets killed.
We can see the readiness and liveness probe failing with 403 error.
The registry pod shall not get killed after getting created. The Liveness and Readiness probe shall not give 403 error.
Miheer, is some kind of network filtering proxy running on the host?
The readiness probe receives (from node.log):
<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" SIZE=2><BR>For assistance, contact your network support team.</FONT></TD></TR>
Which means the request didn't event make it to the registry.
I have changed the "Working with HTTP Proxies" documentation
Please take a look. I can make further edits.
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.