Bug #23916
closedCreate Host -> RHEV Image: Incorrect CPU cores count filled when using APIv4
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1589779
Description of problem:
In a host creation form, when I select a RHEV CR that uses APIv4 and select some image in the OS tab, I get incorrect number (1) in Cores field in the VM tab. This does not happen with APIv3. I guess this is caused by actually using processor count instead of core count.
Version-Release number of selected component (if applicable):
Sat 6.4 snap 7
How reproducible:
Deterministic
Steps to Reproduce:
1. Have a Sat, RHEV with some template with cpu_count!=cores!=1, this RHEV added to Sat (with apiv4==true) and Image assigned to it, using that template
2. Hosts -> Create Host
3. Select RHEV as provider, go to OS tab, select arch + OS, select Image Based
4. Select the image, go to VM tab
Actual results:
Cores==1
Expected results:
Cores should be number of cores set in the template
Updated by Ori Rabin over 6 years ago
- Status changed from New to Assigned
- Assignee set to Ori Rabin
Updated by Ori Rabin over 6 years ago
- Related to Bug #22117: Add support for specifying number for sockets for oVirt added
Updated by Ori Rabin over 6 years ago
- Assignee changed from Ori Rabin to Shira Maximov
Updated by Ori Rabin over 6 years ago
- Has duplicate Bug #23915: Create Host -> RHEV Image: Incorrect CPU cores count filled when using APIv4 added
Updated by Ori Rabin over 6 years ago
- Related to Tracker #19568: Migrate to oVirt APIv4 API added
Updated by Shira Maximov over 6 years ago
- Triaged set to No
- Pull request https://github.com/abenari/rbovirt/pull/125 added
Updated by Ivan Necas over 6 years ago
- Target version set to 1.18.1
Proposing for 1.18.1, as this makes the usage of ovirt integration quite unfriendly.