Constraint numeric comparison

[onlyjob]

For some reason job with

      constraint {
        attribute = "${attr.cpu.numcores}"
        operator  = ">"
        value     = "10"
      }

Is placed to machines with cpu.numcores == 8.

Why? Even if constraints are not mandatory but merely advisory a job should have been placed to client with 10+ cores, right?

[dadgar]

I changed the title of the issue. Constraints are compared lexicographically. We should parse it as a number if possible however. Marking as an enhancement

[onlyjob]

Thanks, but according to your comment it looks like a bug...

[onlyjob]

Is there any hope to get it fixed?

[tgross]

It looks like @MrJacek has a patch here MrJacek@74e43fe that was never submitted as a PR. I wonder if we could get him to submit that?

[MrJacek]

It was submitted as a PR in 4856 but rejected :)

[tgross]

Ah, I see that now. It does look like this should be supported following #4783 where attributes get parsed into numbers, but I just verified it's still lexicographically sorting the constraints. I'll dig into this because the behavior seems like a gotcha even if it's documented.

[onlyjob]

Thanks, @tgross. I agree that documenting this bug is not enough. It should be fixed as current behaviour is illogical, counter-intuitive and potent to cause very undesirable placement issues.

It does not seem to be a difficult technical issue to fix, right?

[github-actions]

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.