When creating a new Datavolume, if there is already an existing PVC having the same name, then the DataVolume will be in an unrecoverable error state. If such a DataVolume is associated with a VM (or was created via the dataVolumeTemplates section in the VM yaml) then the VM will fail to start but the underlying DataVolume error will not be propagated to the VM. The above situation should be documented in the list of CNV-1.4 known issues.
Adam: what's the original BZ link so I can put it in the release notes? & Draft text (some minor wording changes, let me know what you think): "If you create a new DataVolume while a PVC already exists with the same name, the DataVolume enters an unrecoverable error state. If this DataVolume is associated with a virtual machine, or if it was created with the `dataVolumeTemplates` section of a VM configuration file, then the VM will fail to start. In these cases, the underlying DataVolume error will not be propagated to the VM."
Text looks great. Bug link here: https://bugzilla.redhat.com/show_bug.cgi?id=1669163
Thanks Adam! Moving to ON_QA. QE: here's the latest preview build containing this Known Issue: http://file.bos.redhat.com/pousley/022019/knownissues/cnv_release_notes/cnv_release_notes.html
Looks good. Thanks.
The requested content was published here: https://docs.openshift.com/container-platform/3.11/cnv_release_notes/cnv_release_notes.html#RN_known_issues