customize-failure-domain has no effect when ceph-mon is deployed in a container
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Dmitrii Shcherbakov | ||
| 2.2 |
Fix Released
|
High
|
Dmitrii Shcherbakov | ||
| Ceph Monitor Charm |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Let's say I have 3 machines among 3 racks.
node01 - rack01
node02 - rack02
node03 - rack03
And MAAS zones are configured as zone-rack01, 02, 03. In this case, it's quite common to deploy ceph-mon as containers on top of physical nodes and ceph-osd to the hosts. JUJU_AVAILABILI
https:/
As a result, no "step chooseleaf firstn 0 type rack" line in the crush map.
[container]
$ juju run --unit ceph-mon/0 'env | grep JUJU_AVAILABILI
JUJU_AVAILABILI
[physical host]
$ juju run --unit ceph-osd/0 'env | grep JUJU_AVAILABILI
JUJU_AVAILABILI
[juju debug-log -i unit-ceph-mon-2 --replay]
unit-ceph-mon-2: 15:33:28 INFO unit.ceph-
| Chris MacNaughton (chris.macnaughton) wrote | #1 |
| affects: | charm-ceph-mon → juju |
| Tim Penhey (thumper) wrote | #2 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: availability-zones bitesize containers |
| Dmitrii Shcherbakov (dmitriis) wrote | #3 |
| Dmitrii Shcherbakov (dmitriis) wrote | #5 |
| Changed in juju: | |
| assignee: | nobody → Dmitrii Shcherbakov (dmitriis) |
| status: | Triaged → Fix Committed |
| Changed in juju: | |
| milestone: | none → 2.3-alpha1 |
| Nobuto Murata (nobuto) wrote | #6 |
| Changed in charm-ceph-mon: | |
| status: | New → Invalid |
| tags: |
added: cpe-onsite removed: cpec |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
This is a new version of a recurring Juju bug where the JUJU_AVAILABILI