LVM/iSCSI storage method does not work

It looks like vdb in particular was causing the problem. It works for another existing device (vdc) and it works for a newly-created-and-added disk (vdd).

This bug needs reopening. My successful tests were feeding off the scenario that involved manual adjustments.

The only way I can get a successful volume created in OpenStack is by making the manual adjustments on the node and then deploying the charm (making sure to configure with the correct block device). Merely re-configuring the charm (juju config) did not work for me.

Hi,

Could you please provide more information:

Openstack version
Deployment bundle
Particular juju config you're using
Documentation you're following

Ideally the information you provide here should enable me or someone else to replicate the issue without having to do any research.

Documentation is the Cinder charm README:

https://opendev.org/openstack/charm-cinder/src/branch/master/README.md#user-content-storage-backed-by-lvm-iscsi

OpenStack version is Train.

There is no deployment bundle.

There is no Juju configuration beyond what's been used in the above documentation or the cinder.yaml file in the pastebin.

If it worked for /dev/vdc but not for /dev/vdb then there's something different about /dev/vdb that the charm is perhaps choosing not to do it.

Please, if you get time, could you post the ubuntu version, openstack version, charm version (or indicate if next) and the FULL log files for the cinder unit. Thanks.

Alex. I wrote this in a later comment:

"The only way I can get a successful volume created in OpenStack is by making the manual adjustments on the node and then deploying the charm (making sure to configure with the correct block device). Merely re-configuring the charm (juju config) did not work for me."

> "The only way I can get a successful volume created in OpenStack is by making the manual adjustments on the node and then deploying the charm (making sure to configure with the correct block device). Merely re-configuring the charm (juju config) did not work for me."

Yes, and it would be useful to know why the cinder charm took no action. The full cinder log might give a clue as to what's going on. I suspect it's a test environment issue with /dev/vdb and the charm deciding not to do something with it. This is based on the idea that you said it worked fine for the /dev/vdc block device.

FYI I had similar issues on ServerStack and solved it by:

1. Making sure that /dev/vdb didn't get mounted by default by using this fix [0]
2. Setting the config option 'overwrite' [1] to 'true'.

[0] https://github.com/openstack-charmers/charm-test-infra/commit/778f9b94
[1] https://github.com/openstack/charm-cinder/blob/master/config.yaml#L76

[Expired for OpenStack cinder charm because there has been no activity for 60 days.]

I'm facing this issue with cinder-304.
I tried to use the workaround in #8, adapted to my scenario, but with no success.
The charm will not initialize the LVM requiring manual intervention.
I ended up using cinder-lvm [1] charm for handling the LVM automatically.

[1] https://jaas.ai/u/andre-ruiz/cinder-lvm