Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

For information on the advisory (MTV 2.7.6 Images), and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2024:10996

Thanks sgratch@redhat.com , richard.hoch !

According to the comment, we can get the warning message now, and let me set this bug as verified, and use the MTV-1778 to track the left scenario

MTV-1778 - Mapping static ip network to nad network get warning message

The message appears as follows:

A PR was  merged upstream to main branch only (2.8.0):

https://github.com/kubev2v/forklift-console-plugin/pull/1405

richard.hoch 

All alert  messages, including this, are seen on all tabs, not specifically on the details tab.

Messages are located in the page's header section, shared by all tabs.

Choose a different mapping for your migration plan
Your migration plan preserves the static IPs of VMs and uses Pod Networking target network mapping. This combination isn't supported, because VM IPs aren't preserved in Pod Networking migrations.

• If your VMs use static IPs, click the Mappings tab, and choose a different target network mapping.
• if your VMs don't use static IPs, you can ignore this message.  ** 

sgratch@redhat.com chhu@redhat.com Please check – based on fdeutsch@redhat.com's comment this morning. The user is on Page details when they see this message, right? If not the first bullet should be "If your VMs user static IPs, open your plan's Plan details page, click Mappings. and choose a different target network mapping." 

A PR was  submitted upstream:

https://github.com/kubev2v/forklift-console-plugin/pull/1405

chhu@redhat.com

Currently the backend (and therefore the UI) are not aware of which source network is configured to use a static ip and which isn't.  We can't know if static IPs are actually used and for which VMs.

So the current UI verification is as follows:

If the plan is set to enable preserving of the static IPs (once configured to any of the plan VMs) and if one of the plan mappings is targeted to "pod networking" then warn the user that the preserving might fail for those VMs that use that mapping,

For improving the solution:

1. We can check in backend if there is a way to receive that info per source network - mnecas@redhat.com 

2. Improve the warning message to be more informative.

richard.hoch suggested the following msg, please review:

Tested on MTV 2.7.6-6 IIB build with CNV 4.17.1

Create a migration plan and map the static IP to nad network but not pod network, still get the message below, testing FAILED.

“The plan is set to preserve the static IPs of VMs mapped to a Pod network type. This is not supported and therefore VM IPs can be changed during the migration process. For fixing, update the destination network mappings to avoid using the 'Pod Networking' type.”

Steps:

1) Create a migration plan to migrate VM with two networks: Mgmt Network with static ip map to nad: mybridge, VM Network with dhcp map to Pod Networking

2) Check the "Plan Details" page, Get the message below,but the plan don't map static ip network to pod network

“The plan is set to preserve the static IPs of VMs mapped to a Pod network type. This is not supported and therefore VM IPs can be changed during the migration process. For fixing, update the destination network mappings to avoid using the 'Pod Networking' type.”

CPaaS Service Account mentioned this issue in merge request !1057 of mtv / MTV on branch MTV-2.7-rhel-9_upstream_670164b5ee41d6bbb571c7c62fff0441:

Updated US source to: 5e2969b Merge pull request #1400 from sgratch/bump-version-to-2-7-6