Bug 1794573
Summary: | vmotion migration (live migrations using the vmware tool) are not triggering vm migration control policies | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
Component: | Automate | Assignee: | Lucy Fu <lufu> |
Status: | CLOSED ERRATA | QA Contact: | John Dupuy <jdupuy> |
Severity: | high | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
Priority: | high | ||
Version: | 5.10.13 | CC: | akarol, dmetzger, fdewaley, gmccullo, jfrey, jhardy, lufu, mfeifer, mkanoor, mshriver, obarenbo |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.10.15 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | 5.10.15.1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1788540 | Environment: | |
Last Closed: | 2020-02-25 05:39:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | CFME Core | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1788540 | ||
Bug Blocks: |
Comment 2
CFME Bot
2020-01-28 15:07:38 UTC
Based on the BZ description I am marking this verified. Steps of verification: 1) Create an action of type "Inherit Parent Tags" that inherits tags of various categories on a "Host/Node" parent type 2) Create a policy that calls this action on the event "VM Live Migration" 3) Assign this policy to a policy profile 4) Add a vSphere provider and assign the policy profile to it 5) Add some tags to the hosts on the provider so that they'll be inherited, make sure they are of the same category as the tags in 1) 6) Create a VM on the provider 7) In vcenter, migrate the VM to some other host 8) In CFME, verified that the tags of the new host were inherited/placed onto the VM created in 6) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:0589 |