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
The order of auto-injected constraint{} for signal availability some times changes order, causing the job to be rolled / deployed / restarted when there are no functional different between the two.
it would be nice if the order in RTarget did not matter, as SIGHUP,SIGTERM and SIGTERM,SIGHUP are exactly the same
sort them before adding them automatically
make this generic and always split RTarget by , and sort them before evaluating the job
The text was updated successfully, but these errors were encountered:
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.
Nomad version
v0.7.1
Issue
The order of auto-injected
constraint{}
for signal availability some times changes order, causing the job to be rolled / deployed / restarted when there are no functional different between the two.it would be nice if the order in
RTarget
did not matter, asSIGHUP,SIGTERM
andSIGTERM,SIGHUP
are exactly the sameRTarget
by,
and sort them before evaluating the jobThe text was updated successfully, but these errors were encountered: