Project

General

Profile

Actions

Bug #15080

closed

Service technique reports a warning after stopping a service

Added by Alexander Brunhirl over 5 years ago. Updated about 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
First impressions of Rudder
Effort required:
Priority:
77
Name check:
Fix check:
Regression:

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

Services_technique.PNG (13.5 KB) Services_technique.PNG Alexander Brunhirl, 2019-06-13 15:50

Related issues 1 (0 open1 closed)

Is duplicate of Rudder - Architecture #8683: check_* methods output error messages when the result of a check is "no"ResolvedActions
Actions #1

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.

Actions #2

Updated by Nicolas CHARLES over 5 years ago

  • Target version set to 5.0.13
Actions #3

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 80 to 79
Actions #4

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
Actions #5

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.

Actions

Also available in: Atom PDF