upgrade-charm --force behavior causes races
Bug #1475509 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
Running 'juju upgrade-charm --force' returns immediately, rather than waiting until the code has actually been pushed to the affected units. This means that the very popular iterative debugging cycle of 'juju upgrade-charm --force foo; juju resolved --retry foo/0' will sometimes trigger the failed hook to be retried before the code has been updated.
The easiest workaround is to add a sleep between the commands, which reduces the probability of the race being triggered. A better work around may be to inspect the unit status, but I have not investigated if the unit status can tell us when the upgrade-charm --force has completed.
| tags: | added: race-condition upgrade-charm |
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| no longer affects: | juju-core |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.