An 'expected-osd-count' of 0 does not work

Bug #1886879 reported by Peter Matulis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceph Monitor Charm
Invalid
Undecided
Unassigned

Bug Description

When I deploy 1 ceph-osd unit the ceph-mon application still expects 3. Since I haven't specified a value for (the ceph-mon) option 'expected-osd-count' my understanding is that the default value of '0' will make ceph-mon consider the actual number of OSDs in the cluster, which in my case is 1. When I redo the deployment with 'expected-osd-count=1' it works. That's why I'm saying that an expected-osd-count of 0 does not work the way it's supposed to.

Revision history for this message
Peter Matulis (petermatulis) wrote :
Revision history for this message
Chris MacNaughton (chris.macnaughton) wrote :

Broadly speaking, an OSD count of 1 is invalid, as ceph is designed to have redundancy.

Revision history for this message
Peter Matulis (petermatulis) wrote :

The ceph-mon and ceph-osd charm READMEs will document this better.

Changed in charm-ceph-mon:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.