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
@panjiang Thanks for the report. I'm looking into the issue. It appears that in the original jobspec parser in the CLI would filter out cases where the distinct_hosts constraint was set to false. This could explain why the feasibility check does not consult the value passed.
However, as you noted, when using jobspec2—the HCL2 version of the jobspec—the value is not being dropped from the parsed JSON and is being incorrectly observed by the feasibility check. This also would appear to impact users who are submitting jobs to the cluster using the JSON-jobspec directly.
I'm still looking into the issue and will add more to the issue as I learn more.
I want to disable
distinct_hosts
in certain env, but it not working as expected.Then I find the source code, is not reading the value config.
The text was updated successfully, but these errors were encountered: