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
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
Cores should be number of cores set in the template
Created redmine issue http://projects.theforeman.org/issues/23916 from this bug
This happens when selecting a template or filling in an image.
The number of cores shown in APIv3 is the total virtual CPUs count (cores and sockets together) but APIv4 shows only the cores.
Upstream bug assigned to email@example.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23916 has been resolved.
Verified with Sat 6.4 snap 18.
Used reproducer from OP. The template's CPU settings was 2:3:1 which resulted in Sockets==2 and Cores==3 in WebUI.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.