Bug 1837670 - Specifying "Ubuntu 18.04 LTS" force the Conroe CPU model
Summary: Specifying "Ubuntu 18.04 LTS" force the Conroe CPU model
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Guest Support
Version: 2.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 2.4.0
Assignee: Karel Šimon
QA Contact: guy chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-19 19:05 UTC by Jean-Francois Saucier
Modified: 2024-01-06 04:29 UTC (History)
5 users (show)

Fixed In Version: kubevirt-ssp-operator-container-v2.4.0-49
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-28 19:10:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
yaml definition from a test VM (2.10 KB, application/octet-stream)
2020-05-19 19:15 UTC, Jean-Francois Saucier 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-32783 0 None None None 2023-09-07 23:13:54 UTC
Red Hat Product Errata RHSA-2020:3194 0 None None None 2020-07-28 19:10:18 UTC

Description Jean-Francois Saucier 2020-05-19 19:05:56 UTC 
Description of problem:
When creating a VM using the VM Wizard in the OpenShift Web Console, if a user choose "Ubuntu 18.04 LTS" for the "Operating System" choice, the resulting VM definition force the Conroe CPU model. This result in VM being unschedulable if this CPU type is not used in the cluster.

~~~
        cpu:
          cores: 1
          model: Conroe
          sockets: 1
          threads: 1
~~~


Version-Release number of selected component (if applicable):
CNV 2.3 running in OCP 4.3


How reproducible:
Every time


Steps to Reproduce:
1. Create a new VM using the wizard
2. Choose "Ubuntu 18.04 LTS" for the Operating System
3. Try to start the VM on the cluster


Actual results:
The VM is unschedulable


Expected results:
The VM start correctly


Additional info:
Comment 1 Jean-Francois Saucier 2020-05-19 19:15:59 UTC 
Created attachment 1689969 [details]
yaml definition from a test VM

This is a test vm yaml definition file. Ignore the cirros container disk, I just wanted to paste something there to create a test VM.
Comment 2 Karel Šimon 2020-05-20 06:01:08 UTC 
fixed in https://github.com/kubevirt/common-templates/pull/152
Comment 5 zhe peng 2020-07-14 03:03:05 UTC 
verify with build:
# virtctl version
Client Version: version.Info{GitVersion:"v0.26.1", GitCommit:"e40ff7965e2aadbf21131626dfa3be85524e3a2c", GitTreeState:"clean", BuildDate:"2020-02-19T16:16:36Z", GoVersion:"go1.12.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{GitVersion:"v0.30.2", GitCommit:"7c16c27ef86816a635bdb7f6ae4ebbba88751fe3", GitTreeState:"clean", BuildDate:"2020-06-30T13:21:01Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}

step:
1. Create a new VM using the wizard
2. Choose "Ubuntu 18.04 LTS" for the Operating System
3. Start the vm

the vm start currently. 
check vm yaml file
...
domain:
        cpu:
          cores: 1
          sockets: 1
          threads: 1
...

move to verified.
Comment 8 errata-xmlrpc 2020-07-28 19:10:07 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/RHSA-2020:3194
Comment 9 Red Hat Bugzilla 2024-01-06 04:29:12 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.