yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #78559
[Bug 1829854] [NEW] volume_type not supported in version 2.72
Public bug reported:
Description
===========
>From https://developer.openstack.org/api-ref/compute/?expanded=create-server-detail#create-server, i see
'volume_type' supported in version 2.67.
>From CLI 'nova help boot'
volume_type=type of volume to
create (either ID or name) when source is
blank, image or snapshot and dest is volume
(optional). (Supported by API versions '2.67'
- '2.latest')
But when i used the 2.latest to test, got unsupported in 2.72
# nova --os-compute-api-version 2.latest boot --flavor m1.tiny --image cirros-0.4.0-x86_64-disk --nic net-id=ec4a4958-7666-4bc0-9329-ce4d571d39a5 --block-device source=blank,dest=volume,volume_type=lvmdriver-1,size=1 test-t
ERROR (CommandError): 'volume_type' in block device mapping is not supported in API version 2.72.
Steps to reproduce
==================
* Setup devstack env
* nova --os-compute-api-version 2.latest boot --flavor m1.tiny --image cirros-0.4.0-x86_64-disk --nic net-id=ec4a4958-7666-4bc0-9329-ce4d571d39a5 --block-device source=blank,dest=volume,volume_type=lvmdriver-1,size=1 test-t
Expected result
===============
Create instance successfully
Actual result
=============
ERROR (CommandError): 'volume_type' in block device mapping is not supported in API version 2.72.
Environment
===========
# git log
commit fc3890667e4971e3f0f35ac921c2a6c25f72adec
Author: OpenDev Sysadmins <openstack-infra@xxxxxxxxxxxxxxxxxxx>
Date: Fri Apr 19 19:45:52 2019 +0000
OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
** 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/1829854
Title:
volume_type not supported in version 2.72
Status in OpenStack Compute (nova):
New
Bug description:
Description
===========
From https://developer.openstack.org/api-ref/compute/?expanded=create-server-detail#create-server, i see
'volume_type' supported in version 2.67.
From CLI 'nova help boot'
volume_type=type of volume to
create (either ID or name) when source is
blank, image or snapshot and dest is volume
(optional). (Supported by API versions '2.67'
- '2.latest')
But when i used the 2.latest to test, got unsupported in 2.72
# nova --os-compute-api-version 2.latest boot --flavor m1.tiny --image cirros-0.4.0-x86_64-disk --nic net-id=ec4a4958-7666-4bc0-9329-ce4d571d39a5 --block-device source=blank,dest=volume,volume_type=lvmdriver-1,size=1 test-t
ERROR (CommandError): 'volume_type' in block device mapping is not supported in API version 2.72.
Steps to reproduce
==================
* Setup devstack env
* nova --os-compute-api-version 2.latest boot --flavor m1.tiny --image cirros-0.4.0-x86_64-disk --nic net-id=ec4a4958-7666-4bc0-9329-ce4d571d39a5 --block-device source=blank,dest=volume,volume_type=lvmdriver-1,size=1 test-t
Expected result
===============
Create instance successfully
Actual result
=============
ERROR (CommandError): 'volume_type' in block device mapping is not supported in API version 2.72.
Environment
===========
# git log
commit fc3890667e4971e3f0f35ac921c2a6c25f72adec
Author: OpenDev Sysadmins <openstack-infra@xxxxxxxxxxxxxxxxxxx>
Date: Fri Apr 19 19:45:52 2019 +0000
OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1829854/+subscriptions
Follow ups