-
Notifications
You must be signed in to change notification settings - Fork 84
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
aws-asg target: Panic while scaling in nodes #506
Comments
Maybe a better log output (from an event I just saw happen):
|
Hi @josegonzalez and thanks for this report. I believe I know the cause after looking at the stack output so will dig into a fix today hopefully. I the meantime, it'd be great to get the version information of the Nomad client(s) that are being processed by the node selector. If you're also able to share what an entry in the return object is from the node list API call for a node in the target pool looks like, that would be very helpful. |
We're using the same version (Nomad 0.12.11+ent) everywhere. Here is the first node from that list (its ineligible, not sure if that matters).
Happy to provide additional details via a hashicorp support ticket if that helps. |
Using nomad-autoscaler v0.3.3 OSS, we get the following panic (logs retrieved from our datadog logs, which may be out of order in case the ordering looks funny):
Running against Nomad 0.12.11+ent.
Happy to provide any extra details that might be useful for debugging.
The text was updated successfully, but these errors were encountered: