Bug 1810479

Summary:	VM vCPU is doubled after VM is created
Product:	OpenShift Container Platform	Reporter:	Filip Krepinsky <fkrepins>
Component:	Console Kubevirt Plugin	Assignee:	Filip Krepinsky <fkrepins>
Status:	CLOSED ERRATA	QA Contact:	Nelly Credi <ncredi>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4	CC:	aos-bugs, fkrepins, gouyang, ncredi
Target Milestone:	---	Keywords:	Regression
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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	Story Points:	---
Clone Of:	1810372	Environment:
Last Closed:	2020-05-13 22:00:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1810372
Bug Blocks:

Description Filip Krepinsky 2020-03-05 10:44:37 UTC

+++ This bug was initially created as a clone of Bug #1810372 +++

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):
4.4.0-0.nightly-2020-03-02-011520

How reproducible:
100%

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

Actual results:


Expected results:


Additional info:

Comment 3 Guohua Ouyang 2020-03-12 02:10:49 UTC

verified on 4.4.0-0.nightly-2020-03-06-170328.

Comment 5 errata-xmlrpc 2020-05-13 22:00:49 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.

https://access.redhat.com/errata/RHBA-2020:0581