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

failing health checks: This account is currently not available #907

Closed
ryane opened this issue Dec 15, 2015 · 2 comments
Closed

failing health checks: This account is currently not available #907

ryane opened this issue Dec 15, 2015 · 2 comments

Comments

@ryane
Copy link
Contributor

@ryane ryane commented Dec 15, 2015

When you build a new cluster, most of the consul health checks fail with the error:

This account is currently not available.

This appears to be because the shell for the consul user is set to /sbin/nologin. However, it is not clear why this is suddenly broken so we need to track down what has changed. This is affecting master and previous releases.

@ryane
Copy link
Contributor Author

@ryane ryane commented Dec 15, 2015

master is fixed by #908. tagged releases are still broken

@stevendborrelli
Copy link
Contributor

@stevendborrelli stevendborrelli commented Dec 30, 2015

Given that 0.5.1 is released, I think we can close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants