Issue #18303 has been updated by eric sorenson. Status changed from Unreviewed to Needs Decision Assignee set to eric sorenson Target version set to 3.x Keywords set to backlog
Thanks for the report and use-case description, Gerard. This seems related to a bug I was looking at the other day - #4568. It's not an exact duplicate but addressing this should be part of the solution. ---------------------------------------- Feature #18303: Ability to take puppet master out of service. https://projects.puppetlabs.com/issues/18303#change-80081 Author: Gerard Hickey Status: Needs Decision Priority: Normal Assignee: eric sorenson Category: Target version: 3.x Affected Puppet version: Keywords: backlog Branch: Desire to have a command line (such as puppet master --disable) that will change the status reported by /production/status/no_key. This would allow a puppet master to be taken out of service in a load balancer without having to shutdown the service or making configuration changes to the load balancer. This would allow the puppet master to be worked on and tested without significantly changing the environment. Conversely there would need to be a command to reenable the puppet master server (such as puppet master --enable). -- 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.
