Originally I thought it was not applicable to Canonical's ~field-high since there was a workaround. However, this issue hit every single field deployment with Pike+ and caused a lot of confusions. Broken Ceph status out of the box is hard to be justified, so ~field-high is now appropriate for faster resolution I believe.
Subscribing ~field-high.
Originally I thought it was not applicable to Canonical's ~field-high since there was a workaround. However, this issue hit every single field deployment with Pike+ and caused a lot of confusions. Broken Ceph status out of the box is hard to be justified, so ~field-high is now appropriate for faster resolution I believe.