Red Hat Bugzilla – Bug 845164
Connection execution during move restart haproxy
Last modified: 2015-05-14 18:57:29 EDT
Description of problem:
HAProxy gets started even if it was stopped upon a gear move of a scalable app
This happens on a scale-up/scale-down/update-namespace etc also
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a scalable app and add some gears (scale-up or add mysql)
2. Stop Haproxy, and move the mysql gear (or scale-up)
Haproxy is alive again automatically
Haproxy should maintain its state after the end of operation
The connection hooks do a reload of the haproxy, they should not start haproxy if it was stopped already
Fixed with git commit f429010a9c99cdfb13454575fbd1e638ba53b0da -- waiting for pull request: https://github.com/openshift/crankcase/pull/322 to get tested and merged in.
rchopra merged the pull request.
Changed to use an consistent init-script like name with commit de72b3618a6c86cebc3e8b18dd8af57448b8b224.
This fix has also been applied to STG by rchopra -- was needed for fixing bugz 844912.
Verified on stg_228,
both after move mysql gear and scal-up
the haproxy still be stopped
[root@localhost mytest]# rhc app cartridge status -a qs1jbossas -c haproxy-1.4 -p 111111
HAProxy instance is stopped