haproxy logs shows redis down: redis/overcloud-controller-1.internalapi.localdomain is DOWN, reason: Layer7 timeout

Solution In Progress - Updated -

Issue

  • In haproxy journalctl logs, redis is shown as DOWN when it is actually seen as running in pcs status output:
overcloud-controller-0 haproxy[146671]: Server redis/overcloud-controller-1.internalapi.localdomain is DOWN, reason: Layer7 timeout, info: " at step 5 of tcp-check (expect string 'role:master')", check duration: 10001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
overcloud-controller-0 haproxy[146671]: Server redis/overcloud-controller-2.internalapi.localdomain is DOWN, reason: Layer7 timeout, info: " at step 5 of tcp-check (expect string 'role:master')", check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.

Environment

  • Red Hat OpenStack Platform

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.