Description of problem: When provisioning a service catalog item that is using an Azure orchestration template automation.log is showing an error of: [----] E, [2016-09-30T17:25:15.653605 #3208:e81994] ERROR -- : Class [System/Event/EmsEvent/AZURE] not found in MiqAeDatastore This error may be generated at other times, but I haven't looked. The surrounding log messages are: [----] I, [2016-09-30T17:25:15.395301 #3208:e81994] INFO -- : Updated namespace [/System/Process/Event?EventStream%3A%3Aevent_stream=10000000108640&MiqServer%3A%3Amiq_server=10000000000003&User%3A%3Auser=10000000000001&VmOrTemplate%3A%3Avm=10000000000309&event_id=10000000108640&event_stream_id=10000000108640&event_type=virtualMachines_deallocate_BeginRequest&object_name=Event&vm_id=10000000000309&vmdb_object_type=event_stream ManageIQ/System] [----] I, [2016-09-30T17:25:15.521430 #3208:e81994] INFO -- : Following Relationship [miqaedb:/System/Event/EmsEvent/AZURE/virtualMachines_deallocate_BeginRequest#create] [----] E, [2016-09-30T17:25:15.653605 #3208:e81994] ERROR -- : Class [System/Event/EmsEvent/AZURE] not found in MiqAeDatastore [----] I, [2016-09-30T17:25:15.653740 #3208:e81994] INFO -- : Followed Relationship [miqaedb:/System/Event/EmsEvent/AZURE/virtualMachines_deallocate_BeginRequest#create] The provisioning succeeds and there are no obvious issues. Version-Release number of selected component (if applicable): 5.6.1 How reproducible: Always Steps to Reproduce: 1. Order a service that provisions using an Azure Orchestration Template 2. 3. Actual results: Lots of ERROR -- : Class [System/Event/EmsEvent/AZURE] not found in MiqAeDatastore appear in the logs Expected results: No error would be logged. Additional info:
Azure eventing support was added in PR https://github.com/ManageIQ/manageiq/pull/7439. Has the automate model been reset? rake evm:automate:reset
Looks like you are running into Bug 1379435 which just had the fix back ported to the 5.6 (Darga) branch in PR https://github.com/ManageIQ/manageiq/pull/11545. *** This bug has been marked as a duplicate of bug 1379435 ***
Greg, I agree that this BZ is a duplicate of the one that you closed this to.