migration_with_memory_devices: set start_vm = no to fix 'Domain is ready active'#6869
Conversation
…ready active'
migration_obj.setup_connection() calls setup_default(), which already starts
the VM when start_vm == "yes" (the default). The test then runs vm.start()
in TEST_STEP2 and fails with:
VMStartError: VM 'avocado-vt-vm1' failed to start:
error: Domain is already active (exit status: 1)
Set start_vm = no at the test-class scope so setup_default() leaves the VM
shut off, and the explicit vm.start() in TEST_STEP2 remains the single
start point.
Signed-off-by: Bolatbek Issakh <bissakh@redhat.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughA configuration setting is added to the migration with memory devices test scenario, setting Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Closing this PR due to current team constraints. This is part of a broader effort to triage all in-flight work across our upstream repos. If this work is still needed, please feel free to reopen and it will be picked up. Apologies for any inconvenience. |
migration_obj.setup_connection() calls setup_default(), which already starts the VM when start_vm == "yes" (the default). The test then runs vm.start() in TEST_STEP2 and fails with:
VMStartError: VM 'avocado-vt-vm1' failed to start:
error: Domain is already active (exit status: 1)
Set start_vm = no at the test-class scope so setup_default() leaves the VM shut off, and the explicit vm.start() in TEST_STEP2 remains the single start point.
Summary by CodeRabbit