Lost action(s) causing juju run to hang?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
Similar to https:/
I was experimenting with scripted series upgrades (using juju run ...) and running stuff like
watch juju run --machine <list> --timeout 5s -- uptime
Gradually some of the machines are timing out. It seems that new run actions don't execute at all.
I find the respective machine log is full of;
2020-11-03 13:50:45 ERROR juju.worker.
2020-11-03 13:52:47 ERROR juju.worker.
2020-11-03 13:54:58 ERROR juju.worker.
2020-11-03 13:57:04 ERROR juju.worker.
Changed in juju: | |
status: | Incomplete → Triaged |
status: | Triaged → New |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Are the machines in question otherwise responsive? Can you do juju status and see them, juju ssh into them, etc?
If so, then it sounds like we still have a bug in the way that actions are handled. If not, you might be running into a different issue in your cloud, which is manifesting as an issue with actions.
(I've been running a test against my localhost cloud, and have not been able to reproduce the issue. I've only been running the test for a couple of hours, though, and only against one machine.)