| 2021-07-02 14:11:18 |
Adam Dyess |
bug |
|
|
added bug |
| 2021-07-02 14:11:53 |
Adam Dyess |
bug task added |
|
charm-neutron-gateway |
|
| 2021-07-02 14:12:18 |
Adam Dyess |
bug task added |
|
charm-neutron-openvswitch |
|
| 2021-07-02 14:12:35 |
Adam Dyess |
bug task added |
|
charm-rabbitmq-server |
|
| 2021-07-02 14:12:38 |
Facundo Ciccioli |
description |
the use of charm specific files in /etc/policy-rc.d/ to prevent services from restarting during
a package upgrade (or other charm services) also prevents those from starting up when the machine is rebooted.
Combined with LP#1934406, the charm presents a very friend "active/idle" when in reality there are necessary services not running requiring the restart actions to be run.
Can you conceive of some way to monitor or signal that there are vital services not running after a reboot, or even better ensure services are running after a machine reboot? |
the use of charm specific files in /etc/policy-rc.d/ to prevent services from restarting during
a package upgrade (or other charm services) also prevents those from starting up when the machine is rebooted.
Combined with LP#1934406, the charm presents a very friendly "active/idle" when in reality there are necessary services not running requiring the restart actions to be run.
Can you conceive of some way to monitor or signal that there are vital services not running after a reboot, or even better ensure services are running after a machine reboot? |
|
| 2021-07-02 14:12:48 |
Adam Dyess |
bug task added |
|
charm-ovn-central |
|
| 2021-07-02 14:12:55 |
Facundo Ciccioli |
description |
the use of charm specific files in /etc/policy-rc.d/ to prevent services from restarting during
a package upgrade (or other charm services) also prevents those from starting up when the machine is rebooted.
Combined with LP#1934406, the charm presents a very friendly "active/idle" when in reality there are necessary services not running requiring the restart actions to be run.
Can you conceive of some way to monitor or signal that there are vital services not running after a reboot, or even better ensure services are running after a machine reboot? |
The use of charm specific files in /etc/policy-rc.d/ to prevent services from restarting during a package upgrade (or other charm services) also prevents those from starting up when the machine is rebooted.
Combined with LP#1934406, the charm presents a very friendly "active/idle" when in reality there are necessary services not running requiring the restart actions to be run.
Can you conceive of some way to monitor or signal that there are vital services not running after a reboot, or even better ensure services are running after a machine reboot? |
|
| 2021-07-02 14:13:02 |
Adam Dyess |
bug task added |
|
charm-ovn-dedicated-chassis |
|
| 2021-07-02 14:40:44 |
Adam Dyess |
summary |
deferred restarts prevent a rebooted machine from starting services |
deferred restarts provide incorrect charm status after machine reboots |
|
