Working in my first RBD bug

The cinder manage command it’s only for independent rbd volumes. However, manage an already-managed volumes is allow by the api and there’re not exception raised.

When you try to manage an already-managed volume, you received an unhandled error: ‘UnboundLocalError: local variable ‘rbd_image’ referenced before assignment’

How to reproduce:
1)Create a volume:
‘cinder create 1 –name vol1’
2) try to manage the volume (you can check the host with ‘cinder show <vol1’s ID>’):
cinder manage <vol1’s host> <vol1’s ID>
3) On the c-vol you can appreciate the unhandled error.
When this happens the RBD driver should handle the error.

The RBD driver should catch the exception and show a custom message notifying the user.

So, trying to handle the problem inside the rbd driver.

Continue reading “Working in my first RBD bug”

Let’s play with Cinder and RBD (part 1)

After you ./stack (you may have a cluster issue):

(1) You need to check out your ceph configuration and see if everything is ok.

~/devstack$sudo ceph -s
  cluster <uuid>
  health HEALTH_OK

To check the size of your cluster:

~/devstack$ceph df

Continue reading “Let’s play with Cinder and RBD (part 1)”

Solving issue with Ceph cluster (devstack)

If this is your first time, just ./stack:

~/devstack$ ./ 

Otherwise  you need to check  your  Ceph cluster and if you have one, remove it with virsh:

What is libvirt? Libvirt is collection of software that provides a convenient way to manage virtual machines and other virtualization functionality, such as storage and network interface management. These software pieces include an API library, a daemon (libvirtd), and a command line utility (virsh).

To check we can just use this command:  virsh secret-list (No need to do it inside devstack directory) and remove it with : virsh secret-undefine <UUID>

~/devstack$ virsh secret-list
~/devstack$ virsh secret-undefine <uuid>

Captura de pantalla de 2016-07-06 22:33:07

Finally you will have something like this:

Captura de pantalla de 2016-07-06 22:17:08

In my case, i need to

~/devstack$ ./clear
~/devstack$ ./unstack

to completely solve the problem, but maybe you don’t.