Ceph Base deploys ceph-osd units blocked

Bug #1982861 reported by David Gomez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Bundles
New
Undecided
Unassigned

Bug Description

When deploying the Ceph Base bundle on virtual maas per the onboarding instructions, the ceph-osd units are in the blocked state(see attached screenshot).

Workaround:
Had to zap the /dev/vdb disks and add them again per ceph-osd/0-2 (where * represents 0-2)
$ juju run-action --wait ceph-osd/* zap-disk devices=/dev/vdb i-really-mean-it=true
$ juju run-action --wait ceph-osd/* add-disk osd-devices=/dev/vdb

After doing the above I was able to use the ceph-osd units to create a storage pool and create an rbd image inside the pool.

Revision history for this message
David Gomez (dvgomez) wrote :
Revision history for this message
Luciano Lo Giudice (lmlogiudice) wrote :

Hello David,

could you share the bundle that you used for the deployment ?

Revision history for this message
David Gomez (dvgomez) wrote : Re: [Bug 1982861] Re: Ceph Base deploys ceph-osd units blocked

Hi Luciano,

The bundle I used was https://charmhub.io/ceph-base

Thanks,
Dave

On Tue, Jul 26, 2022 at 10:25 AM Luciano Lo Giudice <
<email address hidden>> wrote:

> Hello David,
>
> could you share the bundle that you used for the deployment ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1982861
>
> Title:
> Ceph Base deploys ceph-osd units blocked
>
> Status in OpenStack Bundles:
> New
>
> Bug description:
> When deploying the Ceph Base bundle on virtual maas per the onboarding
> instructions, the ceph-osd units are in the blocked state(see attached
> screenshot).
>
> Workaround:
> Had to zap the /dev/vdb disks and add them again per ceph-osd/0-2 (where
> * represents 0-2)
> $ juju run-action --wait ceph-osd/* zap-disk devices=/dev/vdb
> i-really-mean-it=true
> $ juju run-action --wait ceph-osd/* add-disk osd-devices=/dev/vdb
>
> After doing the above I was able to use the ceph-osd units to create a
> storage pool and create an rbd image inside the pool.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-bundles/+bug/1982861/+subscriptions
>
>

Revision history for this message
Luciano Lo Giudice (lmlogiudice) wrote :

The issue seems to be that the disk provided during deploy was not in a pristine state; this is required by the ceph-osd charm to use it as a backing device.

If your virtual MAAS has cinder or any other volume handler, you can use the 'osd-devices' item under 'storage' to specify the number of volumes and their size. Otherwise, for device paths, you have to make sure that they are pristine (i.e: have been zapped, as you did).

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.