Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MTV-1785: Release notes for MTV 2.7.7 #604

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

MTV-1785: Release notes for MTV 2.7.7 #604

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
763b365
MTV-1785: Release notes for MTV 2.7.7
anarnold97 Dec 12, 2024
2e4f1cf
update
anarnold97 Dec 12, 2024
f8847e2
Update documentation/modules/rn-27-resolved-issues.adoc
anarnold97 Dec 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion documentation/modules/known-issues-2-7.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ 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)]
When migrating a virtual machine (VM) with *Secure Boot* enabled, the VM has *Secure Boot* as `disabled` after being migrated. This issue has been resolved in {project-short} 2.7.7. link:https://issues.redhat.com/browse/MTV-1632[(MTV-1632)]

.OVN secondary network is not functioning as expected with the Multus default network override

Expand Down
24 changes: 24 additions & 0 deletions documentation/modules/rn-27-resolved-issues.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,30 @@

{project-first} 2.7 has the following resolved issues:

[id="resolved-issues-2-7-7_{context}"]
== Resolved issues 2.7.7

.{project-short} Controller waiting for snapshot creation

In earlier releases of {project-short}, when performing a warm migration using 200 VMs, the {project-short} Controller could pause the migration during snapshot creation. This issue has been resolved in {project-short} 2.7.7. link:https://issues.redhat.com/browse/MTV-1775[(MTV-1775)]

.Extended delay in time taken for VMs to start migration

In earlier releases of {project-short}, in some situations there was an extended delay before all VMs started to migrate. This issue has been resolved in {project-short} 2.7.7. link:https://issues.redhat.com/browse/MTV-1774[(MTV-1774)]

.Warm migration plan with multi-VMs from ESXi host provider fails in cutover phase

In earlier releases of {project-short}, the migration plan with multi-VMs from an ESXi host provider failed in the cutover phase. This issue has been resolved in {project-short} 2.7.7. link:https://issues.redhat.com/browse/MTV-1753[(MTV-1753)]

.SecureBoot enabled VM in migrated with SecureBoot disabled

In earlier releases of {project-short}, when migrating a virtual machine (VM) with Secure Boot *enabled*, the VM had Secure Boot *disabled* after being migrated. This issue has been resolved in {project-short} 2.7.7. link:https://issues.redhat.com/browse/MTV-1632[(MTV-1632)]

.VDDK validator containers require requests and limits
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VDDK validator failed to launch in environments with quota set

anarnold97 marked this conversation as resolved.
Show resolved Hide resolved

In earlier releases of {project-short}, after creating a migration plan from a VMware provider, the VDDK validation failed due to a `LimitRange` not being provided to add requests and limits to any container that do not define them. This issue has been resolved in {project-short} 2.7.7, with {project-short} setting limits by default to make the migration plan work out of the box. link:https://issues.redhat.com/browse/MTV-1493[(MTV-1493)]


[id="resolved-issues-2-7-6_{context}"]
== Resolved issues 2.7.6

Expand Down