-
Type:
Bug
-
Status: Closed
-
Priority:
Normal
-
Resolution: Won't Fix
-
Affects Version/s: SERVER 2.7.0
-
Fix Version/s: None
-
Component/s: Puppet Server
-
Labels:
-
Template:customfield_10700 160033
-
Acceptance Criteria:
- puppetserver stop command leaves the server stopped, not dead and the /var/run structure unlocked
-
Release Notes:Known Issue
The puppetserver stop command leaves the init/service management system in weird state (puppetserver dead but subsys locked) compared to service puppetserver stop (puppetserver is stopped). This might confused third-party scripts (or even our own code) that expect "stopped" and "not "dead but locked".
Consider the following sequence of commands (CentOS 6.5, Puppet 4.81, Puppet Server 2.6.1.master.SNAPSHOT.2016.11.04T2126):
# service puppetserver status
|
puppetserver (pid 16249) is running...
|
# service puppetserver stop
|
Stopping puppetserver: [ OK ]
|
# service puppetserver status
|
puppetserver is stopped
|
# service puppetserver start
|
Starting puppetserver: [ OK ]
|
# service puppetserver status
|
puppetserver (pid 16511) is running...
|
|
|
# puppetserver stop
|
# service puppetserver status
|
puppetserver dead but subsys locked
|
# puppetserver start
|
# puppetserver start
|
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
|
# service puppetserver status
|
puppetserver (pid 16743) is running...
|
I think the correct(er) behavior is for "puppetserver stop" to mimic the behavior of the service/init system.
- relates to
-
-
- Closed
-