Bug 1911213

Summary: Wrong and misleading warning for VMs that were created manually (not from template)
Product: OpenShift Container Platform Reporter: Chen Yosef <cyosef>
Component: Console Kubevirt PluginAssignee: Yaacov Zamir <yzamir>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.7CC: aos-bugs, gouyang, yzamir
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:49:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
screen shot of the warning none

Description Chen Yosef 2020-12-28 07:43:15 UTC
Created attachment 1742519 [details]
screen shot of the warning

Description of problem:
When creating a VM (using Kubevirt API or just with a simple yaml file), I see a "pending change" warning in the UI:
I am running an OCP 4.7 nightly build from last week, with CNV 2.5.2 installed. Is this a known issue ?

Version-Release number of selected component (if applicable):
OCP 4.7 nightly build
CNV 2.5.2

How reproducible:

Steps to Reproduce:
1. Create a VM using a simple yaml file

Actual results:
A misleading warning is shown in the VM details screen, saying that there are pending changes and that will be applied after restarting the VM. Restarting the VM doesn't help and the warning still displayed.

Expected results:
1. No warning at all is shown.
2. If the decision is to display warning for VMs that were not created using template, than the warning message should reflect it and not call for action. 

Additional info:

Comment 1 Yaacov Zamir 2020-12-28 08:14:40 UTC
VM YAML used to reproduce:

apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachineInstance
    special: vmi-fedora
  name: vmi-fedora
      - disk:
          bus: virtio
        name: containerdisk
      - disk:
          bus: virtio
        name: cloudinitdisk
      rng: {}
      type: ""
        memory: 1024M
  terminationGracePeriodSeconds: 0
  - containerDisk:
      image: registry:5000/kubevirt/fedora-cloud-container-disk-demo:devel
    name: containerdisk
  - cloudInitNoCloud:
      userData: |-
        password: fedora
        chpasswd: { expire: False }
    name: cloudinitdisk

The difference found was CPU:
in VM cpu was {}
in VMI cpu was {cores: 1 sockets: 1 threads: 1}

Comment 5 errata-xmlrpc 2021-02-24 15:49:10 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.