yahoo-eng-team team mailing list archive

[Jiong Liu <liujiong@xxxxxxxxxxxxx>]

Public bug reported:

I created a volume in cinder which was encryped with barbican. 
Then I tried to attach this volume to a vm using command "nova volume-attach vm2 15d7b84a-9f08-4aac-9fcf-495ede08593c /dev/vdc", it failed.
After debugging, I found the secret_ref created in nova was wrong.
The secret_ref returned here https://github.com/openstack/nova/blob/stable/mitaka/nova/keymgr/barbican.py#L308 was "http://controller:9311/secrets/00000000-0000-0000-0000-000000000000";.
In fact, it should contain barbican version number "v1", which means the secret_ref should be "http://controller:9311/v1/secrets/00000000-0000-0000-0000-000000000000";.
My dev env is "stable/mitaka".
Any further information will be attached if needed.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1599385

Title:
  barbican's secret_ref created by nova misses barbican version

Status in OpenStack Compute (nova):
  New

Bug description:
  I created a volume in cinder which was encryped with barbican. 
  Then I tried to attach this volume to a vm using command "nova volume-attach vm2 15d7b84a-9f08-4aac-9fcf-495ede08593c /dev/vdc", it failed.
  After debugging, I found the secret_ref created in nova was wrong.
  The secret_ref returned here https://github.com/openstack/nova/blob/stable/mitaka/nova/keymgr/barbican.py#L308 was "http://controller:9311/secrets/00000000-0000-0000-0000-000000000000";.
  In fact, it should contain barbican version number "v1", which means the secret_ref should be "http://controller:9311/v1/secrets/00000000-0000-0000-0000-000000000000";.
  My dev env is "stable/mitaka".
  Any further information will be attached if needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1599385/+subscriptions