charm remains in maintenance status if charm is restarted while "Restarting services"

[Drew Freiberger]

The LSctl class in hooks/lib/callbacks/scripts.py has code that will set maintenance state for Restarting Services, but if those restarts hang, or the agent is restarted or reconfigured while that's happening, it appears that the maintenance state is stuck permanently:

landscape-server/1 maintenance idle 32 10.55.0.214 Restarting services.

This has been the status for 3 days. no hooks I run will reset this status. It appears that there's a setting to "if current status is maintenance, return" instead of restarting or resetting the state of the charm.

The services are running and all is well with the unit, this is just a status display issue.

[Vern Hart (vern)]

I have also seen this in a customer deployment.

We added the license with juju config and while landscape-server/0 is now active/idle, the other two units are maintenance/idle with "Restarting services."

There doesn't seem to be a way to clear this status.

[Simon Poirier (simpoir)]

FTR, forcing the units to restart should clear the status, when it gets stuck :

  juju run-action landscape-server/<unit> resume --wait