Bug 2145126 - Cant start VM with "clock" virtualMachinePreference
Summary: Cant start VM with "clock" virtualMachinePreference
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Infrastructure
Version: 4.12.0
Hardware: All
OS: All
high
high
Target Milestone: ---
: 4.13.0
Assignee: Lee Yarwood
QA Contact: Ying Cui
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-23 10:00 UTC by Roni Kishner
Modified: 2023-05-18 02:57 UTC (History)
3 users (show)

Fixed In Version: v4.13.0.rhel9-1016
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-18 02:55:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
VirtualMachinePreference (456 bytes, text/plain)
2022-11-23 10:00 UTC, Roni Kishner
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt issues 8844 0 None open The VirtualMachineInstance "foo" is invalid: spec.domain.clock.timer: Invalid value: "null": spec.domain.clock.timer in ... 2022-11-23 18:05:57 UTC
Github kubevirt kubevirt pull 8845 0 None open api: Ensure Timer is omitted when empty from Clock 2022-11-23 18:05:57 UTC
Red Hat Issue Tracker CNV-22808 0 None None None 2022-11-23 10:30:51 UTC
Red Hat Product Errata RHSA-2023:3205 0 None None None 2023-05-18 02:57:02 UTC

Description Roni Kishner 2022-11-23 10:00:31 UTC
Created attachment 1926620 [details]
VirtualMachinePreference

Description of problem:
When trying to start a VM with VirtualMachinePreference with "clock" parameters the VM won't start giving an Error of:

Failure while starting VMI: VirtualMachineInstance.kubevirt.io "rhel-vm"
is invalid: spec.domain.clock.timer: Invalid value: "null": spec.domain.clock.timer in body must be of type object: "null"

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

How reproducible:
100%

Steps to Reproduce:
1. Create a VirtualMachinePreference with "clock" value 
2. Create a VM with reference to the preference
3. Start the VM

Actual results:
VM wont start

Expected results:
VM will start

Additional info:
- Adding to the VM an empty dict under such as - spec.template.spec.domain.clock = {}, will let the VM start

- Attached yaml files of run

Comment 4 Roni Kishner 2023-03-06 10:30:15 UTC
Verified on CNV-v4.13.0.rhel9-1631

Comment 7 errata-xmlrpc 2023-05-18 02:55: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.13.0 Images 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.

https://access.redhat.com/errata/RHSA-2023:3205


Note You need to log in before you can comment on or make changes to this bug.