+++ 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.
Awaiting newer build, insufficient to verify: 14 -p 2019-09-06.1 python2-os-brick-2.5.6-1.el7ost.noarch < fixed-in
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