Bug 1447969 - HA proxy is not functioning as expected
Summary: HA proxy is not functioning as expected
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: GA
: 5.9.0
Assignee: Nick Carboni
QA Contact: luke couzens
URL:
Whiteboard: black:HA
Depends On: 1479050
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-04 10:40 UTC by luke couzens
Modified: 2017-10-24 15:03 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-24 15:03:34 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 luke couzens 2017-05-04 13:24:05 UTC
The last build I got it working on was 5.8.0.11

Comment 3 Nick Carboni 2017-05-08 18:44:26 UTC
Based on the guide it doesn't look like the appliances running HAProxy/keepalived should be cfme boxes. I'm curious why this would change from version to version of cfme? I don't think cfme code is involved at all in the HAProxy failover process.

Are you sure all the correct firewall settings and kernel params are in place?
These would not be set correctly on an appliance out of the box, but needed to be set for a base RHEL 7.2 machine (which is what the doc specifies for the HAProxy appliances).

Comment 5 luke couzens 2017-05-16 08:07:10 UTC
Hi Nick, 

Just clearing need info. Ping me if you need another env setup.

Cheers,
Luke

Comment 6 Gregg Tanzillo 2017-06-01 22:03:56 UTC
Hey Luke, would you mind setting up another env and seeing if you can recreate the bug again? This we we can access it directly to troubleshoot. Thanks!

Comment 21 Nick Carboni 2017-07-31 15:49:12 UTC
Brett,

Any progress on this? Was a bug filed with the HA team?

Comment 26 Marianne Feifer 2017-10-24 15:03:34 UTC
Dependency on https://bugzilla.redhat.com/show_bug.cgi?id=1479050 has been closed.


Note You need to log in before you can comment on or make changes to this bug.