Created attachment 1685606 [details]
VM overview screen

Description of problem:
A VM with runStrategy=Always has a running VMI but:
1. In cli 'RUNNING' column is empty
2. In the UI - the VM status is 'Stopping'


Version-Release number of selected component (if applicable):
OCP 4.4, CNV 2.3

How reproducible:
100%

Steps to Reproduce:
1. Create a VM with container disk and runStrategy: Always
2. Check VM status in CLI
3.Check VM status in UI

Actual results:
1. In cli 'RUNNING' column is empty

$ oc get vm,vmi -A
NAMESPACE                                       NAME                                                AGE   RUNNING   VOLUME
virt-general-vm-lifecycle-test-vm-run-strateg   virtualmachine.kubevirt.io/vm-with-container-disk   20m             

NAMESPACE                                       NAME                                                        AGE   PHASE     IP            NODENAME
virt-general-vm-lifecycle-test-vm-run-strateg   virtualmachineinstance.kubevirt.io/vm-with-container-disk   20m   Running   10.0.2.2/24   host-172-16-0-22


2. In the UI - the VM status is 'Stopping'; see attached screenshot

Expected results:
Correct VM status should be displayed (running).

Additional info:
I guess that this is caused by the fact that the information is extracted from 'running' element in the VM (?)
If so, this is problematic as 'runStrategy' and 'running' cannot coexist.

=========== VM yaml ===========
$ oc get vm vm-with-container-disk -n virt-general-vm-lifecycle-test-vm-run-strateg -oyaml
apiVersion: kubevirt.io/v1alpha3
kind: VirtualMachine
metadata:
  annotations:
    kubevirt.io/latest-observed-api-version: v1alpha3
    kubevirt.io/storage-observed-api-version: v1alpha3
  creationTimestamp: "2020-05-06T09:10:35Z"
  generation: 6
  labels:
    kubevirt.io/vm: vm-with-container-disk
  name: vm-with-container-disk
  namespace: virt-general-vm-lifecycle-test-vm-run-strateg
  resourceVersion: "1561505"
  selfLink: /apis/kubevirt.io/v1alpha3/namespaces/virt-general-vm-lifecycle-test-vm-run-strateg/virtualmachines/vm-with-container-disk
  uid: a5ba4d57-18e5-4db9-9e99-e6520702edf8
spec:
  runStrategy: Always
  template:
    metadata:
      annotations:
        ansible: '{"ansible_user": "fedora", "ansible_ssh_pass": "fedora", "ansible_become":
          true, "ansible_become_method": "sudo"}'
      creationTimestamp: null
      labels:
        kubevirt.io/domain: vm-with-container-disk
        kubevirt.io/vm: vm-with-container-disk
    spec:
      domain:
        cpu:
          cores: 1
        devices:
          disks:
          - disk:
              bus: virtio
            name: containerdisk
          interfaces:
          - masquerade: {}
            name: default
          rng: {}
        machine:
          type: q35
        resources:
          requests:
            memory: 1Gi
      networks:
      - name: default
        pod: {}
      terminationGracePeriodSeconds: 0
      volumes:
      - containerDisk:
          image: quay.io/redhat/cnv-tests-fedora-staging:31
        name: containerdisk
status:
  created: true