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

Bug 1721099

Summary:	[RHOSP14][os-brick][Backport] FC scan always scanning all HBAs when receiving initiator_target_map'.
Product:	Red Hat OpenStack	Reporter:	Pablo Caruana <pcaruana>
Component:	python-os-brick	Assignee:	Pablo Caruana <pcaruana>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	apevec, jschluet, knoha, lhh, nlevinki, pcaruana, rheslop, tshefi
Target Milestone:	z4	Keywords:	Triaged, ZStream
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-os-brick-2.5.6-2.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, the OpenStack Cinder brick library would only check for a single WWNN (World Wide Node Name) if an `initiator_target_map` was not received from the backend. This misses some storage arrays, as some array architectures return the `initiator_target_map` though some ports are not connected to specific HBAs. This patch changes that behavior so that `initiator_target_map` is always checked.	Story Points:	---
Clone Of:	1721080
Clones:	1721104 (view as bug list)		Environment:
Last Closed:	2019-11-06 16:47:36 UTC	Type:	---
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:	1721104
Bug Blocks:	1721080

Description Pablo Caruana 2019-06-17 11:03:13 UTC

+++ This bug was initially created as a clone of Bug #1721080 +++

Description of problem:

FC: Ignore some HBAs from map for single WWNN

Current FC OS-Brick code only checks for single WWNN to exclude some
HBAs from scanning when we don't receive an initiator_target_map from
the backend.

There are storage arrays,like XtremIO, that due to their architecture
and design have all target ports automatically mapped to LUNs and are
returning the initiator_target_map, but some of those ports may not be
connected to our HBAs, so we end up with another case of bug #1765000.

For example,
A server contains 4 HBAs.
2 HBAs are connected to VNX only.
Other 2 HBAs are connected to XtremIO only. 


This particular patch ensures  always checking  if the target implements single WWNN, not only when not  receiving the initiator_target_map.

Main goal is decreasing  the likelihood of ending with unexpected devices as  now it will ignore unconnected HBAs (even if reported in the initiator_target_map) if  working with single WWNN target.

Comment 2 Tzach Shefi 2019-10-02 05:04:57 UTC

Awaiting newer build, insufficient to verify:
14  -p 2019-09-06.1
python2-os-brick-2.5.6-1.el7ost.noarch < fixed-in

Comment 6 errata-xmlrpc 2019-11-06 16:47:36 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://access.redhat.com/errata/RHBA-2019:3745