Public bug reported:
Found the below issue with HPE driver but appears applicable to all.
Pre-requisites:
1) Volume migration requires that you have the Dynamic Optimization license
installed on the HPE 3PAR Storage array.
2) 3parFC-1 and 3parFC-2 backends must be configured and enabled with
encryption (LuksEncryptor).
3) 3parFC-1 and 3parFC-2 backends have the same volume_backend_name in the
cinder.conf.
4) Volume type of 3parFC-1 must contain ""thin"" provisioning type and "minBWS1
and minIOPS1" QoS settings.
5) Volume type of 3parFC-2 must contain ""full"" provisioning type and "minBWS2
and minIOPS2" QoS settings.
Steps to Reproduce:
1. SSH Devstack Host IP using SSH Client via Valid user credentials.
2. Create a volume <volume1> with volume type 3parFC-1.
Run this command: cinder create --volume-type 3parFC-1 --name volume1 <size>
3. Perform Volume Retype.
Run the command: cinder retype --migration-policy on-demand <volume1> <3parFC-2
volume type>
4. Verify the retyped volume in 3par array via CLI using valid user credentials.
Run this command: showvv
5. Verify the volume type for <volume1>.
Run this command: cinder show <volume>
Expected Result:
Volume1 must be retyped and displayed in 3par array with correct details
of provisioning type and QoS settings of 3parFC-2 volume type.
Observed Result:
Volume retype fails with error “ERROR: Invalid input received: Retype
cannot change encryption requirements”.
** 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/1662401
Title:
Volume Retype with encryption fails.
Status in OpenStack Compute (nova):
New
Bug description:
Found the below issue with HPE driver but appears applicable to all.
Pre-requisites:
1) Volume migration requires that you have the Dynamic Optimization license
installed on the HPE 3PAR Storage array.
2) 3parFC-1 and 3parFC-2 backends must be configured and enabled with
encryption (LuksEncryptor).
3) 3parFC-1 and 3parFC-2 backends have the same volume_backend_name in the
cinder.conf.
4) Volume type of 3parFC-1 must contain ""thin"" provisioning type and
"minBWS1 and minIOPS1" QoS settings.
5) Volume type of 3parFC-2 must contain ""full"" provisioning type and
"minBWS2 and minIOPS2" QoS settings.
Steps to Reproduce:
1. SSH Devstack Host IP using SSH Client via Valid user credentials.
2. Create a volume <volume1> with volume type 3parFC-1.
Run this command: cinder create --volume-type 3parFC-1 --name volume1 <size>
3. Perform Volume Retype.
Run the command: cinder retype --migration-policy on-demand <volume1>
<3parFC-2 volume type>
4. Verify the retyped volume in 3par array via CLI using valid user
credentials.
Run this command: showvv
5. Verify the volume type for <volume1>.
Run this command: cinder show <volume>
Expected Result:
Volume1 must be retyped and displayed in 3par array with correct
details of provisioning type and QoS settings of 3parFC-2 volume type.
Observed Result:
Volume retype fails with error “ERROR: Invalid input received: Retype
cannot change encryption requirements”.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1662401/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
