Upgrade series unit verification race
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
The verification logic for an upgrade-series doesn't take into account fully realised units (subordinate relations).
Considering the following:
$ juju deploy ubuntu
$ juju deploy nrpe
# Wait until everything has settled
$ juju add-relation nrpe ubuntu
$ juju upgrade-series 0 prepare focal
If you time it correctly, the verification will only take into account the units deployed and not units that want to be deployed.
Essentially the verification code doesn't check if all the machine applications relations aren't fully realised (subordinates) as units. If we're missing units then we should error out asking the user to wait until running/idle state.
As we now have a validation state after a machine lock is created, we can ensure this happens correctly.
Changed in juju: | |
milestone: | 2.9.1 → 2.9.2 |
Changed in juju: | |
milestone: | 2.9.2 → 2.9.3 |
Changed in juju: | |
milestone: | 2.9.3 → 2.9.4 |
Changed in juju: | |
milestone: | 2.9.4 → 2.9.5 |
Changed in juju: | |
milestone: | 2.9.5 → 2.9.6 |
Changed in juju: | |
milestone: | 2.9.6 → 2.9.7 |
Changed in juju: | |
milestone: | 2.9.7 → 2.9-next |
Changed in juju: | |
importance: | Low → Medium |
milestone: | 2.9-next → 3.2-beta1 |
Changed in juju: | |
milestone: | 3.2-beta1 → 3.2-rc1 |
Changed in juju: | |
milestone: | 3.2-rc1 → 3.2.0 |
Changed in juju: | |
milestone: | 3.2.0 → 3.2.1 |
Changed in juju: | |
milestone: | 3.2.1 → 3.2.2 |
Changed in juju: | |
milestone: | 3.2.2 → 3.2.3 |
Changed in juju: | |
milestone: | 3.2.3 → 3.2.4 |
Changed in juju: | |
milestone: | 3.2.4 → 3.2.5 |
Changed in juju: | |
milestone: | 3.2.5 → none |
This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.