Description of problem: Py3-based pylint run has reported an issue with 'HSM.moveImage' method. It seems that one of the exception handlers [1] tries to refer to members that don't exist on the exception instance [2]. Unfortunately this piece of code is not covered by tests nor by basic suite. The pylint errors will be silenced for now, but this isuse should probably be investigated by the storage team. [1] https://github.com/oVirt/vdsm/blob/ec3aa6746a4ce0510fa314cb62056bf32ce6ab6d/lib/vdsm/storage/hsm.py#L1671 [2] https://github.com/oVirt/vdsm/blob/ec3aa6746a4ce0510fa314cb62056bf32ce6ab6d/lib/vdsm/storage/exception.py#L471
Can I have a scenario for reproduction/verification, please?
This is internal issue that was relevant during 4.4 development, and no was never released. We don't need to verify this.
Removing stale need infos.