Description of problem: Openstack supports enhanced redundancy with dm-multipath on Cinder and Nova. Currently configuring multipath is an error prone manual post deployment config task, which involves installing/starting service(s) plus changing config settings on Cinder/Nova. Adding Tripleo support for automation of multipath configuration would be beneficial. This should probably be an RFE. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: LP specs I added a while back nothing happens since. https://blueprints.launchpad.net/tripleo/+spec/multipath-support
*** Bug 1582974 has been marked as a duplicate of this bug. ***
Please do not change the target release flags. The feature was pushed to osp-17, and will be considered for backports after QE has verified the feature.
My initial upstream effort for tripleo to drive the multipath configuration was inadequate. Further work is required, which is why the target has been pushed out to OSP-17. But once the initial work is complete, we will try to backport the solution to earlier releases where feasible.
There is a semi manual approach customers can use until it is automated via tripleO https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/storage_guide/index#multipath-configuration
*** Bug 1856601 has been marked as a duplicate of this bug. ***
Moving priority and severity back. Please do not set them urgent for situations like this. I have a status update for today's cinder meeting, but the situation is very complex.
FYI, happened to test this yaml on 16.2 with netapp iSCSI, working great for both new deployment as well as updating a pre-existing deployment.
Verified on: openstack-tripleo-heat-templates-14.3.1-0.20220607161058.ced328c.el9ost.noarch Successfully managed to deploy a Netapp iSCSI multipathed deployment using multipathd.yaml. Also tested deployment with a custom multipath.conf file. 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 17.0 (Wallaby)), 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/RHEA-2022:6543