I noticed in the logging of the nova debug change related to this that the volume coming back to nova has encrypted=True but the connection_info['data'] dict doesn't:
With this change I noticed that nothing is being logged anymore, yet the warning above wasn't being logged either.
Apparently that's because the connection_info['data'] dict doesn't contain the 'encrypted' key in the ceph case:
So it seems we have some issues with the connection_info coming back from the cinder API after initializing the connection, cinder doesn't thing the volume is encrypted - maybe in the ceph case it's not, hence the bug.
I noticed in the logging of the nova debug change related to this that the volume coming back to nova has encrypted=True but the connection_ info['data' ] dict doesn't:
With this change I noticed that nothing is being logged anymore, yet the warning above wasn't being logged either.
Apparently that's because the connection_ info['data' ] dict doesn't contain the 'encrypted' key in the ceph case:
http:// logs.openstack. org/99/ 189799/ 2/check/ check-tempest- dsvm-full- ceph/353db23/ logs/screen- n-cpu.txt. gz#_2015- 06-09_18_ 21_16_723
However, the volume does have the encrypted value set to True: logs.openstack. org/99/ 189799/ 2/check/ check-tempest- dsvm-full- ceph/353db23/ logs/screen- n-cpu.txt. gz#_2015- 06-09_18_ 21_16_217
http://
So it seems we have some issues with the connection_info coming back from the cinder API after initializing the connection, cinder doesn't thing the volume is encrypted - maybe in the ceph case it's not, hence the bug.