Unable to set email triggers for default alarms related to "Exhaustion" in vCenter 6.7

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Unable to configure email alert for pre-defined default alarms in vCenter 
• When trying to add an Action on "xxx Exhaustion on xxx" it is showing error
• HTML5 client just keeps loading if we click on edit for any of the pre-defined alarms
• Web-client gives an error stack when you try to add an email trigger

Error:
An internal error has occurred - Error #1034.
Reloading the client is recommended, so as to clear any problems left by this error.
Click Yes to reload the vSphere Web Client?

Error Stack
---------------------
TypeError: Error #1034
 at com.vmware.opsmgmt.client.views.alarms.definition.wizard::ActionsPageMediator/saveActions()
 at com.vmware.opsmgmt.client.views.alarms.definition.wizard::ActionsPageMediator/addItem()
 at com.vmware.opsmgmt.client.views.alarms.definition.wizard::ActionsPageMediator/onToolbarButtonClick()
 at flash.events::EventDispatcher/dispatchEvent()
 at mx.core::UIComponent/dispatchEvent()
 at com.vmware.widgets.controls.advancedDataGridExClasses::ToolContainer/onComponentClick()

• We see these messages in the Flex client logs

[2019-01-29T10:31:51.130+09:00] [INFO ] http-nio-9090-exec-5 70005826 100114 200017 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.
[2019-01-29T10:31:51.131+09:00] [ERROR] http-nio-9090-exec-5 70005826 100114 200017 com.vmware.vise.util.logging.LogServiceImpl [Flex|AppErrorHandler]Error #1034
TypeError: Error #1034
        at com.vmware.opsmgmt.client.views.alarms.definition.wizard::ActionsPageMediator/saveActions()
        at com.vmware.opsmgmt.client.views.alarms.definition.wizard::ActionsPageMediator/addItem()
        at com.vmware.opsmgmt.client.views.alarms.definition.wizard::ActionsPageMediator/onToolbarButtonClick()
        at flash.events::EventDispatcher/dispatchEvent()
        at mx.core::UIComponent/dispatchEvent()
        at com.vmware.widgets.controls.advancedDataGridExClasses::ToolContainer/onComponentClick()
[2019-01-29T10:32:34.192+09:00] [INFO ] health-status-52 com.vmware.vise.vim.cm.healthstatus.AppServerHealthService Memory usage: used=550,061,904; max=870,842,368; percentage=63.16434801665507%. Status: GREEN
no errors in the HTML5 client logs as it try to keep load.

Note: Date & time from logs will vary.

You may witness the same error message when you configuring an alarm for below 
 
1.Memory Exhaustion
2.CPU Exhaustion
3.SEAT Disk Exhaustion
4.Core and Inventory Disk Exhaustion
5.Root Disk Exhaustion
6.Boot Disk Exhaustion
7.Autodeply Disk Exhaustion
8.Diagnostics Disk Exhaustion
9.Image Bulder Disk Exhaustion
10.Log Disk Exhaustion
11.ESXI Dump Collector Disk Exhaustion
12.Update Manager Disk

Environment

VMware vCenter Server 6.7.x

Resolution

This issue is resolved in VMware vCenter 6.7 U2.

Workaround:
You can re-create the alarm and you will not see this issue.