[Yahoo-eng-team] [Bug 1491325] Re: nova api v2.1 does not allow to use autodetection of volume device path
** Changed in: nova/kilo
Status: Fix Committed => Fix Released
--
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/1491325
Title:
nova api v2.1 does not allow to use autodetection of volume device
path
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) juno series:
Won't Fix
Status in OpenStack Compute (nova) kilo series:
Fix Released
Status in python-novaclient:
Fix Released
Bug description:
Using API v2.1 we are forced to provide device path attaching a volume
to an instance.
using API v2.0 it allowed to provide 'auto' and in this case Nova
calculated it by itself.
It is very useful when we do not care about exact device path.
using APi v2.1 Nova, at first verifies request body [1] and only then
have logic to autodetect "device path". So, either autodetect is dead
code now or request validation should be changed.
For the moment, this bug is blocker for Manila project.
We get one of two errors:
Returning 400 to user: Invalid input for field/attribute device.
Value: None. None is not of type 'string' __call__
or
Returning 400 to user: Invalid input for field/attribute device.
Value: auto. u'auto' does not match
'(^/dev/x{0,1}[a-z]{0,1}d{0,1})([a-z]+)[0-9]*$'
Where Nova client says explicitly:
$ nova help volume-attach
usage: nova volume-attach []
Attach a volume to a server.
Positional arguments:
Name or ID of server.
ID of the volume to attach.
Name of the device e.g. /dev/vdb. Use "auto" for autoassign (if
supported)
That "device" is optional and can be set to 'auto'.
[1]
https://github.com/openstack/nova/blob/b7c8a73824211db9627962abd31b8801cc2c2880/nova/api/openstack/compute/volumes.py#L270
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1491325/+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
[Yahoo-eng-team] [Bug 1491325] Re: nova api v2.1 does not allow to use autodetection of volume device path
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => liberty-rc1
--
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/1491325
Title:
nova api v2.1 does not allow to use autodetection of volume device
path
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) juno series:
Won't Fix
Status in OpenStack Compute (nova) kilo series:
Fix Committed
Status in python-novaclient:
Fix Released
Bug description:
Using API v2.1 we are forced to provide device path attaching a volume
to an instance.
using API v2.0 it allowed to provide 'auto' and in this case Nova
calculated it by itself.
It is very useful when we do not care about exact device path.
using APi v2.1 Nova, at first verifies request body [1] and only then
have logic to autodetect "device path". So, either autodetect is dead
code now or request validation should be changed.
For the moment, this bug is blocker for Manila project.
We get one of two errors:
Returning 400 to user: Invalid input for field/attribute device.
Value: None. None is not of type 'string' __call__
or
Returning 400 to user: Invalid input for field/attribute device.
Value: auto. u'auto' does not match
'(^/dev/x{0,1}[a-z]{0,1}d{0,1})([a-z]+)[0-9]*$'
Where Nova client says explicitly:
$ nova help volume-attach
usage: nova volume-attach []
Attach a volume to a server.
Positional arguments:
Name or ID of server.
ID of the volume to attach.
Name of the device e.g. /dev/vdb. Use "auto" for autoassign (if
supported)
That "device" is optional and can be set to 'auto'.
[1]
https://github.com/openstack/nova/blob/b7c8a73824211db9627962abd31b8801cc2c2880/nova/api/openstack/compute/volumes.py#L270
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1491325/+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
[Yahoo-eng-team] [Bug 1491325] Re: nova api v2.1 does not allow to use autodetection of volume device path
Since the v2.1 API was still experimental in Juno I don't think this is
worth fixing there.
** Also affects: nova/juno
Importance: Undecided
Status: New
** Also affects: nova/kilo
Importance: Undecided
Status: New
** Changed in: nova/juno
Status: New => Won't Fix
** Changed in: nova/kilo
Status: New => Fix Committed
** Changed in: nova/kilo
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in: nova/kilo
Importance: Undecided => High
** Tags removed: juno-backport-potential
--
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/1491325
Title:
nova api v2.1 does not allow to use autodetection of volume device
path
Status in OpenStack Compute (nova):
Fix Committed
Status in OpenStack Compute (nova) juno series:
Won't Fix
Status in OpenStack Compute (nova) kilo series:
Fix Committed
Status in python-novaclient:
Fix Released
Bug description:
Using API v2.1 we are forced to provide device path attaching a volume
to an instance.
using API v2.0 it allowed to provide 'auto' and in this case Nova
calculated it by itself.
It is very useful when we do not care about exact device path.
using APi v2.1 Nova, at first verifies request body [1] and only then
have logic to autodetect "device path". So, either autodetect is dead
code now or request validation should be changed.
For the moment, this bug is blocker for Manila project.
We get one of two errors:
Returning 400 to user: Invalid input for field/attribute device.
Value: None. None is not of type 'string' __call__
or
Returning 400 to user: Invalid input for field/attribute device.
Value: auto. u'auto' does not match
'(^/dev/x{0,1}[a-z]{0,1}d{0,1})([a-z]+)[0-9]*$'
Where Nova client says explicitly:
$ nova help volume-attach
usage: nova volume-attach []
Attach a volume to a server.
Positional arguments:
Name or ID of server.
ID of the volume to attach.
Name of the device e.g. /dev/vdb. Use "auto" for autoassign (if
supported)
That "device" is optional and can be set to 'auto'.
[1]
https://github.com/openstack/nova/blob/b7c8a73824211db9627962abd31b8801cc2c2880/nova/api/openstack/compute/volumes.py#L270
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1491325/+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
[Yahoo-eng-team] [Bug 1491325] Re: nova api v2.1 does not allow to use autodetection of volume device path
** Changed in: nova
Status: Invalid => In Progress
** Changed in: nova
Assignee: Sean Dague (sdague) => Matt Riedemann (mriedem)
--
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/1491325
Title:
nova api v2.1 does not allow to use autodetection of volume device
path
Status in OpenStack Compute (nova):
In Progress
Status in python-novaclient:
Fix Committed
Bug description:
Using API v2.1 we are forced to provide device path attaching a volume
to an instance.
using API v2.0 it allowed to provide 'auto' and in this case Nova
calculated it by itself.
It is very useful when we do not care about exact device path.
using APi v2.1 Nova, at first verifies request body [1] and only then
have logic to autodetect "device path". So, either autodetect is dead
code now or request validation should be changed.
For the moment, this bug is blocker for Manila project.
We get one of two errors:
Returning 400 to user: Invalid input for field/attribute device.
Value: None. None is not of type 'string' __call__
or
Returning 400 to user: Invalid input for field/attribute device.
Value: auto. u'auto' does not match
'(^/dev/x{0,1}[a-z]{0,1}d{0,1})([a-z]+)[0-9]*$'
Where Nova client says explicitly:
$ nova help volume-attach
usage: nova volume-attach []
Attach a volume to a server.
Positional arguments:
Name or ID of server.
ID of the volume to attach.
Name of the device e.g. /dev/vdb. Use "auto" for autoassign (if
supported)
That "device" is optional and can be set to 'auto'.
[1]
https://github.com/openstack/nova/blob/b7c8a73824211db9627962abd31b8801cc2c2880/nova/api/openstack/compute/volumes.py#L270
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1491325/+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
[Yahoo-eng-team] [Bug 1491325] Re: nova api v2.1 does not allow to use autodetection of volume device path
** Changed in: python-novaclient
Status: Fix Committed => Fix Released
** Changed in: python-novaclient
Milestone: None => 2.28.0
--
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/1491325
Title:
nova api v2.1 does not allow to use autodetection of volume device
path
Status in OpenStack Compute (nova):
In Progress
Status in python-novaclient:
Fix Released
Bug description:
Using API v2.1 we are forced to provide device path attaching a volume
to an instance.
using API v2.0 it allowed to provide 'auto' and in this case Nova
calculated it by itself.
It is very useful when we do not care about exact device path.
using APi v2.1 Nova, at first verifies request body [1] and only then
have logic to autodetect "device path". So, either autodetect is dead
code now or request validation should be changed.
For the moment, this bug is blocker for Manila project.
We get one of two errors:
Returning 400 to user: Invalid input for field/attribute device.
Value: None. None is not of type 'string' __call__
or
Returning 400 to user: Invalid input for field/attribute device.
Value: auto. u'auto' does not match
'(^/dev/x{0,1}[a-z]{0,1}d{0,1})([a-z]+)[0-9]*$'
Where Nova client says explicitly:
$ nova help volume-attach
usage: nova volume-attach []
Attach a volume to a server.
Positional arguments:
Name or ID of server.
ID of the volume to attach.
Name of the device e.g. /dev/vdb. Use "auto" for autoassign (if
supported)
That "device" is optional and can be set to 'auto'.
[1]
https://github.com/openstack/nova/blob/b7c8a73824211db9627962abd31b8801cc2c2880/nova/api/openstack/compute/volumes.py#L270
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1491325/+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
