[R5.0 vcenter]Eam losing connection and agency getting deleted upon resolving issue whille esxi is coming out of standby mode

Bug #1791244 reported by aswani kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R5.0
Won't Fix
Medium
amudhar
Trunk
New
Medium
amudhar

Bug Description

Eam losing connection and agency getting deleted upon resolving issue whille esxi is coming out of standby mode
After restarting eam service from vcenter server every thing is fine

If its valid scenario I think we need to handle this
Steps followed
1)Put esxi in standby mode
2)power on to exit from stand by mode
3)Before exiting from standby mode go to vcenter eam manager and do resolve issue
4)wait untill esxi exits from standby mode ,contrail-agency gets deleted from manager
5)To resolve this issue restart the eam service on vcenter server

tags: added: vmware
tags: added: vcenter-only
removed: vmware
Revision history for this message
amudhar (amudha) wrote :

Recommended Procedure:
1. "Resolve Issues" from EAM - will exit the ESXi host from standby mode and power on ContrailVM.
2. If ESXi host is powered on, wait for host to be back up and "Resolve Issues" from EAM post that if applicable

Workaround:
To resolve the issue as described in the bug, restart the ESX Agent Manager service on vcenter server.

Administration -- Deployment -- System Configuration -- Services -- ESX Agent Manager -- Restart

To tack and debug the EAM exception, SR is raised with VMWare - #18932826409

amudhar (amudha)
tags: added: releasenote
Revision history for this message
Jeba Paulaiyan (jebap) wrote :

In vcenter deployments, recommended procedure to bring a ESXi host out of standby mode:

1. "Resolve Issues" from EAM - will exit the ESXi host from standby mode and power on ContrailVM.
2. If ESXi host is powered on, wait for host to be back up and "Resolve Issues" from EAM post as applicable

In the above procedure, if the EAM looses connection and the agency is deleted, apply the following workaround:

To resolve the issue as described in the bug, restart the ESX Agent Manager service on vcenter server.

Administration -- Deployment -- System Configuration -- Services -- ESX Agent Manager -- Restart

To tack and debug the EAM exception, SR is raised with VMWare - #18932826409

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.