Description of problem: The tripleo_multipathd role will successfully deploy the multipathd daemon and configure services to access /etc/multipath.conf. However, if the THT parameters associated with multipathd are modified, an error occurs when a stack update attempts to refresh the multipath.conf file. How reproducible: Always Steps to Reproduce: 1. Use the tripleo_multipath role to deploy the multipathd daemon 2. Modify any THT multipathd parameter 3. Perform a stack update Actual results: The stack update fails when the new /etc/multipath.conf file is copied to the containers that need it: Error: 2 errors occurred: * error copying to container: copier: put: error creating "/etc/multipath.conf": copier: put: error removing item to be overwritten "/etc/multipath.conf": unlinkat /etc/multipath.conf: device or resource busy * error copying from host: copier: get: "/etc/multipath.conf": error copying /etc/multipath.conf: io: read/write on closed pipe Expected results: The stack update succeeds Additional info: I suspect the problem may be related to recent versions of podman using file locks. The problem did not occur back when the feature was initially developed.
Retargeting this for 16.2 in order to align it with bug #2047705 (the 16.2 BZ associated with tripleo deployment of multipath). It's still POST because the fix has already merged on upstream stable/train, and we just need to wait for the first compose for 16.2.3.
Verified on: openstack-tripleo-heat-templates-11.6.1-2.20220409014848.7c89b16.el8ost.noarch tripleo-ansible-0.8.1-2.20220406160113.2d0ab9a.el8ost.noarch Successfully deployed a netapp iSCSI backed multipath deployment via THT template. After initial deployment completed, I had added a customized multipath config and updated the overcloud. Which again resulted in a successful deployment, including customization of multipath config. 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.3 (Train)), 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:4793