Issue #9704 has been updated by Ryan Conway.

Status changed from Needs More Information to Closed

Hmm, so I spent more time this afternoon looking at this issue and was able to 
resolve it by changing the SSL certificate configuration in our Apache2 vhost, 
as the master sits behind Passenger.

I'm not 100% certain what was happening, and why the Apache config impacts a 
node clean, but I'm happy to close this since no one else seems to be 
experiencing it.

Thanks!
Ryan
----------------------------------------
Bug #9704: Cleaning a node results in all the certificates on the master being 
revoked.
https://projects.puppetlabs.com/issues/9704

Author: Ryan Conway
Status: Closed
Priority: Normal
Assignee: Ryan Conway
Category: SSL
Target version: 
Affected Puppet version: 2.7.3
Keywords: 
Branch: 


Hey there,

An unusual problem I have stumbled across today - when attempting to clean a 
particular node from our master, all the node certificates are being marked as 
'revoked'.

The Puppet Master version is 2.7.3, installed via Rubygems 1.3.7, running Ruby 
Enterprise 1.8.7 2010-04-19 patchlevel 253, on 64-bit Ubuntu 10.04 LTS.

The commands I have tried are:

  puppet node clean $nodename
  puppetca --clean $nodename

Both commands output properly that they are cleaning the specified node, 
however asking for a list of all certificates shows (revoked) beside every one.

  puppetca --list --all
  + $nodename1 (fingerprint) (certificate revoked)
  + $nodename2 (fingerprint) (certificate revoked)
  ...etc

Final piece of information in case this is relevant - the master is serving 
agents from behind Apache2 with Passenger.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to