© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
We'll need to see some additional info to help diagnose the issue:
- the content of the unitstates collection relevant to the affected unit
- the content of the action and actionnotifications collections relevant to the pending task
- the content of the operations collection relevant to the pending operation
- logging for the affected unit agent with "juju.worker.
There's been a couple of fixes landed to better handle orphaned actions, ie those actions which the unit might be executing but the action record no longer exists in state. Juju 3.1.6 should have the earlier fixes. There's a recent one
https:/
But that handled the case where an action had already been started, not pending. It might be that the fix is also relevant to this case. But we'd need to first see via the info above what actions are queued to run for the unit and whether the actions are stored in the db.