Nomad crashes when submitting job "runtime error: index out of range [0] with length 0" #8875
Comments
|
Hi @spuder. Sorry to hear about that. It looks like there's a null pointer bubbling up from the new expose hook. We'll get that fixed ASAP, but in the meantime if you omit the cc @nickethier |
|
We should fix the null pointer (adding validation), but the job really just needs a |
|
Great thank you. Adding the missing networking in bridged mode and removing expose = true did fix the crash. Is there an existing issue for the expose = true bug? If so I'll link and close this out. |
|
There isn't an issue yet, so let's leave this open to track the fix. Turns out there has been validation for the missing network block since forever, it's just that it exists in a validation hook that runs after this expose mutator hook 🤕 |
In #7800, Nomad would automatically generate a port label for service checks making use of the expose feature, if the port was not already set. This change assumed the group network would be correctly defined (as is checked in a validation hook later). If the group network was not definied, a panic would occur on job submisssion. This change re-uses the group network validation helper to make sure the network is correctly definied before adding ports to it. Fixes #8875
In #7800, Nomad would automatically generate a port label for service checks making use of the expose feature, if the port was not already set. This change assumed the group network would be correctly defined (as is checked in a validation hook later). If the group network was not definied, a panic would occur on job submisssion. This change re-uses the group network validation helper to make sure the network is correctly definied before adding ports to it. Fixes #8875
In hashicorp#7800, Nomad would automatically generate a port label for service checks making use of the expose feature, if the port was not already set. This change assumed the group network would be correctly defined (as is checked in a validation hook later). If the group network was not definied, a panic would occur on job submisssion. This change re-uses the group network validation helper to make sure the network is correctly definied before adding ports to it. Fixes hashicorp#8875
|
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. |
Our company is evaluating using nomad, however nomad frequently crashes when a user submits a job.
The main error is:
Version
0.12.4
Nomad Job
Server Logs
The text was updated successfully, but these errors were encountered: