"upgrade in progress" errors persist forever on an API connection
Bug #1772381 reported by
Roger Peppe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
If a client happens to connect to a controller when it's being upgraded,
it gets an API root that's forever restricted to upgrade methods
only, even though the upgrade itself might complete in a short time.
See https:/
This means that clients that make long-term API connections, such as JIMM,
see persistent errors when a controller has been upgraded.
ISTM that the set of methods available on an API connection should
reflect the connected client, not the server state, so when the server
has successfully upgraded, the available methods should be unrestricted
without the need for a client to make a new connection.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.4-beta3 |
Changed in juju: | |
milestone: | 2.4-beta3 → none |
To post a comment you must log in.
Or, could Juju close all client connections after upgrading? That might be a lot simpler.