Bug 2145126
| Summary: | Cant start VM with "clock" virtualMachinePreference | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Roni Kishner <rkishner> | ||||
| Component: | Infrastructure | Assignee: | Lee Yarwood <lyarwood> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Ying Cui <ycui> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.12.0 | CC: | dholler, gkapoor, lyarwood | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.13.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | v4.13.0.rhel9-1016 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-05-18 02:55: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: | |||||||
| Attachments: |
|
||||||
Verified on CNV-v4.13.0.rhel9-1631 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 |
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