Description of problem: Logging and then ignoring multipathd errors when it isn't enforced is confusing to operators investigating attach or detach issues. this has been already addressed in upstream by https://review.opendev.org/c/openstack/os-brick/+/799035 Version-Release number of selected component (if applicable): How reproducible: when multipathd is not used, the error: ERROR os_brick.initiator.linuxscsi [req-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx - xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx] multipathd is not running: exit code 1: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. is shown on nova-compute logs during detach volumes and on cinder-volume logs during volume creation Actual results: the following error is show: ERROR os_brick.initiator.linuxscsi [..] multipathd is not running: exit code 1: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. Expected results: the error log should be shown only if exception is raised Additional info:
Upstream backports are under way.
Pulling in the upstream patch via RDO, https://review.rdoproject.org/r/c/rdoinfo/+/37957
Verified on: python3-os-brick-2.10.8-2.20220112064935.458bfad.el8ost.noarch On a netapp iSCSI backed Cinder deployment, without multipath installed. I had done all these operation: Booted an instance created a volume from an image attached the volume to the instance Detached the volume from the instance Delete the volume, create a new empty volume, create a new volume from an image attach/detach the last volume it from the instance. During all of these operations I didn't spot a single multi path error similar to the ones described on the initial bz comment. Neither on compute node nor on Cinder volumes log. I'd say we're good to verify.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 16.2.2), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:1001