[Bug 1559193] Re: disk-detect/s390-dasd/s390-zfcp: Restructure installer and put DASD and FCP configuration into disk detection
Launchpad Bug Tracker
1559193 at bugs.launchpad.net
Mon Apr 4 17:07:14 UTC 2016
This bug was fixed in the package hw-detect - 1.117ubuntu1
---------------
hw-detect (1.117ubuntu1) xenial; urgency=low
* Merge 1.117 from debian to pick up fix for LP: #1559193.
* Resynchronise with Debian. Remaining changes:
- Add an 'archdetect-deb' package, containing /usr/bin/archdetect. Add
an archdetect(1) manual page.
- Add support for activating fakeraid devices with mdadm.
- disk-detect.sh: Do not check the kernel command line for any option
to enable dmraid support. If functional dmraid arrays are found, the
user will be asked if they wish to activate them.
- 'dmraid -c -s' changed its output format; cope with both old and new.
- Make dmraid logging a bit neater.
- Offer iSCSI targets for preseeding if partman-iscsi is available and
no disk devices are found.
- disk-detect.sh: Use mpath[a-z] now rather than mpath[0-9] to identify
multipath devices and thus know to install partman-multipath.
- disk-detect.sh: run update-dev after installing multipath and sg3.
- debian/control: Depends on multipath-udeb (>= 0.5.0), which introduces
the multipath device naming changes above.
- Remove dm-emc from the multipath modules, since it's gone since
2.6.27.
- Improve checks for dm-* drivers being present to avoid relying on them
being built as modules.
- Bump question to load driver injection disk from medium to high, and
raise driver-injection-disk package priority to standard. Thus the
udeb will be loaded by default, but before installing any debs from
the OEMDRV a confirmation question will be asked (default true, can be
pre-seeded)
- Drop priorities of a couple of ethdetect questions to medium.
- Exit zero if you continue all the way through ethdetect's errors about
having no network interfaces.
- Remove FireWire Ethernet support.
- disk-detect.sh: multipath: reload udev rules before re-add devices
to guarantee all devices may get new udev properties
- disk-detect.sh: multipath: deactivate LVM volumes before multipath
discovery to unlock individual paths
- disk-detect.sh: multipath: deactivate md arrays before multipath
discovery to unlock individual paths
- disk-detect.sh: use iscsi-start wrapper in partman-iscsi to be able to set
a custom iSCSI initiatorName from the installer.
- disk-detect.sh: load SCSI device handlers before SCSI low-level
device drivers.
hw-detect (1.117) unstable; urgency=medium
* Team upload
[ Hendrik Brueckner ]
* Improve and split harddrive detection into DASD and SCSI dependency
on s390x (Closes: #818586)
hw-detect (1.116) unstable; urgency=medium
[ Colin Watson ]
* Use HTTPS for Vcs-* URLs, and link to cgit rather than gitweb.
hw-detect (1.115) unstable; urgency=medium
[ Colin Watson ]
* Compress devnames-static.gz using "gzip -n" (Lintian).
-- Dimitri John Ledkov <xnox at ubuntu.com> Mon, 04 Apr 2016 14:37:02
+0100
** Changed in: hw-detect (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to hw-detect in Ubuntu.
https://bugs.launchpad.net/bugs/1559193
Title:
disk-detect/s390-dasd/s390-zfcp: Restructure installer and put DASD
and FCP configuration into disk detection
Status in hw-detect package in Ubuntu:
Fix Released
Status in s390-dasd package in Ubuntu:
Fix Committed
Status in s390-zfcp package in Ubuntu:
Fix Committed
Status in hw-detect package in Debian:
Fix Released
Status in s390-dasd package in Debian:
Fix Released
Status in s390-zfcp package in Debian:
Fix Released
Bug description:
== Comment: #1 - Hendrik Brueckner <brueckner at de.ibm.com> - 2016-03-18 09:23:45 ==
On Linux on z Systems, there are two major disk storage environments,
the direct-attached storage disk (DASD) and SCSI over Fibre-Channel.
There are the s390-dasd and s390-zfcp d-i modules to configure and
enable DASDs and FCP devices. Note that on s390x, disks are not
available by default to Linux and must be enabled in advance.
The s390-dasd and s390-zfcp both provide the harddrive-detection
dependency and, thus, each could fulfill the dependency to silenty
ignore the other. That behavior does not allow to mix DASDs and
SCSI disk on single installation (except you call both manually,
for example, in the expert mode).
To improve and provide a "guided" flow, I have split the harddrive
detection dependency for s390-dasd and s390-zfcp as follows:
- s390-dasd provides harddrive-detection-dasd
- s390-zfcp provides harddrive-detection-zfcp
disk-detect depends on
-> harddrive-detection-dasd
-> harddrive-detection-zfcp
and continues to provide the harddrive-detection.
With this split, the guided installation will install disk-detect to
solve the harddrive-detection dependency. In turn, disk-detect will
then rely on the s390-dasd and s390-zfcp d-i modules to provide DASD
and FC-attached SCSI disks. If both modules fail, the user perceives
the default disk-detect behavior, for example, users might configure
iSCSI.
The other nice benefit of this dependency split is the seamlessly
enablement of multipath with disk-detect (through preseeding).
For s390, multipathing should be always considered when SCSI is used.
I probably will extend the s390-zfcp module to set disk-detect's
multipath debconf variable for usability.
There are already Debian bug reports with patches to provide this solution:
disk-detect: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818586
s390-dasd: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818591
s390-zfcp: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818592
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1559193/+subscriptions
More information about the foundations-bugs
mailing list