From b95ad03d131cd1cbc46cc24dc371758db671bbdf Mon Sep 17 00:00:00 2001 From: "A.Arnold" Date: Wed, 6 Nov 2024 22:27:38 +0000 Subject: [PATCH 01/13] MTV-1649: Release Notes for MTV 2.7.4 Signed-off-by: A.Arnold --- .../modules/rn-27-resolved-issues.adoc | 23 ++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/documentation/modules/rn-27-resolved-issues.adoc b/documentation/modules/rn-27-resolved-issues.adoc index 77c05da9b16..615c980b802 100644 --- a/documentation/modules/rn-27-resolved-issues.adoc +++ b/documentation/modules/rn-27-resolved-issues.adoc @@ -7,6 +7,27 @@ {project-first} 2.7 has the following resolved issues: +[id="resolved-issues-2-7-4_{context}"] +== Resolved issues 2.7.4 + +.OVN secondary network is not functioning as expected with the Multus default network override + +In earlier releases of {project-short}, the secondary network of Open Virtual Network (OVN) did not function as expected with the Multus default network override. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1645[(MTV-1645)] + +.Secure Boot enabled VM migration resulted in a VM with Secure Boot disabled + +In earlier releases of {project-short}, when migrating a virtual machine (VM) with *Secure Boot* enabled, the VM had *Secure Boot* was disabled after being migrated. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1632[(MTV-1632)] + +.VMware warm migration is stuck with the error `No new block status data at offset 6806175744` + +In earlier releases of {project-short}, a warm VM migration from VMware could become stuck for an extended period, logging the same message repeatedly: `No new block status data at offset 6806175744`. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1629[(MTV-1629)] + + +.Error `Did not find CDI importer pod for DataVolume` is recorded in the `forklift-controller` logs during the `CopyDisks` phase + +In earlier releases of {project-short}, the `forklift-controller` incorrectly logged an error `Did not find CDI importer pod for DataVolume` during the `CopyDisks` phase. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1627[(MTV-1627)] + + [id="resolved-issues-2-7-3_{context}"] == Resolved issues 2.7.3 @@ -20,7 +41,7 @@ In earlier releases of {project-short}, having a large number of virtual machine .VM selection disappears when selecting multiple VMs in the Migration Plan -In earlier releases of {project-short}, *VM selection* checkbox disappeared after selecting multiple VMs in the Migration Plan. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1546[(MTV-1546)] +In earlier releases of {project-short}, the *VM selection* checkbox disappeared after selecting multiple VMs in the Migration Plan. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1546[(MTV-1546)] .`forklift-controller` crashing during OVA plan migration From 8ae499862a32867e740718650e1db004640f692a Mon Sep 17 00:00:00 2001 From: Andy Arnold Date: Wed, 6 Nov 2024 22:30:19 +0000 Subject: [PATCH 02/13] Update documentation/modules/rn-27-resolved-issues.adoc Signed-off-by: A.Arnold --- documentation/modules/rn-27-resolved-issues.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/modules/rn-27-resolved-issues.adoc b/documentation/modules/rn-27-resolved-issues.adoc index 615c980b802..413a2521654 100644 --- a/documentation/modules/rn-27-resolved-issues.adoc +++ b/documentation/modules/rn-27-resolved-issues.adoc @@ -14,7 +14,7 @@ In earlier releases of {project-short}, the secondary network of Open Virtual Network (OVN) did not function as expected with the Multus default network override. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1645[(MTV-1645)] -.Secure Boot enabled VM migration resulted in a VM with Secure Boot disabled +.Migration of a VM with Secure Boot enabled VM migration results in a VM with Secure Boot disabled In earlier releases of {project-short}, when migrating a virtual machine (VM) with *Secure Boot* enabled, the VM had *Secure Boot* was disabled after being migrated. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1632[(MTV-1632)] From 443224f1a73d58133e7b5340f1cd8bdb4847ba7c Mon Sep 17 00:00:00 2001 From: Andy Arnold Date: Wed, 13 Nov 2024 22:57:52 +0000 Subject: [PATCH 03/13] Update documentation/modules/rn-27-resolved-issues.adoc Signed-off-by: A.Arnold --- documentation/modules/rn-27-resolved-issues.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/documentation/modules/rn-27-resolved-issues.adoc b/documentation/modules/rn-27-resolved-issues.adoc index 413a2521654..f5d2bb65170 100644 --- a/documentation/modules/rn-27-resolved-issues.adoc +++ b/documentation/modules/rn-27-resolved-issues.adoc @@ -9,6 +9,9 @@ [id="resolved-issues-2-7-4_{context}"] == Resolved issues 2.7.4 +.XFS filesystem corruption after warm migration of VM from VMware + +In earlier releases of {project-short}, in some cases, the destination VMware virtual machine (VM) was observed to have XFS filesystem corruption after being migrated to {virt} using {project-short}. This issue has been resolved in {project-short} 2.7.4. link:https://issues.redhat.com/browse/MTV-1656[(MTV-1656)] .OVN secondary network is not functioning as expected with the Multus default network override From df6a7793c37dd6d0e4b86f22338978fb54e104ea Mon Sep 17 00:00:00 2001 From: Andy Arnold Date: Wed, 13 Nov 2024 22:58:14 +0000 Subject: [PATCH 04/13] Update documentation/modules/rn-27-resolved-issues.adoc Signed-off-by: A.Arnold --- documentation/modules/rn-27-resolved-issues.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/modules/rn-27-resolved-issues.adoc b/documentation/modules/rn-27-resolved-issues.adoc index f5d2bb65170..47a3c432cb2 100644 --- a/documentation/modules/rn-27-resolved-issues.adoc +++ b/documentation/modules/rn-27-resolved-issues.adoc @@ -15,7 +15,7 @@ In earlier releases of {project-short}, in some cases, the destination VMware vi .OVN secondary network is not functioning as expected with the Multus default network override -In earlier releases of {project-short}, the secondary network of Open Virtual Network (OVN) did not function as expected with the Multus default network override. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1645[(MTV-1645)] +In earlier releases of {project-short}, the secondary network of Open Virtual Network (OVN) did not function as expected with the Multus default network override. This issue has been resolved in {project-short} 2.7.4. link:https://issues.redhat.com/browse/MTV-1645[(MTV-1645)] .Migration of a VM with Secure Boot enabled VM migration results in a VM with Secure Boot disabled From 118edd37fe2d749897706d97eeb2dd6a6b6f4d96 Mon Sep 17 00:00:00 2001 From: Andy Arnold Date: Wed, 13 Nov 2024 22:58:42 +0000 Subject: [PATCH 05/13] Update documentation/modules/rn-27-resolved-issues.adoc Signed-off-by: A.Arnold --- documentation/modules/rn-27-resolved-issues.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/modules/rn-27-resolved-issues.adoc b/documentation/modules/rn-27-resolved-issues.adoc index 47a3c432cb2..a7ba0460e9d 100644 --- a/documentation/modules/rn-27-resolved-issues.adoc +++ b/documentation/modules/rn-27-resolved-issues.adoc @@ -23,7 +23,7 @@ In earlier releases of {project-short}, when migrating a virtual machine (VM) wi .VMware warm migration is stuck with the error `No new block status data at offset 6806175744` -In earlier releases of {project-short}, a warm VM migration from VMware could become stuck for an extended period, logging the same message repeatedly: `No new block status data at offset 6806175744`. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1629[(MTV-1629)] +In earlier releases of {project-short}, a warm VM migration from VMware could become stuck for an extended period, logging the same message repeatedly: `No new block status data at offset 6806175744`. This issue has been resolved in {project-short} 2.7.4. link:https://issues.redhat.com/browse/MTV-1629[(MTV-1629)] .Error `Did not find CDI importer pod for DataVolume` is recorded in the `forklift-controller` logs during the `CopyDisks` phase From abdb2bb1be08b6b8fb43fadcf08ecb9f023580e7 Mon Sep 17 00:00:00 2001 From: Andy Arnold Date: Wed, 13 Nov 2024 22:59:13 +0000 Subject: [PATCH 06/13] Update documentation/modules/rn-27-resolved-issues.adoc Signed-off-by: A.Arnold --- documentation/modules/rn-27-resolved-issues.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/modules/rn-27-resolved-issues.adoc b/documentation/modules/rn-27-resolved-issues.adoc index a7ba0460e9d..f024f70e101 100644 --- a/documentation/modules/rn-27-resolved-issues.adoc +++ b/documentation/modules/rn-27-resolved-issues.adoc @@ -28,7 +28,7 @@ In earlier releases of {project-short}, a warm VM migration from VMware could be .Error `Did not find CDI importer pod for DataVolume` is recorded in the `forklift-controller` logs during the `CopyDisks` phase -In earlier releases of {project-short}, the `forklift-controller` incorrectly logged an error `Did not find CDI importer pod for DataVolume` during the `CopyDisks` phase. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1627[(MTV-1627)] +In earlier releases of {project-short}, the `forklift-controller` incorrectly logged an error `Did not find CDI importer pod for DataVolume` during the `CopyDisks` phase. This issue has been resolved in {project-short} 2.7.4. link:https://issues.redhat.com/browse/MTV-1627[(MTV-1627)] [id="resolved-issues-2-7-3_{context}"] From 66ac5699eda897823ac52825a5898a4009907aee Mon Sep 17 00:00:00 2001 From: "A.Arnold" Date: Wed, 13 Nov 2024 23:02:18 +0000 Subject: [PATCH 07/13] update Signed-off-by: A.Arnold --- documentation/modules/known-issues-2-7.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/documentation/modules/known-issues-2-7.adoc b/documentation/modules/known-issues-2-7.adoc index c6433384f0f..f31de21b65a 100644 --- a/documentation/modules/known-issues-2-7.adoc +++ b/documentation/modules/known-issues-2-7.adoc @@ -16,6 +16,10 @@ include::snip_secure_boot_issue.adoc[] include::snip_measured_boot_windows_vm.adoc[] +.Migration of a VM with Secure Boot enabled VM migration results in a VM with Secure Boot disabled + +When migrating a virtual machine (VM) with *Secure Boot* enabled, the VM has *Secure Boot* as `disabled` after being migrated. link:https://issues.redhat.com/browse/MTV-1632[(MTV-1632)] + .Network and Storage maps in the UI are not correct when created from the command line When creating *Network* and *Storage* maps from the UI, the correct names are not shown in the UI. link:https://issues.redhat.com/browse/MTV-1421[(MTV-1421)] From da413674ee0cb47bd9a8a631c8cda851e97ee886 Mon Sep 17 00:00:00 2001 From: "A.Arnold" Date: Mon, 18 Nov 2024 13:49:13 +0000 Subject: [PATCH 08/13] Fixing errors in VMware providers Signed-off-by: A.Arnold --- documentation/modules/adding-source-provider.adoc | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/documentation/modules/adding-source-provider.adoc b/documentation/modules/adding-source-provider.adoc index 407265ae7e9..6543e53f52c 100644 --- a/documentation/modules/adding-source-provider.adoc +++ b/documentation/modules/adding-source-provider.adoc @@ -39,7 +39,7 @@ You can add an {osp} source provider by using the {ocp} web console. [IMPORTANT] ==== -When you migrate an image-based VM from an {osp} provider, a snapshot is created for the image that is attached to the source VM and the data from the snapshot is copied over to the target VM. This means that the target VM will have the same state as that of the source VM at the time the snapshot was created. +When you migrate an image-based VM from an {osp} provider, a snapshot is created for the image that is attached to the source VM and the data from the snapshot is copied over to the target VM. This means that the target VM will have the same state as that of the source VM at the time the snapadding-source-providershot was created. ==== endif::[] @@ -82,6 +82,7 @@ ifdef::vmware[] . Click *vSphere*. . Specify the following fields: ++ *Provider Details* * *Provider resource name*: Name of the source provider. @@ -89,12 +90,15 @@ ifdef::vmware[] * *URL*: URL of the SDK endpoint of the vCenter on which the source VM is mounted. Ensure that the URL includes the `sdk` path, usually `/sdk`. For example, `https://vCenter-host-example.com/sdk`. If a certificate for FQDN is specified, the value of this field needs to match the FQDN in the certificate. * *VDDK init image*: `VDDKInitImage` path. It is strongly recommended to create a VDDK init image to accelerate migrations. For more information, see xref:../master.adoc#creating-vddk-image_mtv[Creating a VDDK image]. -*Provider details* ++ +*Provider credentials* * *Username*: vCenter user or ESXi user. For example, `user@vsphere.local`. * *Password*: vCenter user password or ESXi user password. -+ + +[start=5] include::snip-certificate-options.adoc[] + endif::[] ifdef::rhv[] . Click *Red Hat Virtualization* From 418d6168f7a1b393290eab1ff1abb694b9a2c7a7 Mon Sep 17 00:00:00 2001 From: Andy Arnold Date: Mon, 18 Nov 2024 14:40:44 +0000 Subject: [PATCH 09/13] Update documentation/modules/known-issues-2-7.adoc Signed-off-by: A.Arnold --- documentation/modules/known-issues-2-7.adoc | 4 ---- 1 file changed, 4 deletions(-) diff --git a/documentation/modules/known-issues-2-7.adoc b/documentation/modules/known-issues-2-7.adoc index f31de21b65a..c6433384f0f 100644 --- a/documentation/modules/known-issues-2-7.adoc +++ b/documentation/modules/known-issues-2-7.adoc @@ -16,10 +16,6 @@ include::snip_secure_boot_issue.adoc[] include::snip_measured_boot_windows_vm.adoc[] -.Migration of a VM with Secure Boot enabled VM migration results in a VM with Secure Boot disabled - -When migrating a virtual machine (VM) with *Secure Boot* enabled, the VM has *Secure Boot* as `disabled` after being migrated. link:https://issues.redhat.com/browse/MTV-1632[(MTV-1632)] - .Network and Storage maps in the UI are not correct when created from the command line When creating *Network* and *Storage* maps from the UI, the correct names are not shown in the UI. link:https://issues.redhat.com/browse/MTV-1421[(MTV-1421)] From f46ab6a56bbf2350730018e2908402bb9f29fd7a Mon Sep 17 00:00:00 2001 From: Andy Arnold Date: Mon, 18 Nov 2024 14:41:24 +0000 Subject: [PATCH 10/13] Update documentation/modules/rn-27-resolved-issues.adoc Signed-off-by: A.Arnold --- .../modules/rn-27-resolved-issues.adoc | 24 ------------------- 1 file changed, 24 deletions(-) diff --git a/documentation/modules/rn-27-resolved-issues.adoc b/documentation/modules/rn-27-resolved-issues.adoc index f024f70e101..2bcb24fb0bc 100644 --- a/documentation/modules/rn-27-resolved-issues.adoc +++ b/documentation/modules/rn-27-resolved-issues.adoc @@ -7,30 +7,6 @@ {project-first} 2.7 has the following resolved issues: -[id="resolved-issues-2-7-4_{context}"] -== Resolved issues 2.7.4 -.XFS filesystem corruption after warm migration of VM from VMware - -In earlier releases of {project-short}, in some cases, the destination VMware virtual machine (VM) was observed to have XFS filesystem corruption after being migrated to {virt} using {project-short}. This issue has been resolved in {project-short} 2.7.4. link:https://issues.redhat.com/browse/MTV-1656[(MTV-1656)] - -.OVN secondary network is not functioning as expected with the Multus default network override - -In earlier releases of {project-short}, the secondary network of Open Virtual Network (OVN) did not function as expected with the Multus default network override. This issue has been resolved in {project-short} 2.7.4. link:https://issues.redhat.com/browse/MTV-1645[(MTV-1645)] - -.Migration of a VM with Secure Boot enabled VM migration results in a VM with Secure Boot disabled - -In earlier releases of {project-short}, when migrating a virtual machine (VM) with *Secure Boot* enabled, the VM had *Secure Boot* was disabled after being migrated. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1632[(MTV-1632)] - -.VMware warm migration is stuck with the error `No new block status data at offset 6806175744` - -In earlier releases of {project-short}, a warm VM migration from VMware could become stuck for an extended period, logging the same message repeatedly: `No new block status data at offset 6806175744`. This issue has been resolved in {project-short} 2.7.4. link:https://issues.redhat.com/browse/MTV-1629[(MTV-1629)] - - -.Error `Did not find CDI importer pod for DataVolume` is recorded in the `forklift-controller` logs during the `CopyDisks` phase - -In earlier releases of {project-short}, the `forklift-controller` incorrectly logged an error `Did not find CDI importer pod for DataVolume` during the `CopyDisks` phase. This issue has been resolved in {project-short} 2.7.4. link:https://issues.redhat.com/browse/MTV-1627[(MTV-1627)] - - [id="resolved-issues-2-7-3_{context}"] == Resolved issues 2.7.3 From beaf412d02da114a34fab1dfbfaeba73a7d25b19 Mon Sep 17 00:00:00 2001 From: Andy Arnold Date: Mon, 18 Nov 2024 14:42:30 +0000 Subject: [PATCH 11/13] Update documentation/modules/rn-27-resolved-issues.adoc Signed-off-by: A.Arnold --- documentation/modules/rn-27-resolved-issues.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/modules/rn-27-resolved-issues.adoc b/documentation/modules/rn-27-resolved-issues.adoc index 2bcb24fb0bc..77c05da9b16 100644 --- a/documentation/modules/rn-27-resolved-issues.adoc +++ b/documentation/modules/rn-27-resolved-issues.adoc @@ -20,7 +20,7 @@ In earlier releases of {project-short}, having a large number of virtual machine .VM selection disappears when selecting multiple VMs in the Migration Plan -In earlier releases of {project-short}, the *VM selection* checkbox disappeared after selecting multiple VMs in the Migration Plan. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1546[(MTV-1546)] +In earlier releases of {project-short}, *VM selection* checkbox disappeared after selecting multiple VMs in the Migration Plan. This issue has been resolved in {project-short} 2.7.3. link:https://issues.redhat.com/browse/MTV-1546[(MTV-1546)] .`forklift-controller` crashing during OVA plan migration From afdb07444f10d2b9d1b89fbf27ade69139cd14dd Mon Sep 17 00:00:00 2001 From: Andy Arnold Date: Mon, 18 Nov 2024 14:43:25 +0000 Subject: [PATCH 12/13] Update documentation/modules/adding-source-provider.adoc Signed-off-by: A.Arnold --- documentation/modules/adding-source-provider.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/modules/adding-source-provider.adoc b/documentation/modules/adding-source-provider.adoc index 6543e53f52c..152c5389e33 100644 --- a/documentation/modules/adding-source-provider.adoc +++ b/documentation/modules/adding-source-provider.adoc @@ -39,7 +39,7 @@ You can add an {osp} source provider by using the {ocp} web console. [IMPORTANT] ==== -When you migrate an image-based VM from an {osp} provider, a snapshot is created for the image that is attached to the source VM and the data from the snapshot is copied over to the target VM. This means that the target VM will have the same state as that of the source VM at the time the snapadding-source-providershot was created. +When you migrate an image-based VM from an {osp} provider, a snapshot is created for the image that is attached to the source VM and the data from the snapshot is copied over to the target VM. This means that the target VM will have the same state as that of the source VM at the time the snapshot was created. ==== endif::[] From 906352f2ac0bded0ad1ddc5d34f8bf3b1fa8d0be Mon Sep 17 00:00:00 2001 From: Andy Arnold Date: Mon, 18 Nov 2024 14:52:53 +0000 Subject: [PATCH 13/13] Update documentation/modules/adding-source-provider.adoc Signed-off-by: A.Arnold --- documentation/modules/adding-source-provider.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/modules/adding-source-provider.adoc b/documentation/modules/adding-source-provider.adoc index 152c5389e33..33a32266d47 100644 --- a/documentation/modules/adding-source-provider.adoc +++ b/documentation/modules/adding-source-provider.adoc @@ -83,7 +83,7 @@ ifdef::vmware[] . Specify the following fields: + -*Provider Details* +*Provider details* * *Provider resource name*: Name of the source provider. * *Endpoint type*: Select the vSphere provider endpoint type. Options: *vCenter* or *ESXi*. You can migrate virtual machines from vCenter, an ESX/ESXi server that is not managed by vCenter, or from an ESX/ESXi server that is managed by vCenter but does not go through vCenter.