Description of problem:
Selecting multiple cores per socket not working against vmware provider (image cloning)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Defaine new VNware ESX host from the image.
2. Assign different to default=1 value to Cores per Socket.
3. Create a host
Deployed machine shows "Cores per socket" = 1
Deployed machine shows "Cores per socket" given value as well as machine resizes on several sockets in Vmware cluster
Created redmine issue http://projects.theforeman.org/issues/14038 from this bug
Upstream bug assigned to firstname.lastname@example.org
After digging a bit deeper I've found the needed part on the fog part and opened a PR there: https://github.com/fog/fog-vsphere/pull/29
Created attachment 1133206 [details]
A patch against fog rebased to forg 1.24.1 (sat 6.1)
Additional patch to the foreman's on fog side to support setting the cores per socket setting.
To apply (when not patching the rpm):
git init; git add .; git commit -m 'original' # optional just to track the changes
patch -p1 < numcorespersocket.patch
Moving to POST since upstream bug http://projects.theforeman.org/issues/14038 has been closed
Applied in changeset commit:17c277d5733cf4b814f3d5b357269f38bafcfa8f.
Tested with sat62-snap12.1
Had selected the below options for the VM Tab :
Cores per socket: 2
After submitting the page found the below stuff,
Cores per socket: 1
~]# rpm -qav tfm-rubygem-fog-vsphere
Created attachment 1162543 [details]
cores per socket does get updated
VERIFIED with sat62-snap(GA)-13.1
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.