Actually that exactly problem appears when user executes command
crm_resource --resource p_rabbitmq-server --set-parameter max_rabbitmqctl_timeouts --parameter-value 5
in that case some RabbitMQ nodes become broken and OCF scripts can not fix them. The workaround is not to use the command above. It is not nice, as it blocks using of fix https://review.openstack.org/#/c/217738/ , but we will have to wait until I fix that particular issue.
Georgy,
Actually that exactly problem appears when user executes command _timeouts --parameter-value 5
crm_resource --resource p_rabbitmq-server --set-parameter max_rabbitmqctl
in that case some RabbitMQ nodes become broken and OCF scripts can not fix them. The workaround is not to use the command above. It is not nice, as it blocks using of fix https:/ /review. openstack. org/#/c/ 217738/ , but we will have to wait until I fix that particular issue.