Actions
Bug #6002
closed
Services management 2.0 reports unknown status when disabling a service at start
Added by Nicolas CHARLES over 9 years ago. Updated almost 7 years ago.
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Priority:
36
Name check:
Fix check:
Regression:
Description
With services management 2.0, i get a unknow report when config is repaired
Service starting parameters, with the following reports:
iptables
iptables has been prevented to start on boot
iptables is not started on boot as required
On rudder 2.11, but may happen on 2.10
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.11.6 to 2.11.7
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.11.7 to 2.11.8
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.11.8 to 2.11.9
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.11.9 to 2.11.10
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.11.10 to 2.11.11
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.11.11 to 2.11.12
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.11.12 to 2.11.13
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.13 to 2.11.14
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.14 to 2.11.15
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.15 to 2.11.16
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.16 to 2.11.17
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.17 to 2.11.18
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.18 to 2.11.19
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.19 to 2.11.20
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.20 to 2.11.21
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 2.11.21 to 2.11.22
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 2.11.22 to 2.11.23
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 2.11.23 to 2.11.24
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 2.11.24 to 308
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 308 to 3.1.14
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by François ARMAND about 7 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Getting started - demo | first install | level 1 Techniques
- Effort required set to Small
- Priority set to 36
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Alexis Mousset almost 7 years ago
- Status changed from New to Rejected
In the 3.0 version this is now handled by ncf, which correctly reports repair case.
Closing.
Actions