Wording around osd-devices option can be improved

Bug #2008219 reported by Robert Holling
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Charms Deployment Guide
Fix Released
Low
Peter Matulis

Bug Description

[x] This doc is inaccurate in this way:

the first juju deploy command for the ceph-osd nodes refers to the ceph-osd.yaml file with the osd-devices /dev/sda /dev/sdb /dev/sdc /dev/sdd. As I tried this with /dev/sda, my deployment crashed. I deleted /dev/sda in the yaml file (because of this is the os-device in my case), and everything went well. As I saw, in the documentation for the YOGA-Release, the /dev/sda hadn't been named.

My four machines for ceph-osd have five devices: sda for os, sdb, sdc, sdd and sde for ceph-osd. Should there be a hint, to take care and have a look into MAAS onto the storage of the nodes?

-----------------------------------
Release: on 2023-02-17 19:50:01
SHA: 1e3c10016f6014220e5fc0a41e426504a2cd2a14
Source: https://opendev.org/openstack/charm-deployment-guide/src/deploy-guide/source/install-openstack.rst
URL: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/zed/install-openstack.html

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

Hi Robert,

The Ceph charms are designed to not clobber a device that is currently in use so it sounds like you may have hit an important software bug. If you could dig into that it would be appreciated. You would probably file that bug against the ceph-osd charm. Its bug tracker is here:

https://bugs.launchpad.net/charm-ceph-osd/+filebug

I will still include a note to have the user check the MAAS nodes as you suggested.

Changed in charm-deployment-guide:
importance: Undecided → Low
assignee: nobody → Peter Matulis (petermatulis)
Revision history for this message
Peter Matulis (petermatulis) wrote :

Looking again, the guide does state:

"The name of the block devices backing the OSDs is dependent upon the hardware on the nodes. All possible devices across the nodes should be given as the value for the osd-devices option."

Is this what you were looking for? Or maybe:

"The names of the block devices backing the OSDs is dependent upon the hardware on the nodes. All possible devices (across all the nodes) that are to be used for Ceph storage should be given as the value for the osd-devices option."

Changed in charm-deployment-guide:
status: New → Triaged
Revision history for this message
Robert Holling (rholling) wrote :

Hi Peter,
sorry for my delayed response.

Our installation has gone, so I have to look, if we will be able to re-install like Feb, 17th, with the intention, to reproduce my described results. No promises for that, sorry.

Reg. your 2nd notice: I would prefer the second statement - but that's only my opinion, so...?!

Thanks for your help.
Robert

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-deployment-guide (master)
Changed in charm-deployment-guide:
status: Triaged → In Progress
summary: - Install OpenStack in charm-deployment-guide
+ Wording around osd-devices option can be improved
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-deployment-guide (master)

Reviewed: https://review.opendev.org/c/openstack/charm-deployment-guide/+/880556
Committed: https://opendev.org/openstack/charm-deployment-guide/commit/f56719413464609e65769f710730837676cf4ee7
Submitter: "Zuul (22348)"
Branch: master

commit f56719413464609e65769f710730837676cf4ee7
Author: Peter Matulis <email address hidden>
Date: Fri Apr 14 18:13:07 2023 -0400

    Reword osd-devices option usage

    Slightly reword the text describing how to determine the
    value of the osd-devices option (ceph-osd charm).

    Closes-Bug: #2008219
    Change-Id: I7512d62574f60db3f415ae39757b2a158d559527

Changed in charm-deployment-guide:
status: In Progress → Fix Released
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.