Cannot restart Update of the OSP13z16 controllers.

Solution Verified - Updated -


When restarting an update of OSP13z16 overcloud on a node where the RabbitMQ service is deployed it may fail with: Unable to find constraint. The complete message looks similar to the following output:

FAILED! => {"changed": true, "cmd": ["pcs", "constraint", "remove", "cli-ban-rabbitmq-bundle-on-ctl0"], "delta": "0:00:00.432549", "end": "2021-07-03 18:17:02.513329", "msg": "non-zero return code", "rc": 1, "start": "2021-07-03 18:17:02.080780", "stderr": "Error: Unable to find constraint - 'cli-ban-rabbitmq-bundle-on-ctl0'", "stderr_lines": ["Error: Unable to find constraint - 'cli-ban-rabbitmq-bundle-on-ctl0'"], "stdout": "", "stdout_lines": []}

See the original bz#1979010 where it was first reported.


Update from any OSP13 to OSP13z16.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content