DescriptionFelix Dewaleyne
2020-01-07 13:22:10 UTC
Description of problem:
When live migrating a set of vms with vmotion
Version-Release number of selected component (if applicable):
5.10.13.1
How reproducible:
all the time
Steps to Reproduce:
1. create and apply a control policy that has for purpose to copy the tag of the host to the vm / update the tag of the vm . This should trigger on vm migrate at least
2. set about 200 vms to migrate using vm motion
Actual results:
the migration did not trigger the control policy
Expected results:
the migration triggers the control policy
Additional info:
we do not see any vm migration event in the control.log or any call to a control policy after the migration
this may not be relevant but the policy is set to be triggered on
Service Provision Complete
VM Settings Change
VM Create Complete
VM Clone Complete
VM Guest Reboot
VM Migration (vMotion)
Power On
Power Off
VM Reset
VM Resume
each time the event "DrsVmMigratedEvent" the migration seems to not be detected, while in one case it was a "VmMigratedEvent" that was used and that did trigger the control policy.
New commit detected on ManageIQ/manageiq-content/master:
https://github.com/ManageIQ/manageiq-content/commit/fbca9889184d6d334fcea3138dfa32ad629ba7c8
commit fbca9889184d6d334fcea3138dfa32ad629ba7c8
Author: Adam Grare <agrare>
AuthorDate: Tue Jan 7 10:12:34 2020 -0500
Commit: Adam Grare <agrare>
CommitDate: Tue Jan 7 10:12:34 2020 -0500
Add an automate event for DrsMigrateVM_Task
This adds an automate event instance for the DrsMigrateVM_Task event
which is a more specific subclass of the MigrateVM_Task class.
https://bugzilla.redhat.com/show_bug.cgi?id=1788540
content/automate/ManageIQ/System/Event/EmsEvent/VC.class/drsmigratevm_task.yaml | 12 +
1 file changed, 12 insertions(+)
Description of problem: When live migrating a set of vms with vmotion Version-Release number of selected component (if applicable): 5.10.13.1 How reproducible: all the time Steps to Reproduce: 1. create and apply a control policy that has for purpose to copy the tag of the host to the vm / update the tag of the vm . This should trigger on vm migrate at least 2. set about 200 vms to migrate using vm motion Actual results: the migration did not trigger the control policy Expected results: the migration triggers the control policy Additional info: we do not see any vm migration event in the control.log or any call to a control policy after the migration this may not be relevant but the policy is set to be triggered on Service Provision Complete VM Settings Change VM Create Complete VM Clone Complete VM Guest Reboot VM Migration (vMotion) Power On Power Off VM Reset VM Resume each time the event "DrsVmMigratedEvent" the migration seems to not be detected, while in one case it was a "VmMigratedEvent" that was used and that did trigger the control policy.