Created attachment 1575266 [details] Additional info Description of problem: Manila API service does not failover to active controller node Version-Release number of selected component (if applicable): How reproducible: Failed 100% 2:2 tries Steps to Reproduce: Test case: RHELOSP-27529 test_manila_api_service_survives_loss_of_one_service 1. Disable one of the Manila API services on a controller node. This is most easily accomplished by either suspending or shutting off a controller node that is running an instance of the Manila API service. Expected Result: One of the Manila API services shall be disabled. 2. Issue a "manila list" command on the undercloud nod and ensure that the command completes successfully. Expected Result: The "manila list" command shall complete successfully. Actual results: Manila API service does not failover after controller-2 is shutdown Expected results: The "manila list" command shall complete successfully. Additional info: See attached .pdf file
Created attachment 1576281 [details] New attchment, obsoletes earlier attachment Posted new attachment, BZ1715529-manilaControllerFailover-060219.pdf Previous attachment is obsolete.
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, 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-2019:2811