-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
CLOSED
-
Undefined
-
CNV Virtualization Sprint 200
-
High
-
None
Description of problem: After a MC is implemented or an upgrade is performed some VM do not start migration although the VM migration signal is received. A sample VM is "azksc01" at the must-gather logs.
The MCP gets degraded. Stopping and starting the VM resumes the MC implementation.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Upgrade or create an Machine-config
2. vm do not start migration.
3. Mcp gets degraded
Actual results: Vm migration doesnt start.
Expected results: Vm migrtion do not start.
Additional info:
- external trackers
- links to