MTV 2.12.0 release notes (#935)

* MTV 2.12.0 Attributes and release notes

Signed-off-by: A.Arnold <anarnold@redhat.com> and Richard Hoch
<rhoch@redhat.com>

* Update ref_known-issues-2-12.adoc

* Update ref_resolved-issues-2-12-0.adoc

* Update documentation/modules/ref_known-issues-2-12.adoc

* Update documentation/modules/ref_new-features-and-enhancements-2-12.adoc

* Update documentation/modules/ref_resolved-issues-2-12-0.adoc

* Update documentation/modules/ref_resolved-issues-2-12-0.adoc

* Update ref_resolved-issues-2-12-0.adoc

---------

Signed-off-by: A.Arnold <anarnold@redhat.com> and Richard Hoch
Co-authored-by: A.Arnold <anarnold@redhat.com>

Author: RichardHoch

documentation/doc-Release_notes/master.adoc

@@ -11,31 +11,19 @@ endif::[]
 [role="_abstract"]
 Review these release notes for {project-first} version {project-version}.
 
-include::modules/ref_rn-2-11.adoc[leveloffset=+1]
+include::modules/ref_rn-2-12.adoc[leveloffset=+1]
 
 // Technical changes by x-stream release
-include::modules/ref_technical-changes-2-11.adoc[leveloffset=+2]
+include::modules/ref_technical-changes-2-12.adoc[leveloffset=+2]
 
 // New features and enhancements by z-stream release
-include::modules/ref_new-features-and-enhancements-2-11.adoc[leveloffset=+2]
+include::modules/ref_new-features-and-enhancements-2-12.adoc[leveloffset=+2]
 
 // Resolved issues by y-stream release
 include::modules/ref_rn-resolved-issues.adoc[leveloffset=+2]
 
 // Resolved issues by z-stream release. Most recent release goes first in the list.
-include::modules/ref_resolved-issues-2-11-7.adoc[leveloffset=+3]
-
-include::modules/ref_resolved-issues-2-11-6.adoc[leveloffset=+3]
-
-include::modules/ref_resolved-issues-2-11-5.adoc[leveloffset=+3]
-
-include::modules/ref_resolved-issues-2-11-4.adoc[leveloffset=+3]
-
-include::modules/ref_resolved-issues-2-11-3.adoc[leveloffset=+3]
-
-include::modules/ref_resolved-issues-2-11-1.adoc[leveloffset=+3]
-
-include::modules/ref_resolved-issues-2-11-0.adoc[leveloffset=+3]
+include::modules/ref_resolved-issues-2-12-0.adoc[leveloffset=+3]
 
 // Known issues by x-stream release
-include::modules/ref_known-issues-2-11.adoc[leveloffset=+2]
+include::modules/ref_known-issues-2-12.adoc[leveloffset=+2]

documentation/modules/common-attributes.adoc

@@ -10,8 +10,8 @@
 :ocp-name: OpenShift
 :ocp-short: OpenShift
 // when updating the ocp-version, update the ocp-y-version
-:ocp-version: 4.21
-:ocp-y-version: 4.21, 4.20, 4.19
+:ocp-version: 4.22
+:ocp-y-version: 4.22, 4.21, 4.20
 :ocp-doc: link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single
 :operator: mtv-operator
 :operator-name-ui: Migration Toolkit for Virtualization Operator
@@ -58,3 +58,4 @@
 :subtitle-migrating: Migrating virtual machines from {vmw} vSphere, {rhv-full} or {osp} platforms, or other platforms to Red Hat {virt} by using the {project-full}
 :abstract-migrating: Run your migration plan by using either the {project-first} user interface in the Red Hat OpenShift web console or the command-line interface.
 
+

documentation/modules/ref_known-issues-2-11.adoc

@@ -0,0 +1,42 @@
+// Module included in the following assemblies:
+//
+// * documentation/doc-Release_notes/master.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="ref_known-issues-2-12_{context}"]
+= Known issues
+
+[role="_abstract"]
+{project-first} {project-version} has the following known issues.
+
+VM migrations with XFS v4 file systems fail during conversion::
+Migrating a virtual machine (VM) with an XFS v4 file system uses a Red Hat Enterprise Linux 9 `virt-v2v` image. This image does not support the `virt_v2v_memsize` and `virt_v2v_smp` parameters. As a consequence, the migration fails during the conversion phase if you set these parameters with `xfsCompatibility: true`.
++
+To work around this problem, apply the instructions in the Red Hat Knowledgebase solution link:https://access.redhat.com/solutions/7135435[MTV Migrations fails as virt-v2v appliance runs out of memory]. As a result, you avoid unexpected conversion failures.
++
+link:https://redhat.atlassian.net/browse/MTV-5595[MTV-5595]
+
+
+Deploying many User Defined Networks simultaneously causes node failures::
+Migrating from VMware to OpenShift Virtualization or deploying User Defined Networks (UDNs) can cause heavy resource contention. This contention occurs if you create more than 72 UDNs and their attached resources simultaneously. Open vSwitch (OVS) becomes starved for CPU time. Additionally, there is no way to determine if a UDN is fully created before attaching resources. As a consequence, high pod ready latency occurs, and nodes might enter a `NotReady` state.
++
+To work around this problem, limit simultaneous UDN creation to 72 or fewer. For larger deployments, create the UDNs upfront. Wait for Open Virtual Network Kubernetes (OVNK) utilization to settle before you deploy attached resources. As a result, you maintain stable pod ready latency and prevent node failures.
++
+link:https://redhat.atlassian.net/browse/MTV-5695[MTV-5695]
+
+Warm migrations of NBDE VMs fail during preflight inspection::
+A warm migration of a Network-Bound Disk Encryption (NBDE) virtual machine (VM) uses a DI pod. This pod cannot connect to the Tang server. As a consequence, the preflight inspection fails, and the migration plan fails.
++
+To work around this problem, disable the preflight inspection step by adding `runPreflightInspection: false` to the migration plan `spec`:
++
+[source,yaml]
+----
+spec:
+  ...
+  runPreflightInspection: false
+  ...
+----
++
+As a result, the migration proceeds without the preflight inspection. Potential issues in the plan might not be caught before execution.
++
+link:https://redhat.atlassian.net/browse/MTV-5750[MTV-5750]