Merge pull request #96179 from danielclowers/CNV-64690_418

CNV#64690: RN 4.18 remove fixed known issue

Author: sjhala-ccs

virt/release_notes/virt-4-18-release-notes.adoc

@@ -234,11 +234,9 @@ include::snippets/technology-preview.adoc[]
 * {VirtProductName} links a service account token in use by a pod to that specific pod. {VirtProductName} implements a service account volume by creating a disk image that contains a token. If you migrate a VM, then the service account volume becomes invalid. (link:https://issues.redhat.com/browse/CNV-33835[*CNV-33835*])
 ** As a workaround, use user accounts rather than service accounts because user account tokens are not bound to a specific pod.
 
-[discrete]
-[id="virt-4-16-ki-webconsole_{context}"]
-==== Web console
-//CNV-38594: 4.16 - Still an issue per Guohua
-* When you create a persistent volume claim (PVC) by selecting *With Data upload form* from the *Create PersistentVolumeClaim* list in the web console, uploading data to the PVC by using the *Upload Data* field fails. (link:https://issues.redhat.com/browse/CNV-37607[*CNV-37607*])
+//[discrete]
+//[id="virt-4-16-ki-webconsole_{context}"]
+//==== Web console
 
 [discrete]
 [id="virt-4-18-ki-ibm-z_{context}"]