You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i try to plan job:
failed to process eval: runtime error: invalid memory address or nil pointer dereference
In a test virtual machine (kvm) with the same version of nomad, all jobs work fine, without errors.
When upgrading from older versions of Nomad, the reschedule policy block may be
nil. There is logic to handle this safely in the `NextRescheduleTimeByTime` used
for allocs on disconnected clients, but it's missing from the
`NextRescheduleTime` method used by more typical allocations. Return an empty
time object in this case.
Fixes: #24846
Hi @epachirkov! I took a quick look at this and it seems like we're missing a nil pointer check when checking for the next reschedule time for an allocation that's not on a disconnected client. I've got a draft PR up with a fix here: #24893 (but note this won't be backported to 1.7.x CE, only the 1.9.x series gets backported bug fixes in CE).
@epachirkov I want to make sure we've root-caused this panic. Can you share the jobspec you were trying to plan? And was it an existing job that you were updating, or a new job? Does the panic happen every time you plan this jobspec on this particular cluster?
Nomad version
Nomad v1.7.5
BuildDate 2024-02-13T15:10:13Z
Revision 5f5d464
Operating system and Environment details
CPU i9-13900. Ubuntu 22.04, 3-node nomad cluster.
Issue
When i try to plan job:
failed to process eval: runtime error: invalid memory address or nil pointer dereference
In a test virtual machine (kvm) with the same version of nomad, all jobs work fine, without errors.
Reproduction steps
nomad job plan resec.hcl
Expected Result
plan and run job
Actual Result
The text was updated successfully, but these errors were encountered: