Actions
Bug #27334
closedRemove hardcoded max values of oVirt CR
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - oVirt
Target version:
-
Difficulty:
trivial
Triaged:
No
Pull request:
Description
Related to #27086. oVirt max cpus, memory, cores values are hardcoded and it's not possible ATM to retrieve the good values from the oVirt API. As actual hardcoded values are very low (memory, cpus...) compared to values actually supported by oVirt, it block VMs creation with memory > 16GB from foreman that are valid on oVirt POV.
Actions