vSphere HTML Client - editing custom alarm seems to break the definition

[CathyBr]

Hi,

our QA found a new problem which deals in the changing of the plug-ins custom alarms.

During the plug-in installation we define a number of custom events and alarms.  The alarms are not activated.  When the customer decides to edit one of these alarms, an error occurs.

It can be reproduced as follows:

1) Have a custom alarm defined (during installation)

2) In the HTML Client (6.7) - select a vcenter in the navigation tree.  Navigate to Configure-> Alarm definitions

3) Select the custom alarm , and click on Edit..  Continue through the wizard - nothing needs to be changed to reproduce this.

4) Save the definition.

The following error occurs:

Cannot construct instance of "com.vmware.vise.util.serialization.mixin.TypeNameImplMixin$TypeNameImplBuilder",

problem: null

at [Source: (String) " {

"_type": "com.vmware.vim.binding.vim.alarm.AlarmInfo",

"name": "Acme Test Alarm",

"key": "",

"description" : "this is a test alarm",

"entity" : {

"type" : "Folder",

"value" : "group-d1",

"serverGuid": "aa98acd4-8b59-489b-a5c4-b335690a303a",

"_type" : "com.vmware.vim.binding.vmodl.ManagedObjectReference"

},

"enabled" : true,

"expression" : {

"_type" : "com.vmware.vim.binding.vim.alarm.OrAlarmEx.......

}

So it seems that that the "key" value of the alarm gets lost somewhere - this is similar to the problems we encountered when editing custom roles (earlier discussion).

Could this be confirmed?

Cathy

[_vladi_]

Hi Cathy,

This does not sounds like a plugin related problem - more like issue with a core vSphere Client feature.

Could you please add information on what vSphere Client versions you experience the bug on?

I will forward this internally.

Cheers,

Vladi

[CathyBr]

Hi _vladi_

I just reproduced it on Html Client - V6.7 U1...

thanks for your help

Cathy

[_vladi_]

It turns out this is a known issue with alarms which should be addressed in a future vSphere Client release without changes to your solution.

Cheers,

Vladi

[CathyBr]

Hi Vladi,

sorry, but it seems that this functionality has gotten even worse in 6.7U2.  I just performed a retest for our QA, and now it is not possible to edit a Custom Alarm at all.

If you look at the details of the Alarm by toggling it in the list, you see that it is parsed properly:

But when you start the edit wizard, the Alarm Rules are not parsed correctly, and nothing can be editied at all:

[LokeshN]

Hi Cathy,

Sorry for making you wait for long. Unfortunately the bug was raised and fixed immediately after 6.7u2 was released. So, the fix will be available in 6.7 u3.

For the time being, only alternative I could think of is using Flex client.

Thanks,

Lokesh

[CathyBr]

Hi Lokesh,

thanks very much, our QA has tested it, and it is working in 6.7u3.

Just one more question, will the fix be made available in 6.5xxx?

thanks

Cathy