bootstrap-source relation should provide sanity check for compatible ceph version
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ceph Monitor Charm |
Triaged
|
Medium
|
Unassigned | ||
| OpenStack Ceph Charm (Retired) |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
In the field as I was migrating from charm-ceph to charm-ceph-mon on a trusty-mitaka cloud, I deployed cs:trusty/ceph-mon, then juju add-relation ceph-mon ceph (which auto-relates on bootstrap-source interface).
On the ceph application, the source was set to a UCA link cloud:trusty-
After expanding ceph-mon to 3 units with juju add-unit -n 2 ceph-mon, we found that the 3 ceph-mon nodes had clustered and show 4 mons with 1 mon down and 0 OSDs, but the ceph/0 unit still had only 1 mon defined in ceph status and in /etc/ceph/ceph.conf even after properly being triggered in the relation.
I believe it would be beneficial to the product user base to alert to operator error by providing a sanity check for version of ceph-mon on either side of the bootstrap-source interface before succeeding on bootstrap-
| Drew Freiberger (afreiberger) wrote | #1 |
| Ryan Beisner (1chb1n) wrote | #2 |
| Ryan Beisner (1chb1n) wrote | #3 |
| Changed in charm-ceph: | |
| status: | New → Won't Fix |
| Changed in charm-ceph-mon: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
To reproduce:
juju deploy cs:trusty/ceph --config monitor-count=1 --config source=
juju deploy ceph-osd
juju add-relation ceph-osd ceph
juju deploy cs:trusty/ceph-mon --config no-bootstrap=true
juju add-unit ceph-mon -n 2
This should present the error state. This is from the top of my head and not proven to repro.