Bug 1157681 - vdsm-4.14.13-2 sends FC LIP events on storage actions
Summary: vdsm-4.14.13-2 sends FC LIP events on storage actions
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.4.1-1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.4.4
Assignee: Nir Soffer
QA Contact: Elad
URL:
Whiteboard: storage
Depends On: 1152587
Blocks: 1133612
TreeView+ depends on / blocked
 
Reported: 2014-10-27 13:35 UTC by rhev-integ
Modified: 2019-04-28 10:46 UTC (History)
33 users (show)

Fixed In Version: vdsm-4.14.18-1.el6ev
Doc Type: Bug Fix
Doc Text:
The issue_lip operation introduced in RHEV 3.4.3 to fix a failure to discover new LUNs on Fibre Channel regression introduced in RHEV 3.4.0 has been found to be disruptive on some storage servers and caused storage connection issues. Domains became inaccessible on random occasions. With this update, the issue_lip operation is disabled by default. As a result, discovering new LUNs on Fibre Channel storage server is not supported by default. Users can enable this option through new vdsm configuration (hba_rescan) if this option is compatible with the storage server. A future RHEV version will support discovering new LUNs by default.
Clone Of: 1152587
Environment:
Last Closed: 2014-12-02 20:27:46 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1218583 0 None None None Never
Red Hat Product Errata RHBA-2014:1946 0 normal SHIPPED_LIVE vdsm 3.4.4 bug fix and enhancement update 2014-12-03 01:26:44 UTC
oVirt gerrit 34176 0 master MERGED multiapth: Disable hba rescanning by default Never
oVirt gerrit 34196 0 ovirt-3.4 ABANDONED multiapth: Disable hba rescanning by default Never
oVirt gerrit 34215 0 ovirt-3.5 MERGED multiapth: Disable hba rescanning by default Never
oVirt gerrit 34245 0 master MERGED hba: Rescan using SCSI layer Never

Comment 1 Elad 2014-11-18 10:01:46 UTC 
FC LIP is not initiated as part of edit/create new FC domain (connectStorageServer/getDeviceList) or for monitor domain calls.

Checked also the following scenarios:


Created 3 FC domains, 10 VMs disks attached from the FC domains. Installed OS on the VM and during OS installation tried the following opearaions which supposed to trigger bus refresh:

1) Clicked on new domain, picked FC
2) Tried to edit an existing FC domain
3) Mapped a new LUN to the host from the storage server, exposed it by FC. Then did steps 1 and 2 
4) Issued  'rescan-scsi-bus.sh' on the host so it will see the new LUN. Then did steps 1 and 2


During those actions, OS installation on the guest wasn't affected, it finished successfully.



Didn't encountered any of:

High Latency errors reported by storage
Link Up events registered for FC HBAs
sanlock warnings/errors reported



Checked using XtremIO storage server

Used rhev 3.4.4 vt13.1.
Comment 2 Julie 2014-11-24 03:42:28 UTC 
Hi Allon,

If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format:

Cause:
Consequence:
Fix:
Result:

The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.

Many thanks,
Julie
Comment 3 Allon Mureinik 2014-11-24 05:35:31 UTC 
(In reply to Julie from comment #2)
> Hi Allon,
> 
> If this bug requires doc text for errata release, please provide draft text
> in the doc text field in the following format:
> 
> Cause:
> Consequence:
> Fix:
> Result:
> 
> The documentation team will review, edit, and approve the text.
> 
> If this bug does not require doc text, please set the 'requires_doc_text'
> flag to -.
> 
> Many thanks,
> Julie

Nir, due to the high visibility this regression had, we probably would like some doctext here.
Could you provide it please?
Comment 6 errata-xmlrpc 2014-12-02 20:27:46 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.

https://rhn.redhat.com/errata/RHBA-2014-1946.html
Note You need to log in before you can comment on or make changes to this bug.