Hello, I am also affected by this bug with a device which by defaults is always seen has belonging to the blacklist since it does not have a proper SCSI_IDENT.* udev property.
I have not tested the patch since I found a fast work around and not having
much time right now, but what is described in the email attached to the bug
would definitely solve the issue. The current work around I have is to add the
ID_SERIAL in the property of blacklist_exceptions as such :
blacklist_exceptions {
wwid XXXXXXXXXX
## property "(ID_WWN|SCSI_IDENT_.*)"
property "(ID_WWN|SCSI_IDENT_.*|ID_SERIAL)"
}
For this workaround to be fully function I also had to perform a
update_initramfs (so it is accounted for during boot).
Clearly it would be much better that udeb is already adding the expected
SCSI_IDENT_* properties to SCSI devices as proposed in patch with bug #782487
(sg3-utils: provide udev rules for multipath-tools)
Is it possible to raise the severity level of this bug to make it RC, and is
there a chance that both bugs (782487 and 782488) are solved before the release
so that the installation on systems relying on multipath would not require
workaround to be functional ?
Thank you very much for all the work already done.
Serge.
signature.asc
Description: Message signed with OpenPGP using GPGMail
