Bug #15080
closed
Service technique reports a warning after stopping a service
Description
Hi all,
in the "Services technique" is the option to stop and disable a service, the service is stopped and deactivated as expected.
But the report then issues a "warning", which should not be the case.
Best regards,
Alex
OS: SLES12SP4
Rudder agent: 5.0.11
Rudder server: 5.0.11
# systemctl is-active nscd.service
active
# systemctl is-enabled nscd.service
enabled
#
# rudder agent run -q
[...]
warning services None nscd Check if service nscd is disabled at boot could not be repaired
E| repaired Services technique Services status nscd The service status "stopped" for nscd was repaired
E| repaired Services technique Services boot status nscd The service boot status "disabled" for nscd was repaired
[...]
# rudder agent run -q
[...]
warning services None nscd Check if the service nscd is started could not be repaired
[...]
#
# systemctl is-active nscd.service
inactive
# systemctl is-enabled nscd.service
disabled
#
Files
Updated by Félix DALLIDET over 5 years ago
This is the "expected" behaviour since:
The technique uses generic methods which are also calling other generic methods with limited scope to check if the service is running.
Those sub-methods reports are keep in "Info" and "Warning" for information purposes, and so, errors are caught by the "rudder agent run -q" but are only representative
about internal logic used in Rudder.
This is more an architecture problem than a configuration on or a bug. You can check #8683 which describe more precisely the problem.
Updated by 
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 80 to 79
Updated by François ARMAND about 5 years ago
- Is duplicate of Architecture #8683: check_* methods output error messages when the result of a check is "no" added
Updated by François ARMAND about 5 years ago
- Status changed from New to Rejected
- Priority changed from 79 to 77
I'm closing that one to keep all messages under #8683.