with multiple pools the keyrings are not copied over

Bug #1803526 reported by Wouter van Bommel
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Cinder Charm
Expired
Low
Unassigned

Bug Description

[Impact]
If in an cloud multiple cinder pools are setup, using multiple ceph stores. The client key's don't get synced between the servers in the pool.
This makes it impossible to migrate a volume from one pool to another.

[Test Case]
1. deploy openstack env(https://pastebin.ubuntu.com/p/yPN5rbCFp2/)
2. manual ceph setup on cinder-b
- TBD
3. create 2 volume-types ( A, B )
- openstack volume create type A
- openstack volume create type B
4. set backend name to type A, B
- openstack volume type set A --property volume_backend_name=cinder-ceph
- openstack volume type set B --property volume_backend_name=cinder-backup
5. create volume with volume-type 1
6. change volume-type #4 volume
- openstack volume set --type B --retype-policy on-demand test
7. you can see error like below in cinder-b
- https://pastebin.ubuntu.com/p/hjpQwcSQD6/

[Others]
Copying keyring files between cinder & cinder-b solves this issue.

The keyring file involved, are those needed to access the ceph volumes

Seyeong Kim (seyeongkim)
description: updated
tags: added: sts
Revision history for this message
Chris MacNaughton (chris.macnaughton) wrote :

Can you please add more details about the error in cinder-b (#6)?

Which keyrings are we talking about? The Ceph keyrings for each application?

description: updated
Revision history for this message
Seyeong Kim (seyeongkim) wrote :

Hello Crhis

Added pastebin snippet

description: updated
description: updated
Revision history for this message
James Page (james-page) wrote :

Looking at the bundle, I'm unclear as to why the second cinder principle (cinder-b) is in use; the cinder-backend and cinder-ceph suboridinates can be related to the same principle cinder charm application, ensuring that cinder services have access to all of the keys that they need.

Revision history for this message
James Page (james-page) wrote :

Also I don't think 'cinder-backend' is a valid backend name:

openstack volume type set B --property volume_backend_name=cinder-backup

cinder-backup is a discrete set of functionality within cinder, not an additional backend.

Changed in charm-cinder:
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Seyeong Kim (seyeongkim) wrote :

important thing is not cinder-backend but it has different pool

I'll upload different bundle which has the same issue

Thanks.

Seyeong Kim (seyeongkim)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in charm-cinder:
status: Incomplete → Expired
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.