Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1085036

Summary:	Add support for specifying disk bus and device type when attaching volumes
Product:	Red Hat OpenStack	Reporter:	Nikola Dipanov <ndipanov>
Component:	python-novaclient	Assignee:	Nikola Dipanov <ndipanov>
Status:	CLOSED WONTFIX	QA Contact:	yeylon <yeylon>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.0 (RHEL 7)	CC:	eglynn, jruzicka, ndipanov, sgordon, srevivo, yeylon
Target Milestone:	z5	Keywords:	ZStream
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-16 15:32:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1041053

Description Nikola Dipanov 2014-04-07 15:14:04 UTC

Description of problem:

When completing https://blueprints.launchpad.net/nova/+spec/use-new-bdm-format-in-attach BP, changes that will enable users to use it through python-novaclient were not done.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

$ nova help volume-attach
usage: nova volume-attach <server> <volume> [<device>]

Attach a volume to a server.

Positional arguments:
  <server>  Name or ID of server.
  <volume>  ID of the volume to attach.
  <device>  Name of the device e.g. /dev/vdb. Use "auto" for autoassign (if
            supported)

Expected results:

nova command line utility should provide the possibility to optionally pass disk bus and device type with the volume-attach command.

Additional info:

Comment 4 Stephen Gordon 2015-04-15 16:19:00 UTC

Looks to be resolved upstream, need to backport to Juno tree.