Description of problem: During minor update of a HA controller, we have a script called pacemaker_restart_bundle.sh that is in charge of restarting the local instance of an HA resource after some configuration change. The way the resource is restarted depends on the type of the resource and its current state in the cluster. When the resource is in failed state, the script invokes pcs with an invalid command line, which in turns logs an error and does not restart the resource as expected, e.g.: "stdout: Wed Jun 9 16:45:29 UTC 2021: openstack-cinder-volume is currently not running on 'controller-0', cleaning up its state to restart it if necessary", "", "stderr: Error: Specified option '--node' is not supported in this command" ] } Version-Release number of selected component (if applicable): 16.2 How reproducible: When a resource a in failed state on a node Steps to Reproduce: 1. make a clone resource fail to start on a controller, this will block it and leaves it in failed state. 2. perform a minor upgrade on that node Actual results: The resource stays in failed state Expected results: The resource should have been given a chance to restart Additional info:
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 (Moderate: Red Hat OpenStack Platform 16.2 (openstack-tripleo-heat-templates) security update), 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/RHSA-2022:0995