Project

General

Profile

Bug #27334

Remove hardcoded max values of oVirt CR

Added by Baptiste Agasse 5 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources - oVirt
Target version:
-
Difficulty:
trivial
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

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.

Associated revisions

Revision de0c08b1 (diff)
Added by Baptiste Agasse 5 months ago

Fixes #27334 - Remove hardcoded max values for ovirt

History

#1 Updated by The Foreman Bot 5 months ago

  • Assignee set to Baptiste Agasse
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6909 added

#2 Updated by Baptiste Agasse 5 months ago

  • Found in Releases 1.20.0 added

#3 Updated by The Foreman Bot 5 months ago

  • Fixed in Releases 1.23.0 added

#4 Updated by Anonymous 5 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF