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

Enabling disable_remote_exec removes output of Consul leader in self-hosted UI #1937

Closed
rbink opened this issue Apr 11, 2016 · 4 comments
Closed
Labels
type/bug Feature does not function as expected

Comments

@rbink
Copy link

rbink commented Apr 11, 2016

We are using Consul v0.6.3 - with a cluster consisting of one leader and two followers - and self-hosted UI. We recently enabled disable_remote_exec and created a health check to validate the correct state of this property. The output of the health check - as reported in the UI - is as expected, however the output of the health check script of the Consul leader is not displayed in Consul UI. The output of the health check script of the Consul followers is displayed correctly in Consul UI. Both the Consul leader and followers are using the same script, installed in the same location with exactly the same rights. We were able to reproduce this problem and we did analyze the Consul codebase in order to find the cause of this problem, however without success.

leader: no output

leader

a follower: output

follower

@slackpad slackpad added the type/bug Feature does not function as expected label Apr 11, 2016
@slackpad
Copy link
Contributor

Hi @rbink last night (!) we discovered an issue where there could be a side effect that cleared the output inadvertently. Is it possible for you to try out this change and see if it fixes the issue you are seeing?

#1934

@rbink
Copy link
Author

rbink commented Apr 12, 2016

Hi slackpad. Thanks for your very fast response. Good to read that you most likely found the same issue and fixed it. We raised a ticket to test your fix and get back to you when completed (which might take some time).

@rbink
Copy link
Author

rbink commented May 13, 2016

Hi slackpad, we recently updated Consul 0.6.3 to 0.6.4 and noticed that 0.6.4 did not contain the fix (as you mentioned as well). We will verify the fix once it has been released.

@slackpad
Copy link
Contributor

This was fixed in #1934.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Feature does not function as expected
Projects
None yet
Development

No branches or pull requests

2 participants