Nova conf hardcoded to 'nova' user with 'external ceph'

Bug #1745441 reported by Nathan Harper
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Wishlist
Unassigned

Bug Description

When using the 'external ceph' functionality, the ceph usernames and pools can be configured for each Openstack service.

For nova, it is looking explicitly for keyrings called ceph.client.nova.keyring and ceph.client.cinder.keyring.

If you are using an existing Ceph cluster, there is a good chance that you will not be able to use the default usernames.

Changed in kolla-ansible:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Nathan Harper (nathharp) wrote :

If you can remind me of the process, I'm pretty sure I could patch this

Revision history for this message
Tom Fifield (fifieldt) wrote :

This appears to be fixed in current versions:

1082 # External Ceph keyrings
1083 ceph_cinder_keyring: "ceph.client.cinder.keyring"
1084 ceph_cinder_backup_keyring: "ceph.client.cinder-backup.keyring"
1085 ceph_glance_keyring: "ceph.client.glance.keyring"
1086 ceph_gnocchi_keyring: "ceph.client.gnocchi.keyring"
1087 ceph_manila_keyring: "ceph.client.manila.keyring"
1088 ceph_nova_keyring: "{{ ceph_cinder_keyring }}"

Changed in kolla-ansible:
status: Triaged → Fix Released
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.