action #99267

Updated by geor almost 2 years ago

After some recent changes in the zfcp connectivity, `validate_multipath` module is failing. 

 The main reason of the failure is that after the changes, we have two `wwid` entries instead of one.  
 Compare the listed wwids (output at the bottom) from [this job]( to [this one]( 
 This results in the stored `$wwid` output in the `validate_multipath` module to contain two lines with two different worldwide identifiers. 

 Similarly, due to this, the output of `multipath -ll` now contains two device mapper devices instead of one. 
 This can be seen [here]( in contrast to [this old job]( 

 This setup results in two commands being susceptible to failure.  
 1. The first is `assert_matches(qr/$wwid dm-0 $ven_pro_rev/, $topology_output, 'General topology info are not displayed properly');`. This of course fails because `$wwid` contains two lines of identifiers corresponding to the two multipath maps. This is the failure seen in our zfcp jobs currently. 
 2. The second one is `validate_script_output("multipath -d -v3 | grep ^$wwid", qr/$wwid.*$name/);`. If the previous command would not exist the jobs would fail here because, once more, the `$wwid` parameter no longer contains only one WWID, and also because it points to a different disk. WWID. 

 ## Observation 

 openQA test in scenario sle-15-SP4-Online-s390x-zfcp@s390x-zfcp fails in 

 ## Test suite description 
 Testsuite maintained at Maintainer: QE Yast, mgriessmeier 

 Installation-only test configuring an s390x ZFCP storage. 

 ## Reproducible 

 Fails since (at least) Build [29.1]( 

 ## Expected result 

 Last good: (unknown) (or more recent) 

 ## Further details 

 Always latest result in this scenario: [latest]( 

 ## Suggestion 

 A good middle ground solution would be to store in the `$wwid` parameter only one of the identifiers matching to a single multipath map. 
 This would mean that both commands 1. and 2. listed on the top of the description would pass. 
 This is not a compromise, since we will still test the validity of one multipath map (as was the case for 15-SP3, before this change had occured)