Different Task Name for PowerOn Task

[irshadahmed_200]

Hey Guys,

We have the same VCenter version in 2 different locations and we are using Redhat Cloudforms for event management for billing purpose.

PowerOn, PowerOff and VMReconfigure are some of the events that we are capturing

Why are we seeing different fullformattedmessage on different vcenters with the same version and build specially poweron

version is 6.0.0 Build 5312803

Vcenter 1

PowerCLI C:\> Get-Task

Name State % Complete Start Time Finish Time

---- ----- ---------- ---------- -----------

PowerOffVM_Task Success 100 02:09:19 PM 02:09:19 PM

PowerOnMultiVM_Task Success 100 02:09:23 PM 02:09:23 PM

Power On virtual machine Success 100 02:09:23 PM 02:09:24 PM

PowerOnMultiVM_Task Success 100 02:10:01 PM 02:10:01 PM

Power On virtual machine Success 100 02:10:01 PM 02:10:02 PM

PowerOffVM_Task Success 100 02:10:21 PM 02:10:21 PM

PowerOnMultiVM_Task Success 100 02:15:22 PM 02:15:22 PM

Power On virtual machine Success 100 02:15:22 PM 02:15:23 PM

PowerOffVM_Task Success 100 02:15:41 PM 02:15:42 PM

PowerOnMultiVM_Task Success 100 02:16:16 PM 02:16:16 PM

Power On virtual machine Success 100 02:16:16 PM 02:16:17 PM

PowerOffVM_Task Success 100 02:16:32 PM 02:16:32 PM

Vcenter 2

PowerCLI C:\> Get-Task

Name State % Complete Start Time Finish Time

---- ----- ---------- ---------- -----------

powerOn Success 100 02:12:48 PM 02:12:49 PM

ReconfigVM_Task Success 100 02:14:06 PM 02:14:06 PM

PowerOffVM_Task Success 100 02:20:10 PM 02:20:11 PM

powerOn Success 100 02:20:14 PM 02:20:15 PM

So the PowerOn Task is showing differently on both the VCenters which is causing issues in the Cloudforms Events

According to Cloudforms the PowerOn event is not being sent by the VCenter so its adding as a generic event

Regards

Irshad

[daphnissov]

In the case of the first vCenter, you must be passing an array of virtual machines to the powerOn task and not just a single managed object. Otherwise, just a single powerOn task is recorded. So you either need to find out in your automation how to pass serially separate managed object references for VMs so Cloudforms can see and interpret powerOn, or you need to somehow have Cloudforms view them similarly, possibly through something like a regex.

[irshadahmed_200]

Those tasks are for multiple vms

All the tasks are recorded but the issue is that the task name is different in both the vcenters

In 1 vcenter the task name is recorded as

Power On virtual machine

And the other vcenter the task name is recorded as

powerOn

So there is discrepencies for the task name being recorded

Both the vcenters are running the same version, so don’t know why we have different names

Regards,

Irshad

[daphnissov]

What is initiating the power on in both vCenters? Is it exactly the same tool/script/process?

[irshadahmed_200]

I am directly initiating the poweroff and poweron through the vcenter for testing purpose

No matter where I initiate it from its the same

Task Name is different on both the vcenters

[daphnissov]

Is it possible you have had a solution, past or present, that added new or changed existing tasks in vCenter? Some solutions or plug-ins, when installed, will add their own alarms and task definitions, for example. I wonder if something similar happened in the case of one of your vCenters.

[irshadahmed_200]

No plugins have been installed other than patches which are all the same on all the vcenters

I even tested it on some of my test vcenters and they are also doing the same thing

Some vcenters have different task messages to the similar that I posted earlier

So just dont know why these event messages are different on all vcenters

[irshadahmed_200]

Any help on this please ??

Regards

Irshad