Merge pull request #93689 from sbeskin-redhat/CNV-5775_assemble_CNV_4_19_RN

CNV-5775: Assemble CNV-4.19 RN

Author: JoeAldinger

modules/virt-supported-cluster-version.adoc

@@ -1,7 +1,7 @@
 // Module included in the following assemblies:
 //
 // * virt/about_virt/about-virt.adoc
-// * virt/virt_release_notes/virt-4-9-release-notes.adoc
+// * virt/virt_release_notes/virt-4-19-release-notes.adoc
 
 [id="virt-supported-cluster-version_{context}"]
 = Supported cluster versions for {VirtProductName}

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

@@ -6,12 +6,12 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-[id="virt-doc-feedback"]
+[id="virt-doc-feedback_{context}"]
 == Providing documentation feedback
 
 To report an error or to improve our documentation, log in to your link:https://issues.redhat.com[Red Hat Jira account] and submit a link:https://issues.redhat.com/secure/CreateIssueDetails!init.jspa?pid=12323181&issuetype=1&components=12333768&priority=10200&summary=%5BDoc%5D&customfield_12316142[Jira issue].
 
-[id="virt-about-virt"]
+[id="virt-about-virt_{context}"]
 == About Red Hat {VirtProductName}
 
 With Red Hat {VirtProductName}, you can bring traditional virtual machines (VMs) into {product-title} and run them alongside containers. In {VirtProductName}, VMs are native Kubernetes objects that you can manage by using the {product-title} web console or the command line.
@@ -29,12 +29,12 @@ xref:../../virt/install/preparing-cluster-for-virt.adoc#preparing-cluster-for-vi
 include::modules/virt-supported-cluster-version.adoc[leveloffset=+2]
 
 
-[id="virt-guest-os"]
+[id="virt-guest-os_{context}"]
 === Supported guest operating systems
 To view the supported guest operating systems for {VirtProductName}, see link:https://access.redhat.com/articles/973163#ocpvirt[Certified Guest Operating Systems in Red Hat OpenStack Platform, Red Hat Virtualization, OpenShift Virtualization and Red Hat Enterprise Linux with KVM].
 
 //Ensure platform passes Windows Server Virtualization Validation Program. Otherwise, comment out the section below.
-[id="virt-svvp-certification"]
+[id="virt-svvp-certification_{context}"]
 === Microsoft Windows SVVP certification
 
 //CNV-47134 SVVP 4.18 Release Note: New
@@ -46,50 +46,64 @@ The SVVP certification applies to:
 * Red Hat Enterprise Linux CoreOS workers. In the Microsoft SVVP Catalog, they are named __Red Hat OpenShift Container Platform 4 on RHEL CoreOS 9__.
 * Intel and AMD CPUs.
 
-[id="virt-quick-starts"]
+[id="virt-quick-starts_{context}"]
 == Quick starts
 
 Quick start tours are available for several {VirtProductName} features. To view the tours, click the *Help* icon *?* in the menu bar on the header of the {product-title} web console and then select *Quick Starts*. You can filter the available tours by entering the keyword `virtualization` in the *Filter* field.
 
 
-[id="virt-4-19-new"]
+[id="virt-4-19-new_{context}"]
 == New and changed features
 
 This release adds new features and enhancements related to the following components and concepts:
 
-[id="virt-4-19-installation-update"]
+[id="virt-4-19-installation-update_{context}"]
 === Installation and update
+//[id="virt-4-19-installation-update"]
+//=== Installation and update
 
-[id="virt-4-19-infrastructure"]
+[id="virt-4-19-infrastructure_{context}"]
 === Infrastructure
+//[id="virt-4-19-infrastructure"]
+//=== Infrastructure
 
 //CNV-49593
 * You can now prevent the inadvertent deletion of a virtual machine (VM) by xref:../../virt/managing_vms/virt-enabling-disabling-vm-delete-protection.adoc#virt-enabling-disabling-vm-delete-protection[enabling delete protection for the VM]. You can also disable delete protection that has been set for a VM.
 +
 As a cluster administrator, you can prevent users from enabling VM delete protection xref:../../virt/managing_vms/virt-enabling-disabling-vm-delete-protection.adoc#virt-removing-vm-delete-protection_virt-enabling-disabling-vm-delete-protection[by removing the option at the cluster level].
 
+[id="virt-4-19-virtualization_{context}"]
+=== Virtualization
+
 //CNV-54747
 * You can now choose to expand virtual machines (VMs) using instance types and preferences. For more information, see link:https://access.redhat.com/solutions/7107803[Using InstancetypeReferencePolicy to expand VirtualMachines] in the Red Hat Customer Portal.
 
-[id="virt-4-19-virtualization"]
-=== Virtualization
 
 
-[id="virt-4-19-networking"]
+
+
+[id="virt-4-19-networking_{context}"]
 === Networking
 
 //CNV-30151 NNCP to enable LLDP
 * You can now xref:../../networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc#virt-example-enabling-lldp-policy_k8s-nmstate-updating-node-network-config[configure a `NodeNetworkConfigurationPolicy` manifest] to enable the Link Layer Discovery Protocol (LLDP) listener for all ethernet ports in your {product-title} cluster.
 
 
-[id="virt-4-19-storage"]
+
+[id="virt-4-19-storage_{context}"]
 === Storage
 
-[id="virt-4-19-web"]
+
+[id="virt-4-19-web_{context}"]
 === Web console
 
 
-[id="virt-4-19-monitoring"]
+
+
+
+
+
+[id="virt-4-19-monitoring_{context}"]
 === Monitoring
 
 //CNV-59720
@@ -98,32 +112,35 @@ As a cluster administrator, you can prevent users from enabling VM delete protec
 ** `HighCPUWorkload`
 ** `NodeNetworkInterfaceDown`
 
-[id="virt-4-19-documentation"]
+
+[id="virt-4-19-documentation_{context}"]
 === Documentation improvements
 
 
-[id="virt-4-19-notable-technical-changes"]
+[id="virt-4-19-notable-technical-changes_{context}"]
 === Notable technical changes
 
 
-[id="virt-4-19-deprecated-removed"]
+[id="virt-4-19-deprecated-removed_{context}"]
 == Deprecated and removed features
 //NOTE: Comment out deprecated and removed features (and their IDs) if not used in a release
 
-[id="virt-4-19-deprecated"]
+[id="virt-4-19-deprecated_{context}"]
 === Deprecated features
 // NOTE: When uncommenting deprecated features list, change the Removed features header level below to ===
 
 Deprecated features are included in the current release and supported. However, they will be removed in a future release and are not recommended for new deployments.
 
 * The `OperatorConditionsUnhealthy` alert is deprecated. You can safely xref:../../observability/monitoring/managing-alerts/managing-alerts-as-an-administrator.adoc#silencing-alerts-adm_managing-alerts-as-an-administrator[silence] it.
 
-[id="virt-4-19-removed"]
+
+[id="virt-4-19-removed_{context}"]
 === Removed features
 
 Removed features are no longer supported in {VirtProductName}.
 
 
+
 [id="virt-4-19-technology-preview_{context}"]
 == Technology Preview features
 
@@ -135,43 +152,76 @@ link:https://access.redhat.com/support/offerings/techpreview[Technology Preview
 * You can now xref:../../virt/vm_networking/virt-setting-interface-link-state.adoc#virt-setting-interface-link-state[manage the link state] of a primary or secondary virtual machine (VM) interface by using the {product-title} web console or the CLI.
 
 
-[id="virt-4-19-bug-fixes"]
+
+[id="virt-4-19-bug-fixes_{context}"]
 == Bug fixes
-//
-[id="virt-4-18-known-issues"]
+
+
+[id="virt-4-19-known-issues_{context}"]
 == Known issues
 
 [discrete]
-[id="virt-4-19-ki-monitoring"]
+[id="virt-4-19-ki-monitoring_{context}"]
 === Monitoring
 
 [discrete]
-[id="virt-4-19-ki-networking"]
+[id="virt-4-19-ki-networking_{context}"]
 === Networking
 //CNV-38746
 * When you update from {product-title} 4.12 to a newer minor version, VMs that use the `cnv-bridge` Container Network Interface (CNI) fail to live migrate. (link:https://access.redhat.com/solutions/7069807[])
 ** As a workaround, change the `spec.config.type` field in your `NetworkAttachmentDefinition` manifest from `cnv-bridge` to `bridge` before performing the update.
 
 
-[discrete]
-[id="virt-4-18-ki-nodes"]
-=== Nodes
-
 
 [discrete]
-[id="virt-4-18-ki-storage"]
-=== Storage
+[id="virt-4-19-ki-nodes_{context}"]
+==== Nodes
+//CNV-38543 - 4.16 Still an issue
+* Uninstalling {VirtProductName} does not remove the `feature.node.kubevirt.io` node labels created by {VirtProductName}. You must remove the labels manually. (link:https://issues.redhat.com/browse/CNV-38543[*CNV-38543*])
 
+[discrete]
+[id="virt-4-19-ki-storage_{context}"]
+==== Storage
+//CNV-23501: 4.16 - Keep per Dominik Holler
+* If you clone more than 100 VMs using the `csi-clone` cloning strategy, then the Ceph CSI might not purge the clones. Manually deleting the clones might also fail. (link:https://issues.redhat.com/browse/CNV-23501[*CNV-23501*])
+** As a workaround, you can restart the `ceph-mgr` daemon to purge the VM clones.
+
+// CNV-55104: 4.18 - Unresolved
+* If you perform storage class migration for a stopped VM, the VM might not be able to start because of a missing bootable device. To prevent this, do not attempt storage class migration if the VM is not running. (link:https://issues.redhat.com/browse/CNV-55104[*CNV-55104*])
++
+--
+:FeatureName: Storage class migration
+include::snippets/technology-preview.adoc[]
+--
 
 [discrete]
-[id="virt-4-18-ki-virtualization"]
+[id="virt-4-19-ki-virtualization_{context}"]
 === Virtualization
 
+//CNV-33835: 4.16 - Unresolved
+* {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}"]
+[id="virt-4-19-ki-webconsole_{context}"]
 === Web console
 
 [discrete]
-[id="virt-4-18-ki-ibm-z_{context}"]
+[id="virt-4-19-ki-ibm-z_{context}"]
 === {ibm-z-title} and {ibm-linuxone-title}
+
+--
+:FeatureName: Using {VirtProductName} with s390x architecture
+include::snippets/technology-preview.adoc[]
+--
+
+// ocpbugs-51113 - ballooning call traces
+* When you create a VM by using {op-system-base-full} container disk images for s390x architecture, call traces referencing `virtio_balloon` print to the VM console. (link:https://issues.redhat.com/browse/OCPBUGS-51113[OCPBUGS-51113])
+** As a workaround, add the following parameter to the VM YAML configuration: `spec.autoattachMemBalloon: false`.
+
+// cnv-56889 - boot mode
+* In the {product-title} web console, the *Boot mode* list for an s390x VM incorrectly includes *BIOS*, *UEFI*, and *UEFI (secure)* boot modes. If you select one of these modes for an s390x-based VM, the operation fails. This is because VMs based on s390x architecture can only use the *IPL* boot mode. (link:https://issues.redhat.com/browse/CNV-56889[CNV-56889])
+
+// cnv-56890 - threads
+* In the {product-title} web console, it is erroneously possible to define multiple CPU threads for a VM based on s390x architecture. If you define multiple CPU threads, the VM enters a `CrashLoopBackOff` state with the `qemu-kvm: S390 does not support more than 1 threads` error. (link:https://issues.redhat.com/browse/CNV-56890[CNV-56890])