Actions
Bug #8049
closedrudder-webapp and rudder-slapd does not register themself on boot on Debian 7
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When installing 2.11.19, on a debian 7, I get no reports for check on boot rudder-jetty and rudder-slapd
Indeed, there are no /etc/rc2.d/S.*rudder-jetty nor rudder-slapd
so service is not registered at boot
There is no report, because we are promising on an empty promiser (file is not there -> nothing to promise -> no class created -> no repair)
This may happen also on 3.0, 3.1 and 3.2
Updated by Nicolas CHARLES over 8 years ago
Ok, this happened already in 2.11.17
Updated by Nicolas CHARLES over 8 years ago
- Related to Bug #6833: System techniques tries to add old services at boot added
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.20 to 2.11.21
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.21 to 2.11.22
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.22 to 2.11.23
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.23 to 2.11.24
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.24 to 308
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 308 to 3.1.14
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Benoît PECCATTE over 7 years ago
- Status changed from New to Rejected
2.11 is not supported anymore
Actions