To improve the robustness of live migration testing, a ping test should be executed after each migration is completed. This will verify network connectivity and ensure that virtual machines remain accessible following a migration. Adding this step to the test suite will help identify and address potential connectivity issues earlier in the process, enhancing overall reliability.

Objective:
Integrate a post-migration ping test into the live migration testing workflow within the CI pipeline to validate successful network connectivity after VM migration. The current Tempest test is not doing that.

Acceptance Criteria:

1. Post-Migration Validation:
   • A ping test is automatically executed for the migrated VM to verify that it maintains network connectivity.
2. Integration into CI:
   • The ping test is incorporated into the automated live migration test suite within CI.
3. Failure Reporting:
   • Any failure of the ping test is logged and flagged within the CI results for immediate attention.
4. Compatibility:
   • The ping test should work seamlessly across all supported platforms and configurations.

Testing Requirements:

• Validate ping test functionality for different VM configurations and network setups.
• Ensure compatibility with current CI workflows and tools.
• Confirm accurate reporting of results in case of failures.

Priority: Medium

Target Release:
RHOSO & OSP17.1 NFV tempest plugin

Refer to customer case: https://bugzilla.redhat.com/show_bug.cgi?id=2322666