OpenStack provider: Juju storage failing due to different availability zones
Bug #1885639 reported by
Haw Loeung
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
Hi,
Splitting this out from LP:1884018.
In Juju 2.7 and beyond, code was added to detect availability zones (AZ) and to try bring up storage in the same AZ. Unfortunately, in some cases, there may be more than one AZ for compute but yet a single AZ for storage / cinder. In these cases, deploy fails with storage stuck in 'pending' and unit agents stuck in 'initializing' blocked on storage.
| Changed in juju: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| milestone: | none → 2.7.8 |
| importance: | Undecided → High |
| status: | New → In Progress |
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
| Changed in juju: | |
| status: | Fix Released → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/