Marked as invalid, OP indicated they had resolved the issue.
** Changed in: nova
Status: Incomplete => Invalid
** Changed in: cinder
Status: New => Invalid
--
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/1580294
Title:
Impossible to create another iSCSI volume after encrypted one was
created
Status in Cinder:
Invalid
Status in OpenStack Compute (nova):
Invalid
Bug description:
Description
===========
Tempest test for Cinder drivers which uses encrypted volumes fails. I figured
out that test uses nova.volume.encryptors.cryptsetup.CryptsetupEncryptor.
On setup it executes:
cryptsetup create --key-file=- dev_name dev_path
ln --symbolic --force /dev/mapper/dev_name symlink_path
On remove:
cryptsetup remove dev_name
and it doesn't restore the link. When a driver deletes a volume and creates
anoter one with the same name as previous, that link becomes broken and volume
is not able to be working. When I manually replace the link with original one,
it works fine.
Steps to reproduce
==================
cd /opt/stack/tempest
tox -eall -- --concurrency=1 test_encrypted_cinder_volumes_cryptsetup
run the test twice
Expected result
===============
the test passes every time
Actual result
=============
the test passes only the first time
Environment
===========
I used devstack from master branch and Nexenta iSCSI driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1580294/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
