Bug 1399856

Summary:	Error: Could not request certificate: Error 403 on SERVER: Forbidden request: SERVER_NAME(SEVER_IP) access to /certificate_revocation_list/ca [find] at :133
Product:	Red Hat Satellite	Reporter:	Ian Tewksbury <itewksbu>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2.4	CC:	bbuckingham, itewksbu, stbenjam
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-02 20:07:47 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 Ian Tewksbury 2016-11-29 22:27:33 UTC

Description of problem:

[root@itewk-test puppet]# puppet agent -t
Info: Creating a new SSL key for itewk-test.rhc-lab.iad.redhat.com
Info: Caching certificate for ca
Info: csr_attributes file loading from /etc/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for itewk-test.rhc-lab.iad.redhat.com
Info: Certificate Request fingerprint (SHA256): 29:A5:BC:20:D1:3F:9C:C9:1D:12:6A:BB:D1:0D:6C:B2:B0:15:01:45:92:F9:C5:CB:A7:0E:3F:95:E6:26:3B:50
Info: Caching certificate for itewk-test.rhc-lab.iad.redhat.com
Error: Could not request certificate: Error 403 on SERVER: Forbidden request: sat-cap-content-1.rhc-lab.iad.redhat.com(10.15.69.159) access to /certificate_revocation_list/ca [find] at :133
Exiting; failed to retrieve certificate and waitforcert is disabled


How reproducible:

Always


Actual results:

An error message when trying to run puppet.


Expected results:

No error message when trying to run puppet.


Additional info:

If I edit /etc/puppet/auth.conf to add `auth any` to the certificate_revocation_list path

from:

# allow all nodes to access the certificates services
path /certificate_revocation_list/ca
method find
allow *

to:

# allow all nodes to access the certificates services
path /certificate_revocation_list/ca
auth any
method find
allow *

and restart the httpd service then I no longer get the error.

This looks to be the same as one of the issues reported in https://bugzilla.redhat.com/show_bug.cgi?id=1260973 which says this had been resolved but as of 6.2.4 it does not seem to be resolved.

Comment 2 Stephen Benjamin 2016-12-02 19:04:01 UTC

Works for me just fine on 6.2.4 and a regular puppet client:

[root@puppet-client ~]# puppet agent --test
Info: Creating a new SSL key for puppet-client.example.com
Info: csr_attributes file loading from /etc/puppet/csr_attributes.yaml
Info: Creating a new SSL certificate request for puppet-client.example.com
Info: Certificate Request fingerprint (SHA256): EF:F7:76:1B:EF:62:EB:D9:82:32:F2:B2:F9:C2:B2:24:22:07:4D:BF:52:E5:46:50:2F:59:5D:1D:03:57:D7:A3
Exiting; no certificate found and waitforcert is disabled


auth any" isn't the correct solution, you're just turning all the auth off.

Sounds like you have something misconfigured, what did you change from a default install?

Comment 3 Ian Tewksbury 2016-12-02 19:50:50 UTC

@Stephen,

I am using a centralized Puppet CA on the Satellite Server and using the Puppet CA Proxy on the Capsule.

SO maybe that is the issue?

Let me know if there is any specific configs or something you need to see. I can also just give you access to my environment if you are curious.

Comment 4 Stephen Benjamin 2016-12-02 20:07:47 UTC

Indeed it is, per the puppet docs your change  is the right one:
  https://docs.puppet.com/guides/scaling_multiple_masters.html#option-2-proxy-certificate-traffic

We'll need to handle that in the installer as well as part of fixing BZ1233302.

Thanks!

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

Comment 5 Ian Tewksbury 2016-12-02 20:10:40 UTC

@stephen,

So to clarify, the solution is to set auth all and you all will work on including that in BZ1233302?

Comment 6 Stephen Benjamin 2016-12-02 21:04:20 UTC

Yup!