…(#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]>

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]>

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]>