-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve multipath identifiers #5412
Improve multipath identifiers #5412
Conversation
d3d8470
to
fa7cdda
Compare
…(#2046654) Multipath devices themselves do not have a path-id but only their path members. In that case, a good volume identifier is the WWID/WWN/UUID. Fixes: 8e75893 ("Remove the local storage object from the advanced storage spoke") Signed-off-by: Steffen Maier <[email protected]> Resolves: RHEL-11384
Currently, the UI prints the kernel device names for multipath path members. Kernel device names are unpredictable and non-persistent and thus hardly suitable as path identifier for users. This is a preparation providing backend data to be used in a future commit to show in the UI. FCoE, iSCSI, and NVDIMM already have the attribute since commit e74030e ("Add the path-id attribute to the DBus structure for device data"). Provide the same for zfcp-attached SCSI disks, which should always be used with multipathing. This change tolerates the absence of the id_path attribute if the corresponding change adding the attribute in blivet does not exist. Signed-off-by: Steffen Maier <[email protected]> Related: RHEL-11384
As user I expect that I can re-run the installation unattendedly when using the generated kickstart file of an interactive installation run (using the same installer boot options plus inst.ks=). Meanwhile, only those zfcp statements from a kickstart file provided as input for an installation run were also written into the generated kickstart file. Fix the missing zfcp statements in the generated kickstart file that originate in user interactions on the storage screen UI. Fixes: d819bb9 ("Remove unused writeKS methods.") Fixes: 0d76185 ("Remove all the writeKS methods except in network and storage.") Signed-off-by: Steffen Maier <[email protected]> Related: RHEL-11384
fa7cdda
to
6f7f41b
Compare
Validation tests are failing because of dependencies:
waiting for this anaconda update: #5399 - I wouldn't block on that
waiting for python-blivet 3.6.0-13 appearing in nightly composes (should happen tonight). |
So now only the tests depending on #5399 are failing, as expected.
|
/kickstart-test --testtype smoke |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks!
if "wwpn" in dir(fcpdev): | ||
zd.wwpn = fcpdev.wwpn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code is ported from upstream, isn't it? It should be ideally zd.wwpn = getattr(fcpdev, "wwpn", "")
and same for fcplun
, but it doesn't make sense to change the original commits here.
No description provided.