Custom source and destination for migration and resize tests

Bug #2028540 reported by Martin Kopec
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
Wishlist
Jakub Skunda

Bug Description

As discussed in Vancouver - https://etherpad.opendev.org/p/vancouver-june2023-qa

Let's add an option to specify the source and the destination host for live-migration, cold-migration and resize tests.

Currently, the following 4 scenario tests don't specify the source and destination host.

    * test_server_connectivity_cold_migration

    * test_server_connectivity_cold_migration_revert

    * test_server_connectivity_live_migration

    * test_server_connectivity_resize

https://opendev.org/openstack/tempest/src/branch/master/tempest/scenario/test_network_advanced_server_ops.py

Martin Kopec (mkopec)
Changed in tempest:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Ghanshyam Mann (ghanshyammann) wrote :

I am ok with the idea and it will give ability to test the specific nodes for migration.

Martin Kopec (mkopec)
Changed in tempest:
assignee: nobody → Jakub Skunda (jskunda)
Changed in tempest:
status: Confirmed → In Progress
Revision history for this message
Martin Kopec (mkopec) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.opendev.org/c/openstack/tempest/+/891123
Committed: https://opendev.org/openstack/tempest/commit/5a7ed97b7f36c7d966946dabf2383738e7dbad79
Submitter: "Zuul (22348)"
Branch: master

commit 5a7ed97b7f36c7d966946dabf2383738e7dbad79
Author: jskunda <email address hidden>
Date: Thu Aug 10 22:04:19 2023 +0200

    Add option to specify source and destination host

    This patch adds new class of tests, in which it is possible to
    specify source and destination host to migration.

    Closes-Bug: #2028540
    Change-Id: If07355464d1567c18bedbf07c479e61874ec2031

Changed in tempest:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tempest 38.0.0

This issue was fixed in the openstack/tempest 38.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.