Bug 2094584 - VM with sysprep is failed to create
Summary: VM with sysprep is failed to create
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Matan Schatzman
QA Contact: Guohua Ouyang
Depends On: 2102302
TreeView+ depends on / blocked
Reported: 2022-06-07 23:34 UTC by Guohua Ouyang
Modified: 2022-08-01 11:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-01 11:34:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
vm yaml (4.78 KB, text/plain)
2022-06-07 23:34 UTC, Guohua Ouyang
no flags Details

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11775 0 None open [release 4.10] Bug 2094584: Cant create vm with sysprep 2022-06-30 11:32:31 UTC
Red Hat Product Errata RHSA-2022:5730 0 None None None 2022-08-01 11:36:13 UTC

Description Guohua Ouyang 2022-06-07 23:34:38 UTC
Created attachment 1887804 [details]
vm yaml

Description of problem:
VM with sysprep configured is failed to create at sometimes. It usually happens when it's the first time to use the template.

Error "Required value" for field "spec.dataVolumeTemplates.spec.sourceRef.kind".

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

How reproducible:

Steps to Reproduce:
1. use customize wizard to create a windows vm with sysprep

Actual results:

Expected results:

Additional info:

Comment 2 Guohua Ouyang 2022-07-27 05:11:19 UTC
verified on 4.10.0-0.nightly-2022-07-25-110002

Comment 5 errata-xmlrpc 2022-08-01 11:34:48 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.10.25 bug fix and security 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.


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