Comment 2 for bug 1889395

Thanks for filing it, I'm looking into it right now.

On standalone deployment, the haproxy container is not started properly because of the way the haproxy config and the VIP are configured. Since it's a standalone deployment, this is not a immediate issue because the services aren't consumed directly via haproxy. We are looking into this specific concern with Michele.

What's happening in the failed job is that on upgrade, a technical container "haproxy_restart_bundle" tries to run "pcs resource restart haproxy" while the resource isn't started, and that shouldn't happen.

I'm having a look at the shell script which handles that restart (pacemaker_restart_bundle.sh), I'll add comments once I figured out the exact problem.