Issue #7027 has been updated by Randall Hansen.

Pieter and I talked and this is what I think is best:

If cert signing fails for any reason, present the user with a simple message to 
that effect and two copyable commands:

1. to sign the cert (this should be the final step, and if this succeeds the 
bootstrap process should be complete and successful),
2. to destroy the node (this should also remove the node from the ENC).

If (2) isn't completely possible, I think the fallback is to instead show two 
commands for (1), the second of which is to classify the node.
----------------------------------------
Feature #7027: CloudPack: Automatic Certificate Signing
https://projects.puppetlabs.com/issues/7027

Author: Pieter van de Bruggen
Status: Accepted
Priority: Normal
Assignee: Pieter van de Bruggen
Category: 
Target version: 
Affected Puppet version: 
Keywords: 
Branch: 


We should at least make an attempt to sign certificates created for new cloud 
instances.

Still undefined is the behavior of when the cloud instance's CA is not the same 
as ours, or when we don't have valid credentials or authorization to sign on 
the cloud instance's CA.

Randall: In the event of certificate signing failure, what should the behavior 
be?  Simply skipping the step (and the following steps)?  Destroying the 
instance?


-- 
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