Bug 1487585

Summary: Incorrectly logging as error message on HBA channel search
Product: Red Hat OpenStack Reporter: Gorka Eguileor <geguileo>
Component: python-os-brickAssignee: Gorka Eguileor <geguileo>
Status: CLOSED ERRATA QA Contact: Tzach Shefi <tshefi>
Severity: medium Docs Contact:
Priority: low    
Version: 10.0 (Newton)CC: apevec, eharney, geguileo, jschluet, lhh, lruzicka, mzheng, pgrist, srevivo
Target Milestone: z6Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-os-brick-1.6.1-7.el7ost Doc Type: Bug Fix
Doc Text:
During FC scan we were logging failure to find target and channel to limit the scanning as an error, now we correctly log it as debug information.
Story Points: ---
Clone Of: 1487582 Environment:
Last Closed: 2017-11-15 13:45:13 UTC Type: Bug
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: 1487582    
Bug Blocks:    

Description Gorka Eguileor 2017-09-01 10:48:54 UTC
+++ This bug was initially created as a clone of Bug #1487582 +++

On the FC initiator, when we are doing a scan we try to narrow the scope of the scan as much as possible, for this purpose we try to get the HBA channel and SCSI targets for an HBA.

Unfortunately the mechanism we have implemented to detect these two parameters is not universal and will only work on FC targets that implement a single WWN.

This is OK, as the code is capable of operating normally without those 2 parameters, it's just that the filtering on the scan is not as precise as it could be.

So the issue is that we are logging as an error when we cannot get that information, which is clearly misleading to anybody reading the logs.

Comment 6 errata-xmlrpc 2017-11-15 13:45:13 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-2017:3231