Bug 1810372 - VM vCPU is doubled after VM is created
Summary: VM vCPU is doubled after VM is created
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.0
Assignee: Filip Krepinsky
QA Contact: Nelly Credi
Depends On:
Blocks: 1810479
TreeView+ depends on / blocked
Reported: 2020-03-05 05:42 UTC by Guohua Ouyang
Modified: 2020-07-13 17:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: VM template sockets were not reflected in the final VM created by the wizard Consequence: VM vCPU was doubled/.. after VM is created Fix: VM template sockets/cores/thread are reflected when creating a VM. Result: numberof vCPUs is correct
Clone Of:
: 1810479 (view as bug list)
Last Closed: 2020-07-13 17:18:18 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 4652 0 None closed Bug 1810372: fix wrong sockets/threads when using Custom flavor 2020-07-02 18:34:14 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:18:44 UTC

Description Guohua Ouyang 2020-03-05 05:42:44 UTC
Description of problem:
Create a VM with custom vCPUs, after the VM or VM template is created, the vCPUs are doubled in detail page. It may caused by the CPU sockets are 2.

Edit the flavor and save, it shows the same value which is just inputed and the cpu socket changes to 1.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create a VM with custom flavor.
2. Verify CPU in detail page.

Actual results:

Expected results:

Additional info:

Comment 4 Guohua Ouyang 2020-03-31 07:31:05 UTC
verified on 4.5.0-0.nightly-2020-03-29-224016.

Comment 5 errata-xmlrpc 2020-07-13 17:18:18 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.