Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
-
Night's Watch
-
2
-
NW - 2020-05-13
-
Needs Assessment
-
38781
-
1
-
Bug Fix
-
Fix `puppet resource` wrongly reporting the `enabled` state of a systemd service when the `ensure` parameter is also specified.
-
Needs Assessment
Description
When installing an agent on Ubuntu (any version) using switches to both enable and stop the puppet service, via
curl -k https://<fqdnhere>:8140/packages/current/install.bash | bash -s -- --puppet-service-ensure stopped --puppet-service-enable true |
The output shows this:
Setting the puppet service to ensure=stopped and enable=true |
service { 'puppet': |
ensure => 'stopped', |
enable => 'false', |
provider => 'systemd', |
}
|
The expected output, and the output on EL6/7/8, is this:
Setting the puppet service to ensure=stopped and enable=true |
service { 'puppet': |
ensure => 'stopped', |
enable => 'true', |
provider => 'systemd', |
}
|
This issue is entirely cosmetic, the service does end up enabled. The issue is not present when the switch "--puppet-service-enable true" is used standalone.
* Please see Zendesk Support tab for further comments and attachments.