Skip to content

MTV 2.12.0 release notes#935

Open
RichardHoch wants to merge 9 commits into
kubev2v:mainfrom
RichardHoch:MTV-2-12-0-release-notes-rhoch
Open

MTV 2.12.0 release notes#935
RichardHoch wants to merge 9 commits into
kubev2v:mainfrom
RichardHoch:MTV-2-12-0-release-notes-rhoch

Conversation

@RichardHoch

@RichardHoch RichardHoch commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator

MTV 2.12.0 release notes

This PR continues the work started in #934 by @anarnold97.

Resolves https://redhat.atlassian.net/browse/MTV-4408

Changes

  • Updated release notes for version 2.12.0
  • Updated OpenShift version to 4.22
  • Added new features and enhancements for 2.12
  • Updated known issues and resolved issues

Co-authored-by: Andy Arnold anarnold97@users.noreply.github.com

Summary by CodeRabbit

  • New Features

    • Web console now documents support for Spanish, French, Japanese, Korean, and Simplified Chinese.
  • Documentation

    • Release notes and reference pages updated to target 2.12; older 2.11 reference modules removed.
    • Added 2.12 “Known issues” including NBDE/Tang preflight workaround for warm migrations.
    • Added 2.12 “Resolved issues” summaries covering migration, storage, and networking fixes.
    • Compatibility details updated for OpenShift 4.22.

@vercel

vercel Bot commented Jun 8, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
forklift-documentation Ready Ready Preview, Comment Jun 11, 2026 5:15pm

@coderabbitai

coderabbitai Bot commented Jun 8, 2026

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

This PR retargets release notes to 2.12: bumps OpenShift and project attributes, rewires the master release-notes assembly to include 2.12 modules, and adds new 2.12 reference modules for technical changes, new features, known issues, and resolved issues.

Changes

Release Notes Transition to 2.12

Layer / File(s) Summary
Version and Platform Attributes
documentation/modules/common-attributes.adoc
OpenShift platform attributes bumped to 4.22 and {project-version}/derived URLs updated from 2.11 → 2.12; :project-z-version: updated to 2.12.0.
Release Notes Assembly Wiring
documentation/doc-Release_notes/master.adoc
Master release notes now include 2.12-specific modules for technical changes, new features/enhancements, resolved issues, and known issues, removing 2.11 patch includes.
2.12 Reference Modules
documentation/modules/ref_rn-2-12.adoc, documentation/modules/ref_technical-changes-2-12.adoc, documentation/modules/ref_new-features-and-enhancements-2-12.adoc, documentation/modules/ref_known-issues-2-12.adoc, documentation/modules/ref_resolved-issues-2-12-0.adoc, documentation/modules/ref_rn-resolved-issues.adoc
Adds 2.12 release modules: updated release page anchor/title, technical-changes module, new-features documenting multi-language UI (Spanish, French, Japanese, Korean, Simplified Chinese), known-issues (multiple entries incl. NBDE/Tang preflight), and resolved-issues 2.12.0; also replaced a hardcoded resolved-issues version string with attributes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

Suggested reviewers

  • anarnold97
  • mnecas
  • solenoci

Poem

🐰 I hopped through docs from old to new,
Bumped versions, rewired includes too,
Languages bloom in the console light,
Known and resolved issues set right,
A tiny hop — release notes in view!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'MTV 2.12.0 release notes' directly corresponds to the main objective of the PR, which is to update release notes for version 2.12.0 across multiple documentation files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@documentation/modules/ref_known-issues-2-12.adoc`:
- Around line 12-15: This entry under the “Known issues” heading should be
rewritten to state the current limitation rather than implying a past failure:
update the paragraph titled "Virtual machine migrations with XFS v4 file
systems..." to explicitly say that migrations are rejected when
xfsCompatibility: true is combined with virt_v2v_memsize or virt_v2v_smp (e.g.,
"Migrations are now blocked when `xfsCompatibility: true` is used together with
`virt_v2v_memsize` or `virt_v2v_smp`; {project-short} will prevent these
incompatible configurations."), or move the item out of Known issues into the
resolved/behavior-change section so it reads as a deliberate validation change;
keep the {project-short} placeholder and the MTV-5595 link intact.

In `@documentation/modules/ref_resolved-issues-2-12-0.adoc`:
- Around line 12-21: The two identical entries titled "RDM disks converted to a
LUN now have the correct SCSI interface type" should be reconciled: inspect the
two issue references (link MTV-5610 and MTV-5620) and either (a) merge them into
a single entry that lists both links if they are the same fix, or (b) if they
are distinct, update each entry to state the unique scope or difference (e.g.,
component, affected release, or additional details) so both are justified;
remove the duplicated paragraph if they are truly the same. Locate the
duplicated block by searching for the exact heading text and the two link
identifiers (MTV-5610, MTV-5620) to apply the change.
- Line 13: The sentence describing RDM-to-LUN behavior in MigrationPlan contains
stray reference markers "[1, 2]"; edit the paragraph that mentions
"spec.rdmAsLun=true" and "MigrationPlan" to remove all occurrences of "[1, 2]"
so the text reads naturally (e.g., "…kept the virtio interface instead of
changing it to Small Computer System Interface (SCSI)." and "…have the required
SCSI interface type.") and ensure no leftover bracketed numbers remain.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4b76da7b-8d7a-4e20-8b59-72a5e95c429a

📥 Commits

Reviewing files that changed from the base of the PR and between a8ca70d and d73ddd1.

📒 Files selected for processing (17)
  • documentation/doc-Release_notes/master.adoc
  • documentation/modules/common-attributes.adoc
  • documentation/modules/ref_known-issues-2-11.adoc
  • documentation/modules/ref_known-issues-2-12.adoc
  • documentation/modules/ref_new-features-and-enhancements-2-11.adoc
  • documentation/modules/ref_new-features-and-enhancements-2-12.adoc
  • documentation/modules/ref_resolved-issues-2-11-0.adoc
  • documentation/modules/ref_resolved-issues-2-11-1.adoc
  • documentation/modules/ref_resolved-issues-2-11-3.adoc
  • documentation/modules/ref_resolved-issues-2-11-4.adoc
  • documentation/modules/ref_resolved-issues-2-11-5.adoc
  • documentation/modules/ref_resolved-issues-2-11-6.adoc
  • documentation/modules/ref_resolved-issues-2-11-7.adoc
  • documentation/modules/ref_resolved-issues-2-12-0.adoc
  • documentation/modules/ref_rn-2-12.adoc
  • documentation/modules/ref_technical-changes-2-11.adoc
  • documentation/modules/ref_technical-changes-2-12.adoc
💤 Files with no reviewable changes (10)
  • documentation/modules/ref_known-issues-2-11.adoc
  • documentation/modules/ref_resolved-issues-2-11-6.adoc
  • documentation/modules/ref_resolved-issues-2-11-3.adoc
  • documentation/modules/ref_resolved-issues-2-11-1.adoc
  • documentation/modules/ref_resolved-issues-2-11-5.adoc
  • documentation/modules/ref_technical-changes-2-11.adoc
  • documentation/modules/ref_resolved-issues-2-11-4.adoc
  • documentation/modules/ref_new-features-and-enhancements-2-11.adoc
  • documentation/modules/ref_resolved-issues-2-11-0.adoc
  • documentation/modules/ref_resolved-issues-2-11-7.adoc

Comment thread documentation/modules/ref_known-issues-2-12.adoc Outdated
Comment thread documentation/modules/ref_resolved-issues-2-12-0.adoc Outdated
Comment thread documentation/modules/ref_resolved-issues-2-12-0.adoc Outdated

@solenoci solenoci left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What is the process for documenting new features? Do we want to add all of them (or at least the most important)? Asking because we had quite a few and in the new features section, there is only one.

: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, 4.19

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

are these OCP versions supported for MTV 2.12? If so, the please remove 4.19

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

@Solenci -- changed as you suggested.

anarnold97 and others added 8 commits June 11, 2026 11:14
Signed-off-by: A.Arnold <anarnold@redhat.com>
Signed-off-by: A.Arnold <anarnold@redhat.com>
Signed-off-by: A.Arnold <anarnold@redhat.com> and Richard Hoch
<rhoch@redhat.com>
id: network-21
----
+
link:https://issues.redhat.com/browse/MTV-5511[MTV-5511]

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@solenoci & @RichardHoch - please can we add the NetApp integration as a New Feature - WDYT?

Suggested change
link:https://issues.redhat.com/browse/MTV-5511[MTV-5511]
link:https://issues.redhat.com/browse/MTV-5511[MTV-5511]
Zero-copy migrations via NetApp SHIFT integration::
Migration Toolkit for Virtualization (MTV) 2.12 provides integration with NetApp SHIFT for VMware environments. This feature enables "zero-copy" cold migrations to dramatically minimize migration downtime. As a result, you can achieve near-instantaneous data transfers.
+
The MTV user interface (UI) automates the process by generating specially labeled persistent volume claims (PVCs). These PVCs signal the NetApp Trident Container Storage Interface (CSI) to perform the disk transfer. When the transfer completes, MTV automatically executes the guest conversion, applies necessary boot permissions, and provisions the final virtual machine (VM) on OpenShift.
+
Review the following prerequisites and limitations for zero-copy migrations:
* You must install the NetApp SHIFT add-on on the OpenShift cluster alongside the Trident Operator.
* Source disks must reside on an ONTAP NFS datastore. Basic VMFS datastores are not supported.
* You must annotate the applicable storage classes within the MTV UI to identify them as NetApp SHIFT-capable.
* Source VMs cannot have active snapshots. You must flatten all disks before initiating the migration.
* Only cold migrations from VMware sources are supported. If a source VM is powered on when the migration starts, MTV automatically powers it off.

I was very kind and wrote a first draft for you! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants