Bug 1667438
| Summary: | KubeVirt vendors version of CDI with mandatory status field in DataVolumes | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | sgott | ||||
| Component: | Virtualization | Assignee: | sgott | ||||
| Status: | CLOSED ERRATA | QA Contact: | Kedar Bidarkar <kbidarka> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 1.4 | CC: | cnv-qe-bugs, fsimonce, kbidarka, ncredi, sgordon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 1.4 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | kubevirt-0.13.2-1.ge1ce9da.6d86849 virt-api-container-v1.4.0-15 virt-controller-container-v1.4.0-15 virt-handler-container-v1.4.0-15 virt-launcher-container-v1.4.0-15 virt-operator-container-v1.4.0-7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-02-26 13:24:18 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: | |||||||
| Bug Depends On: | 1663238 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
sgott
2019-01-18 13:49:56 UTC
To reproduce this for verification, follow the steps in this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1666805 Created attachment 1524503 [details]
status field is no longer required for DataVolumes
Status field is no longer required for Data-volumes.
Tested/VERIFIED this with the below CNV build.
cnv_build_name: "CNV-1.4-RHEL-7-20190128.n.0"
Also tested this with the webui and submission of VM with data-volumes was successful.
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, 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/RHEA-2019:0417 |