Skip to content
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

Merged
merged 3 commits into from
Jan 24, 2024

Conversation

rvykydal
Copy link
Contributor

No description provided.

…(#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
@rvykydal rvykydal force-pushed the improve-multipath-identifiers branch from fa7cdda to 6f7f41b Compare January 19, 2024 07:50
@rvykydal
Copy link
Contributor Author

rvykydal commented Jan 19, 2024

Validation tests are failing because of dependencies:

FAILED unit_tests/pyanaconda_tests/test_kickstart_specification.py::ModuleSpecificationsTestCase::test_all_commands
FAILED unit_tests/pyanaconda_tests/test_kickstart_specification.py::ModuleSpecificationsTestCase::test_useless_command_map
FAILED unit_tests/pyanaconda_tests/modules/payloads/payload/test_rpm_ostree.py::RPMOSTreeKickstartTestCase::test_ostree_kickstart
FAILED unit_tests/pyanaconda_tests/modules/payloads/payload/test_rpm_ostree.py::RPMOSTreeKickstartTestCase::test_priority_kickstart

waiting for this anaconda update: #5399 - I wouldn't block on that

FAILED unit_tests/pyanaconda_tests/modules/storage
/test_module_device_tree.py::DeviceTreeInterfaceTestCase::test_get_zfcp_device_data

waiting for python-blivet 3.6.0-13 appearing in nightly composes (should happen tonight).

@rvykydal
Copy link
Contributor Author

So now only the tests depending on #5399 are failing, as expected.

=========================== short test summary info ============================
FAILED unit_tests/pyanaconda_tests/test_kickstart_specification.py::ModuleSpecificationsTestCase::test_all_commands
FAILED unit_tests/pyanaconda_tests/test_kickstart_specification.py::ModuleSpecificationsTestCase::test_useless_command_map
FAILED unit_tests/pyanaconda_tests/modules/payloads/payload/test_rpm_ostree.py::RPMOSTreeKickstartTestCase::test_ostree_kickstart
FAILED unit_tests/pyanaconda_tests/modules/payloads/payload/test_rpm_ostree.py::RPMOSTreeKickstartTestCase::test_priority_kickstart
====== 4 failed, 1730 passed, 3 skipped, 26 warnings in 105.35s (0:01:45) ======

@rvykydal
Copy link
Contributor Author

/kickstart-test --testtype smoke

Copy link
Contributor

@poncovka poncovka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks!

Comment on lines +93 to +94
if "wwpn" in dir(fcpdev):
zd.wwpn = fcpdev.wwpn
Copy link
Contributor

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.

@rvykydal rvykydal added the ready to merge The PR can be merged. It should have all BZ flags required for releasing set (usually release+). label Jan 23, 2024
@M4rtinK M4rtinK merged commit af1fd28 into rhinstaller:rhel-9 Jan 24, 2024
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready to merge The PR can be merged. It should have all BZ flags required for releasing set (usually release+). rhel-9
Development

Successfully merging this pull request may close these issues.

5 participants