Adding a vip after deployment causes connection-refused errors

Bug #2001888 reported by Vern Hart
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Masakari Charm
New
Undecided
Unassigned

Bug Description

After deployment, I realized I forgot to add the vip. After adding the vip, haproxy was listening on port 15868 but nothing was listing on port 15858. All requests to the vip endpoints were getting the following SSL error which effectively means the SSL connection fails to start because the connection is closed. This is what happens when none of the hosts behind haproxy are responding.

  OpenSSL SSL_connect: SSL_ERROR_SYSCALL

Checking the apache2 service status, it had not been restarted since the units were deployed. The simple solution was to restart apache2 on all masakari units with a juju-run command:

  juju run -a masakari systemctl restart apache2

Obviously, I would expect the charm to do that automatically.

After doing this, all vip endpoints behaved as expected.

We're running yoga/stable channel (2944cf7 2022-07-20 41).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.