Can't attach or boot nova volumes backed by cinder ceph rbd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-cinder |
Won't Fix
|
Undecided
|
Unassigned | ||
puppet-nova |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I'm reusing/rewriting bug reports from fellow config management tools [1][2]
> https:/
> change in Ocata where any data provided by cinder for rbd block devices is preferred over any local
> libvirt sectional configuration for rbd (which was used in preference in the past).
> Username on the compute units won't match the username for ceph being used on the cinder units (as
> compute and cinder units get different keys created) so I don't think the key created on the compute
> units will actually work with the username provided from cinder.
> As a result, isn't possible to attach ceph block devices in instances in a puppet deployed Ocata;
Main point here is the absence of virsh-secret with cinder ceph-auth-secret on nova-compute. Nova computes try to attach cinder volume using this xml with ceph usename cinder instead of nova.
> <disk type="network" device="disk">
> <driver name="qemu" type="raw" cache="writeback" discard="unmap"/>
> <source protocol="rbd" name="cinder_
> <host name="192.
> </source>
> <auth username="cinder">
> <secret type="ceph" uuid="4d317a47-
> </auth>
> <target bus="virtio" dev="vdb"/>
> </disk>
Since cinder-
[1]https:/
[2]https:/
I've fixed that using the same ceph-auth-key for both cinder and nova ceph-user, that way, when nova tries to attach a volume using cinder-ceph-user and nova-libvirt-secret it will match and work.