Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1159839 - New FC LUNs are not detected on hypervisor without a reboot
Summary: New FC LUNs are not detected on hypervisor without a reboot
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.5.0
Assignee: Nir Soffer
QA Contact: Elad
Whiteboard: storage
Depends On:
Blocks: 1103722 oVirt_3.5.1_tracker rhev35rcblocker rhev35gablocker 1173969
TreeView+ depends on / blocked
Reported: 2014-11-03 13:28 UTC by Nir Soffer
Modified: 2016-02-10 19:35 UTC (History)
16 users (show)

Fixed In Version: vdsm-
Doc Type: Bug Fix
Doc Text:
Previously, Red Hat Enterprise Linux Virtualization 3.4.0 introduced a regression where SCSI scans for FC devices were disabled. As a result, new LUNs on FC servers were not discovered automatically. With this release, the SCSI scan for FC devices has been reintroduced so that new LUNs on FC servers can be discovered automatically.
Clone Of:
: 1173969 (view as bug list)
Last Closed: 2015-02-11 21:13:09 UTC
oVirt Team: Storage
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0159 normal SHIPPED_LIVE vdsm 3.5.0 - bug fix and enhancement update 2015-02-12 01:35:58 UTC
oVirt gerrit 34245 master MERGED hba: Rescan using SCSI layer Never
oVirt gerrit 35650 ovirt-3.5 MERGED hba: Rescan using SCSI layer Never

Description Nir Soffer 2014-11-03 13:28:57 UTC
Description of problem:

After adding new LUNs on FC server, the LUNs are not detected on

Version-Release number of selected component (if applicable):
All versions since 4.14.0

How reproducible:

Steps to Reproduce:
1. Start a hypervisor connected to FC storage server
2. On the FC stoage server, add new LUN and expose it to the hypervisor
3. Try to edit a FC storage domain or create new one

Actual results:
The new LUN does not appear in the device lists

Expected results:
The new LUN should be listed

Additional info:

In versions before 4.14.0, we used to perform scsi scan, equivalent
to this:

    for path in /sys/class/scsi_host/host*/scan
        do echo "- - -" > $path

This scan was removed in 66c24c1996 (iscsi: Iscsi rescan cleanup),
assuming that iscsiadm -m session --rescan is already doing the scsi
scan. iscsiadm is doing scssi scan, but only for iscsi connections.

This issue was reported in bug 1123637, but we did not detect the missing
scsi scan on FC devices. We fixed this but by introducing FC issue_lip
operation. This fix was disabled later due to bug 1157681, because on 
some storage server, issue_lip was disruptive.


Perform manual scsi scan on all fc hosts:
1. Log in to host
2. Run:

    for path in /sys/class/fc_host/host*/device/scsi_host/host*/scan; do
        echo "- - -" > $path

For more details see:

Comment 4 Elad 2014-11-24 10:40:39 UTC
Tested Nir's patch. Tested that FC scan is performed:

- Mapped a new device to the host by FC, then tried to create new FC storage domain. New devices are visible to the host
- Mapped a new device to the host by FC, then tried to edit an existing FC domain.  New devices are visible to the host
- Negative: Unmapped a device from the host. fc_scan doesn't hung

Tested with both RHEL6.6 and RHEL7 OS installed on the hosts.
Tested using 2 storage servers: EMC-XtremIO and EMC-VNX

Comment 5 Elad 2014-12-10 13:32:49 UTC
FC LUNs are detected while exposing them without rebooting the host.
Tested the following:
- Exposed new LUN to the host and clicked on 'New' domain. LUN was visible
- Exposed new LUN to the host and clicked on 'Edit' FC domain. LUN was visible

Tested using 2 storage servers:
- EMC XtremIO

Verified using rhev 3.5 vt13.1

Comment 9 errata-xmlrpc 2015-02-11 21:13:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

Note You need to log in before you can comment on or make changes to this bug.