-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Nomad 0.9.3 multiple panics #6063
Comments
@scalp42 Thanks for reporting - If I'm reading the logs correctly, it look like the panic occured while somebody was trying to |
Hi @endocrimes, I'm asking the engineer, trying to gather as much info as I can. |
Per the engineer, they didn't 🤷♂ |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Output from
nomad version
Operating system and Environment details
Ubuntu 18.04
Issue
I saw the symptom live: the deployment (1 container) was in progress in the UI, reporting the one container unhealthy but Consul service checks were passing.
Reproduction steps
Apparently, the container was unhealthy during the deployment and one of our engineers clicked restart during the deployment itself. Might not be related.
Job file (if appropriate)
https://gist.github.com/scalp42/4c3cec1149be1612f82e385ea3433f0e
Nomad Client logs (if appropriate)
https://gist.github.com/scalp42/70ca6217e96982dd574c188f3829c93c
Nomad Server logs (if appropriate)
Could not find anything on servers.
The text was updated successfully, but these errors were encountered: