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

Bug 1092012

Summary: Specified mountpoint is ignored when a volume is attached to an instance
Product: Red Hat OpenStack Reporter: Tzach Shefi <tshefi>
Component: openstack-novaAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact: Ami Jeain <ajeain>
Severity: unspecified Docs Contact:
Priority: low    
Version: 4.0CC: ndipanov, sgordon, tshefi, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-22 19:35:39 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:
Attachments:
Description Flags
Compute log none

Description Tzach Shefi 2014-04-28 13:43:19 UTC
Created attachment 890501 [details]
Compute log

Description of problem:  Attaching a volume to instance works with auto, but when I force specific mount point it's ignored, on instance mount point used is the next free one, no matter what I ask for. 

nova volume-attach <instance-ID> <vol_ID>  /dev/vdc
Inside instance (rhel 6.5) device is mounted as /dev/vdb, also tired on cirros same problem. 

Instaleld with packstack semi dist', Cinder's backend Gluster. 

Version-Release number of selected component (if applicable):
RHEL 6.5
openstack-nova-compute-2013.2.3-6.el6ost.noarch

Instances used to test rhel6.5 and cirros image

How reproducible:
Every time

Steps to Reproduce:
1. Boot an instance
2. Create a new cinder volume
3. Nova attache a volume to an instance in a specific mount point /dev/vdg for example
4. Check new volume's mount point in instance

Actual results:

Volume is mounted but on next free mount path, not at requested path /dev/vdg.

Expected results:

Volume should be mounted on requested path. 

Additional info:
Linked bug from launchpad, it's an old one still not fixed.

Comment 2 Nikola Dipanov 2014-04-29 19:47:55 UTC
There is a lot of information on the upstream bug so I am not sure we need to track it here as well.

Ideally - the user will let nova figure out the device name and use the by-uuid to figure out the disk as explained in the bug.

It might be reasonable to document this (although I believe it has been documented in several places. We could move this to docs - would that work?

Comment 3 Tzach Shefi 2014-05-01 07:33:01 UTC
I Agree users would usually auto mount, so this is low priority. As QE my goal is to find stuff that doesn't work and report it, having done that, it's not up to me to decide how to further handle bugs. 

Those decisions fall upon PM / dev, if you think moving to doc would be sufficient, that's fine by me.

Comment 4 Nikola Dipanov 2014-05-09 14:37:51 UTC
Might be worth keeping around as we may want to make this a bit more user friendly. Pushing off to future releases tho, as it is unlikely to get work done for 5.0