Barbican with Live Migration issue
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Unassigned |
Bug Description
I am having some issues with key management in a multinode devstack (from master branch 27th July ’18) environment where Barbican is the configured key_manager. I have followed setup instructions from the following pages:
• https:/
• https:/
So far:
• Unencrypted block volumes can be attached to instances on any compute node
• Instances with unencrypted volumes can also be live migrated to other compute node
• Encrypted bootable volumes created successfully
• Instances can be launched using these encrypted volumes when the instance is spawned on demo_machine1 (controller & compute node)
• Instances cannot be launched using encrypted volumes when the instance is spawned on demo_machine2 or demo_machine3 (compute only), the same failure can be seen in nova logs from both compute nodes:
Jul 30 14:35:18 demo_machine2 nova-compute[
Jul 30 14:35:18 demo_machine2 nova-compute[
Jul 30 14:35:18 demo_machine2 nova-compute[
Jul 30 14:35:18 demo_machine2 nova-compute[
All instance of Nova have [key_manager] configured as follows:
[key_manager]
backend = barbican
auth_url = http://
### Tried with and without the below config options, same result
# auth_type = password
# password = devstack
# username = barbican
Any assistance here would be greatly appreciated, I have spent a lot of time looking for some additional information for the use of Barbican in multinode devstack environments or with live migration but there is nothing out there, everything is for all-in-one environments and I’m not having any issues when everything is on one node. I am wondering if at this point there is something I am missing in terms of services in a multinode devstack environment, qualification of barbican in a multinode environment is outside of the recommended test config but following the docs it looks very straight forward.
Some information on the three nodes in my environment are below, if there is any other information I can provide let me know, thanks for the help!
Node & Service Breakdown
Node 1 (Controller & Compute)
stack@demo_
+------
| ID | Name | Type |
+------
| 43a1334c755c4c8
| 52a8927c09154e3
| 5427a9dff3b6477
| 5b319b6d5063466
| 5ffbb2e9f7c84c9
| 787fd29afe2f41b
| 96813e167b8842a
| 993e615a03cc49e
| b3834468ffc44f3
| cab9ff9e175f456
| d12f710b815442f
| eb80de21e42b4e9
+------
stack@demo_
+------
| ID | Region | Service Name | Service Type | Enabled | Interface | URL |
+------
| 00b276609956454
| 18e5d431143d47e
| 20cfe0a80cc94b6
| 3a740b472e7349f
| 4d957921fe894ab
| 4df258794fde476
| 719eabec7cb9458
| 792f4c99085f4b0
| 9e8c27c6e22f4a7
| a271f19f29d443a
| a975403a2ff149b
| b65b46e83b45475
| bfd1f91ba18b4bc
| d38a11dcfe824fe
| ea9139e670e84ff
+------
stack@
+------
| Field | Value |
+------
| Secret href | http://
| Name | None |
| Created | 2018-07-
| Status | ACTIVE |
| Content types | None |
| Algorithm | aes |
| Bit length | 256 |
| Secret type | opaque |
| Mode | cbc |
| Expiration | None |
+------
Node 2 & 3 (Compute Only)
Services:
stack@
<email address hidden> enabled
<email address hidden> enabled
<email address hidden> enabled
stack@
<email address hidden> enabled
<email address hidden> enabled
<email address hidden> enabled
*******