Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
PUP 5.3.3
-
None
-
Coremunity
-
Platform Core KANBAN
-
Needs Assessment
-
Normal
-
3 - 25-50% of Customers
-
2 - Annoyance
-
2 - $$$
-
-
Bug Fix
-
-
Needs Assessment
Description
A common error in enterprise environments is a mismatch between the server setting on the agent and the common name of the master's cert / its dns alt names.
Today, if this situation occurs the error message the agent prints is as clear as mud. For example:
# You can't tell, but for this run server=master.tld
|
#
|
[root@aws-1 ssl]# puppet agent -t
|
Warning: Unable to fetch my node definition, but the agent run will continue:
|
Warning: SSL_connect returned=1 errno=0 state=error: certificate verify failed: [ok for /CN=master-1.tld]
|
Info: Retrieving pluginfacts
|
Error: /File[/opt/puppetlabs/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=error: certificate verify failed: [ok for /CN=master-1.tld]
|
...
|
This error message is INCREDIBLY unhelpful. There's kinda-sorta a reference to the master's certificate being master-1.tld, but you can't see in the message that the configured server is master.tld. There's also no reference to other valid alt names.
What we want:
The error message should clearly state something along the lines of
Error: Unable to validate server certificate. Expected "master.tld":
|
server certificate common name "master-1.tld" does not match
|
server certificate alt name "puppet" does not match
|
server certificate alt name "master" does not match
|
server certificate alt name "master-alt.tld" does not match
|