Creating a mixture of non-encrypted and encrypted units does not work

[Steven Parker]

We started out with ceph-osd deployed with encryption off then attempted to expand this set of units with encrypt set to true. Everything looked good at that point.

However late on...

This failed after a config changed event as the non encrypted drives are now trying to use vault keys that were never registered.

This could impact expansion efforts on other clouds.

Replicate with :

Deploy ceph-osd with encryption off
Add new unit with encryption on.

Generate config changed event and you should see the exception.

Sorry the customer had already worked around this issue with two seperate ceph-osd applications one with encryption on and one with encryption off. But this took some time to back out from once we encountered the issues.

[Alex Kavanagh (ajkavanagh)]

Hi there. Thanks for the bug report. Please could you add:

Ubuntu version
OpenStack version
Charms version (release or -number)
The bundle that deployed this (sanitised as needed, please)
juju version

Thanks.

[Steven Parker (sbparke)]

bionic/stein
juju 2.6.7

charms

cs:ceph-osd-301
cs:ceph-mon-46
cs:vault-37

I'll try and replicate this with a generic bundle later

[Steven Parker (sbparke)]

Ok I tried to replicate the bug with no success with a new bundle.

As a work around to avoid the issue we simply split the osd units into a encrypted and unencrypted charm deployment and added them later to the same ceph pool.

[Launchpad Janitor (janitor)]

[Expired for OpenStack ceph-osd charm because there has been no activity for 60 days.]