os-brick

WWN verification fails if no WWN is found

Bug #1819577 reported by Avishay Traeger on 2019-03-12

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	os-brick	New	Undecided	Avishay Traeger

Bug Description

Due to the recently-added WWN validation, if get_sysfs_wwn() doesn't return a WWN for some reason, the verification fails:

VolumeDeviceValidationFailed: Volume device validation failed for device sda (expected 3624a93702f6eb7add2464f9b004a6826, found .

Revision history for this message

Sahid Orentino (sahid-ferdjaoui) wrote on 2019-03-12:

It would have been great to share a bit of more of details related to the issue. My thinking is that your patch can't work in case of multipath usage since the devices are not registered anymore in sysfs. But it's just one potential issue, it may have others.

As you have noticed, reverting this commit 14be08d0b53836963a530e2990a6db73901cbdac may be a good start but if we can have share details we could also try to fix the change.

commit 14be08d0b53836963a530e2990a6db73901cbdac
Author: Avishay Traeger <email address hidden>
Date: Tue Jan 29 10:10:50 2019 +0200

Verify WWN of connected iSCSI devices if passed

    If a WWN has been provided in connection_properties, verify that the
    found devices have that expected WWN. Fail the attachment if not. This
    prevents cases where a device already exists on the host from an old
    attachment that wasn't fully cleaned up, and the new attachment got
    the same LUN. Using this old device could lead to data corruption.

Change-Id: I45a2221c0518213dc8132831c0bde9db4734da2b
Closes-Bug: 1813609

Revision history for this message

Avishay Traeger (avishay-il) wrote on 2019-03-12:

Thanks Sahid. Right now the goal is to revert the patch since a new version of os-brick was just released and this is broken, and we need a low-risk fix (revert). After that we should definitely try to fix it.