-
Type:
Bug
-
Status: Closed
-
Priority:
Normal
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: PUP 6.0.2
-
Component/s: None
-
Template:
-
Acceptance Criteria:
-
Epic Link:
-
Team:Platform OS
-
Sprint:Platform OS Kanban
-
CS Priority:Normal
-
CS Frequency:3 - 25-50% of Customers
-
CS Severity:2 - Annoyance
-
CS Business Value:5 - $$$$$$
-
CS Impact:
-
Release Notes:Bug Fix
-
Release Notes Summary:The Windows service provider now returns enable = false, ensure = stopped for nonexistent services, and errors when setting enable = true or ensure = running on them.
Linux agents don't seem to have this issue, for example:
]# puppet apply -e 'service {"notaservice": ensure => "stopped", enable => false,}' |
Notice: Compiled catalog for pe-201620-master.example.com in environment production in 0.12 seconds |
Notice: Applied catalog in 0.33 seconds |
However, on Windows, an attempt to apply the same resource gives:
PS C:\Users\Administrator> puppet apply -e 'service {"notaservice": ensure => "stopped", enable => false,}' |
Notice: Compiled catalog for windows-agent1 in environment production in 0.03 seconds |
Error: /Stage[main]/Main/Service[notaservice]: Could not evaluate: Cannot get status of notaservice, error was: The specified service does not exist as an installed service. - OpenService: The specified service does not exist as an installed service.
|
Wrapped exception:
|
The specified service does not exist as an installed service. - OpenService: The specified service does not exist as an installed service.
|
Notice: Applied catalog in 0.14 seconds |
- is blocked by
-
PUP-5475 Windows Service provider should use something better than net.exe - perhaps direct FFI access
-
- Closed
-