Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Haproxy will report a backend's status as 'UP' when there are no #24

Merged
merged 1 commit into from
Oct 3, 2017

Conversation

bjhaid
Copy link
Contributor

@bjhaid bjhaid commented Oct 2, 2017

backend configured, this PR uses backend 'weight' instead of backend
'status' from the haproxy stats socket to represent a backend's state as
this represents the total weights of the backends and will be 0 when
there's no backend configured.

backend configured, this PR uses backend 'weight' instead of backend
'status' from the haproxy stats socket to represent a backend's state as
this represents the total weights of the backends and will be 0 when
there's no backend configured.
@lollipopman
Copy link
Contributor

looks good, can you add note in the commit message that 'status' will report UP when there are no backends

@lollipopman
Copy link
Contributor

missed the header, this looks good 👍

@bjhaid
Copy link
Contributor Author

bjhaid commented Oct 2, 2017

The error in 1.9.3 travis is a bug with the version of bundler used:

rubygems/bundler#3558

We can include installing a newer version of bundler in before_install but I'll merge this PR regardless tomorrow

@lollipopman lollipopman merged commit c0a3f0a into master Oct 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants