Deployment stuck when trying to raise haproxy_global_maxconn

Solution Verified - Updated -

Issue

After bumping haproxy_global_maxconn to a very high value :

    tripleo::haproxy::haproxy_global_maxconn: 5120001

Deployment stuck at container-startup-config/step_3:

2024-01-17 12:17:21,246 p=193042 u=stack n=ansible | 2024-01-17 12:17:21.245192 | 8e903c10-915b-4180-a318-f9111cf44bf2 |   INCLUDED | /usr/share/ansible/roles/tripleo_container_manage/tasks/create.yml | controller-0
2024-01-17 12:17:21,307 p=193042 u=stack n=ansible | 2024-01-17 12:17:21.306905 | 525400aa-ff3f-f048-27fc-00000000b979 |       TASK | Create containers managed by Podman for /var/lib/tripleo-config/container-startup-config/step_3

Environment

  • Red Hat OpenStack Platform 17.1

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