Israel I need you to confirm if this VM didn't went through a cluster change. If it didn't it means we have some other place that caused the cpu profile to be null.
The VM is create from template, it did not change cluster.
In the beginning of the test we update cpu socket and core, and then start the VM.
Verify with: 18.104.22.168-0.1.1.el6
OS Version: RHEL - 7.2 - 13.0.el7ev
Kernel Version: 3.10.0 - 327.30.1.el7.x86_64
KVM Version: 2.3.0 - 31.el7_2.21
LIBVIRT Version: libvirt-1.2.17-13.el7_2.5
VDSM Version: vdsm-4.17.35-1.el7ev
1. Create VM
2. Hot plug CPU to VM
3. Run Automation tests.
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.