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
▶ nomad eval status 86001
ID = 860013f2
Create Time = 32m34s ago
Modify Time = 25m45s ago
Status = failed
Status Description = evaluation reached delivery limit (3)
Type = _core
TriggeredBy = alloc-stop
Priority = 200
Placement Failures = false
After this happens, you'll get errors like the following:
▶ nomad job run volume2.nomad
==> Monitoring evaluation "c19b6557"
Evaluation triggered by job "example2"
Evaluation within deployment: "9f0988d5"
Evaluation status changed: "pending" -> "complete"
==> Evaluation "c19b6557" finished with status "complete" but failed to place all allocations:
Task Group "cache" (failed to place 1 allocation):
* Constraint "missing CSI plugins" filtered 2 nodes
Evaluation "d5719861" waiting for additional capacity to place remainder
The text was updated successfully, but these errors were encountered:
With a bit of work with -coverprofile I was able to reproduce this with a new unit test that covers the controller unpublish part of volume claim GC. This panic is because #7218 isn't implemented yet.
Unfortunately because the names of RPCs are just strings, the compiler won't save you from implementing an RPC that doesn't exist and in that scenario you get this silly stack trace because of all the reflection in net/rpc. The test snippet below will exercise the same failure mode:
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
During volume claim release, we're throwing a panic that's in turn corrupting state such that we can no longer schedule volumes.
The eval status for this is:
After this happens, you'll get errors like the following:
The text was updated successfully, but these errors were encountered: