Bug 1936932

Summary:	Common templats - VirtualMachine api version should be updated to kubevirt.io/v1
Product:	Container Native Virtualization (CNV)	Reporter:	Ruth Netser <rnetser>
Component:	SSP	Assignee:	Andrej Krejcir <akrejcir>
Status:	CLOSED ERRATA	QA Contact:	Sarah Bennert <sbennert>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	4.8.0	CC:	akrejcir, cnv-qe-bugs, fdeutsch, sbennert
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 14:28:41 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:
Embargoed:

Description Ruth Netser 2021-03-09 13:58:17 UTC

Description of problem:
Common templats - VirtualMachine api version should be updated to kubevirt.io/v1
Currently the templates are shipped with kubevirt.io/v1alpha3, but in 4.8.0, VMs are created with kubevirt.io/v1

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fabian Deutsch 2021-03-30 12:21:18 UTC

There should be no issue, because the old apiversion will be supported for a while. Do you see any functional impacts?
If there is not, is it fair to lower severity?

Comment 2 Ruth Netser 2021-03-30 13:17:20 UTC

I prefer to wait for bug 1936926 fix and verify we're OK with new and old apiversion

Comment 4 Sarah Bennert 2021-05-13 17:43:03 UTC

(In reply to Ruth Netser from comment #2)
> I prefer to wait for bug 1936926 fix and verify we're OK with new and old
> apiversion

Will await resolution of bug 1936926

Comment 5 Sarah Bennert 2021-05-18 21:08:13 UTC

Creating a VM using the CLI works using either version in the manifest, v1 or v1alpha3.


The console however is using the v1alpha3 API with a v1 VM manifest, which fails.


POST https://console.example/api/kubernetes/apis/kubevirt.io/v1alpha3/namespaces/default/virtualmachines

{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {
    
  },
  "status": "Failure",
  "message": "the API version in the data (kubevirt.io/v1) does not match the expected API version (kubevirt.io/v1alpha3)",
  "reason": "BadRequest",
  "code": 400
}

# Openshift cluster
4.8.0-fc.2

# HCO Operator
registry.redhat.io/container-native-virtualization/hyperconverged-cluster-operator@sha256:508529059070b9fc4cb701416f7911e6954b15424af7e68ff161e93fda805dd3
hyperconverged-cluster-operator-container-v4.8.0-51

# SSP Operator
registry.redhat.io/container-native-virtualization/kubevirt-ssp-operator@sha256:572b2ed7d34667520874e99402863f3011cd6f13452600451e715a4230c1f9b1
kubevirt-ssp-operator-container-v4.8.0-33

Comment 6 Fabian Deutsch 2021-05-19 06:57:37 UTC

Scope of this bug is to ensure that all templates are using the kubevirt.io/v1 api.

If the UI is setting a different version, the this is a UI bug.

Comment 7 Sarah Bennert 2021-05-19 10:08:10 UTC

I have verified all templates have been updated to use v1.

I will open a new bug for UI.

Comment 10 errata-xmlrpc 2021-07-27 14:28:41 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 Virtualization 4.8.0 Images), 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-2021:2920