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 "Placement Metrics" table in the output of nomad alloc status -verbose does not always include all the relevant scoring information. It seems like the list of scorerNames (and therefore the table header) are built only based on the firstScoreMetaData object. This means that, if a later ScoreMetaData object contains a score that is not in the first one, then that information will not be printed.
Reproduction steps
Create a job with an affinity for a particular node, but not one strong enough to actually place the allocation on that node.
Run nomad alloc status -verbose <allocID>
Expected Result
The "Placement Metrics" table should include a node-affinity column, as per the docs.
Actual Result
The "Placement Metrics" table only includes that column if the node the allocation was placed on is the one that the job had the affinity for.
Notice there is no node-affinity column in the nomad alloc status output, but there is a node-affinity score in the secondScoreMetaData returned from the API:
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
Nomad v1.1.2 (60638a086ef9630e2a9ba1e237e8426192a44244)
Operating system and Environment details
CentOS 7
Issue
The "Placement Metrics" table in the output of
nomad alloc status -verbose
does not always include all the relevant scoring information. It seems like the list ofscorerNames
(and therefore the table header) are built only based on the firstScoreMetaData
object. This means that, if a laterScoreMetaData
object contains a score that is not in the first one, then that information will not be printed.Reproduction steps
nomad alloc status -verbose <allocID>
Expected Result
The "Placement Metrics" table should include a
node-affinity
column, as per the docs.Actual Result
The "Placement Metrics" table only includes that column if the node the allocation was placed on is the one that the job had the affinity for.
Job file (if appropriate)
Nomad Server logs (if appropriate)
Nomad Client logs (if appropriate)
Notice there is no
node-affinity
column in thenomad alloc status
output, but there is anode-affinity
score in the secondScoreMetaData
returned from the API:The text was updated successfully, but these errors were encountered: