Project

General

Profile

Actions
Copy link

Bug #27334

closed

Remove hardcoded max values of oVirt CR

Added by Baptiste Agasse almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Baptiste Agasse
Category:
Compute resources - oVirt
Target version:
-
Difficulty:
trivial
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/6909
Fixed in Releases:
1.23.0
Found in Releases:
1.20.0
Red Hat JIRA:

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
Copy link
 #1

Updated by The Foreman Bot almost 5 years ago

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

Updated by Baptiste Agasse almost 5 years ago

  • Found in Releases 1.20.0 added
Actions
Copy link
 #3

Updated by The Foreman Bot over 4 years ago

  • Fixed in Releases 1.23.0 added
Actions
Copy link
 #4

Updated by Anonymous over 4 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF