No worries; it's nothing you configured/changed as far as I can tell. We look up device paths to disk via serial or wwn; as it turns out your two disks have different serials, but a duplicate (and invalid WWN); so we'll need to fix our code to ignore these invalid WWN and not include them in the storage config; I suspect if we removed two 'wwn' keys from the storage config, all would work fine.
Thanks for the crash, we have enough data here to fix the issue.
@Michael,
in block-discover, we should not include the wwn key if the value is invalid (0x0000... )
If we omit the key then we'll have 'serial' which does differ and we will find the correct block devices.
@Stian
No worries; it's nothing you configured/changed as far as I can tell. We look up device paths to disk via serial or wwn; as it turns out your two disks have different serials, but a duplicate (and invalid WWN); so we'll need to fix our code to ignore these invalid WWN and not include them in the storage config; I suspect if we removed two 'wwn' keys from the storage config, all would work fine.
Thanks for the crash, we have enough data here to fix the issue.
@Michael,
in block-discover, we should not include the wwn key if the value is invalid (0x0000... )
If we omit the key then we'll have 'serial' which does differ and we will find the correct block devices.