apiserver: pinger can access state before upgrade has completed
Bug #1505309 reported by
Roger Peppe
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
| juju-core |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
The API server is started before upgrades have completed, so
it's potentially problematic if anything accesses the state before
the first API calls have been made. Unfortunately the pinger
is started at the same time as run is called, so runs concurrently
with the upgrader, so may access the pinger collection at the
same time as it is being upgraded.
One solution may be to have a StartPinger method that
starts the pinger, rather than have it starting automatically.
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
Revision history for this message
| Roger Peppe (rogpeppe) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → 2.0.1 |
| Changed in juju: | |
| milestone: | 2.0.1 → none |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This is still a valid bug that really should be fixed.