You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The end result is that all disks come back as "bluestore" which matches the desired configuration, so no OSD gets removed and recreated. The disk_format and journal above are correct for the pillar, but not the actual OSD.
This is related to bnc:1157549.
The text was updated successfully, but these errors were encountered:
Description of Issue/Question
For anybody reading this, the workaround is to remove and deploy the osd as two steps.
The comparison in
osd.is_incorrect
is relying on the pillar. I don't see a quick fix for this.Here's one example, although many existed in this particular installation. The grains are correct for
and lists a filestore OSD. Here are the corresponding snipped logs from an
osd.redeploy
runThe
is_incorrect
uses the OSDConfig which inspects the pillar and not the actual disk. The pillar part isThe end result is that all disks come back as "bluestore" which matches the desired configuration, so no OSD gets removed and recreated. The disk_format and journal above are correct for the pillar, but not the actual OSD.
This is related to bnc:1157549.
The text was updated successfully, but these errors were encountered: