HTTPS request to designate randomly fail
Bug #2067277 reported by
David Negreira
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The following happens when we have a juju designate cluster with HA and SSL enabled.
When a unit is put on pause, for example with:
- juju run-action designate/2 pause
The apache service is not stopped, and the haproxy from pacemaker/corosync will still route the connection and the server will return 503, since the designate service is stopped but not apache.
The connections to the other units that are not paused work well as expected, but in a cluster of three servers we will get a 503 every three requests.
The fix should be to add the apache2 to the list of services and stop it when necessary.
To post a comment you must log in.
Seems this is not a bug of designate, but of the juju deployment.