Bug 1247061

Summary: VMware provider events not being processed by control
Product: Red Hat CloudForms Management Engine Reporter: ncatling
Component: ControlAssignee: Lucy Fu <lufu>
Status: CLOSED WORKSFORME QA Contact: Dave Johnson <dajohnso>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.4.0CC: jhardy, ncatling, obarenbo
Target Milestone: GA   
Target Release: 5.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-30 15:51:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
evm.log snippet
none
policy examples none

Description ncatling 2015-07-27 09:08:00 UTC
Created attachment 1056526 [details]
evm.log snippet

Description of problem:
VMware events are not being processed/detected by control policies.

Version-Release number of selected component (if applicable):
CFME 5.4.0

How reproducible:
Assign provider event policy to VMware provider (examples attached). Create event directly in VMware vCenter, for example power off a VM. Control policy is not triggered.

Steps to Reproduce:
1. Import\assign policy to VMware (attached)
2. Create event directly in VMware (for example power off a machine)
3. Monitor policy.log (no updates detected)

Actual results:
Control policy not triggered.

Expected results:
Control policy should be triggered.

Additional info:
evm.log attached indicates event catcher is detecting the event correctly, however it is not being passed/detected by control.

Comment 1 ncatling 2015-07-27 09:09:31 UTC
Created attachment 1056527 [details]
policy examples

Comment 3 Greg McCullough 2015-07-27 14:06:09 UTC
Lucy - Please take a look at this and let me know if you need any help.  I was playing with events/policies against VMware last week and did not experience the reported issues so I am thinking it is a configuration issues somewhere.

ncatling - Do you still have the environment configured and can we connect to it?