This message was deleted.
# harvester
a
This message was deleted.
b
Ok, Maybe I take this back.
But only part of it.
It LOOKS like it's actually respecting the memory limit, but not the CPU limits.
Also, if that's the case, it's not groking the math right for the limits error messages.
Maybe this is just a bug.
The CPU limits for the project are set to 24 cores and 48 Gi
The VM Default Resource Limit are set above (16 cores and 32 Gi)
A VM with 24 cores and 40 Gi does not run, but the error message references a 24Gi limit, which is only set as the reserves limit.
I guess there would be two seperate issues to be filed on github: One for the missing docs, two for bad evaluations on the CPU Limits and Memory Error message. I'm happy to fill that out, but it would be nice if someone could confirm that's how they're suppose to work?