Project

General

Profile

Bug #1105

multiple puppetca or puppet enterprise puppet cause smart-proxy to fail

Added by Corey Osman about 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

I have /usr/bin/puppetca and I have /opt/puppet/bin/puppet. Both are supposed to list the puppet certificates. However, since I am using puppet enterprise foreman needs to use /opt/puppet/bin/puppet cert. Furthermore, I think foreman should test each match to see which puppet or puppetca works.

History

#1 Updated by Corey Osman about 8 years ago

This will cause kickstarts to not process and leave the user with a OS to configure manually.

D, [2011-08-11T03:40:02.577838 #32308] DEBUG -- : Found sudo at /usr/bin/sudo
D, [2011-08-11T03:40:02.577945 #32308] DEBUG -- : Executing /usr/bin/sudo -S /usr/bin/puppetca --clean puppetagent5.logicminds.corp
W, [2011-08-11T03:40:04.180020 #32308]  WARN -- : Failed to run puppetca: Retrieved certificate does not match private key; please remove certificate from server and regenerate it with the current key

E, [2011-08-11T03:40:04.181042 #32308] ERROR -- : Failed to remove certificate(s) for puppetagent5.logicminds.corp: Execution of puppetca failed, check log files
192.168.11.47 - - [11/Aug/2011 03:40:04] "DELETE /puppet/ca/puppetagent5.logicminds.corp HTTP/1.1" 406 111 1.6088
puppet - - [11/Aug/2011:03:40:02 EDT] "DELETE /puppet/ca/puppetagent5.logicminds.corp HTTP/1.1" 406 111
- -> /puppet/ca/puppetagent5.logicminds.corp

#2 Updated by Benjamin Papillon about 6 years ago

  • Status changed from New to Closed

it has been resolved. If the problem persists, feel free to open the ticket again.

Also available in: Atom PDF