Bug 1275935 - nova searches for wrong device unexpectedly when multipath device has faulty lun
Summary: nova searches for wrong device unexpectedly when multipath device has faulty lun
Keywords:
Status: CLOSED DUPLICATE of bug 1275937
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Eoghan Glynn
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-28 07:02 UTC by Chen
Modified: 2019-09-09 14:48 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-30 16:47:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Chen 2015-10-28 07:02:15 UTC 
Description of problem:

nova searches for wrong device unexpectedly when multipath device has faulty lun

The error message is something following:

TRACE nova.compute.manager [instance: d9db6ec9-0758-4565-acd8-e06bd6a29c3a] libvirtError: Cannot access storage file '/dev/mapper/Oct' (as uid:107, gid:107): No such file or directory

As the above we can see that nova-compute is looking for a device called /dev/mapper/Oct.

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

OSP 6.0 on RHEL 7

How reproducible:



Steps to Reproduce: ( according to the customer )
1. Make one lun faulty in multipath device
2. Start a nova instance
3. Check the nova-compute.log

Actual results:

A wrong device ( /dev/mapper/Oct ) is used

Expected results:

The instance should boot normally.

Additional info:
Comment 2 Lee Yarwood 2015-10-30 16:47:24 UTC 

*** This bug has been marked as a duplicate of bug 1275937 ***
Note You need to log in before you can comment on or make changes to this bug.