Creating a mixture of non-encrypted and encrypted units does not work
Bug #1916496 reported by
Steven Parker
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ceph OSD Charm |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
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.
Revision history for this message
| Alex Kavanagh (ajkavanagh) wrote | #1 |
| Changed in charm-ceph-osd: | |
| status: | New → Incomplete |
Revision history for this message
| Steven Parker (sbparke) wrote | #2 |
Revision history for this message
| Steven Parker (sbparke) wrote | #3 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in charm-ceph-osd: | |
| status: | Incomplete → Expired |
| Changed in charm-ceph-osd: | |
| status: | Expired → Triaged |
| importance: | Undecided → Medium |
To post a comment you must log in.
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.