Bug 1666805
| Summary: | Status field is required for DataVolumes while it should be optional. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Alexander Wels <awels> | ||||||
| Component: | Storage | Assignee: | Alexander Wels <awels> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Kedar Bidarkar <kbidarka> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 1.4 | CC: | alitke, cnv-qe-bugs, kbidarka, ncredi | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 1.4 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | v1.4.0-6 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2019-03-05 16:50:59 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: |
|
||||||||
Backport of fix to the cdi release-1.5 branch https://github.com/kubevirt/containerized-data-importer/pull/610 Vendor fix into kubevirt (where the validation was failing) https://github.com/kubevirt/kubevirt/pull/1952 Created attachment 1524501 [details]
status field is no longer required for DataVolumes
Tested/VERIFIED this with the below CNV build.
cnv_build_name: "CNV-1.4-RHEL-7-20190128.n.0"
|
Created attachment 1521076 [details] VM def with data volume that is missing a status field. Description of problem: Creating a DataVolume requires on to add: Status: {} Into the spec, which should be optional if there is no status. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a VM using a DataVolumeTemplate yaml without the status field as part of the data volume. See attached example. 2. Try to create the data volume with a kubectl create -f <file> 3. Validation will reject the yaml. Actual results: Creation is rejected Expected results: Creation is successful. Additional info: