Changes made to autodeploy configurations are not taking affect till restarting autodeploy service.
search cancel

Changes made to autodeploy configurations are not taking affect till restarting autodeploy service.

book

Article ID: 315221

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

This article is to provide a solution to let autodeploy changes reflect in UI without the need of restarting autodeploy .

Symptoms:
Changes made to autodeploy configurations are not taking affect till restarting autodeploy service.
Examples for those changes  :
1- trying to install new ESXi host using autodeploy rule, the host is installed correctly and it is added to the correct cluster, but we can't see the host listed in the deployed hosts in autodeploy page until restarting autodeploy service

2- Trying  to change the assigned image profile for a host will not be reflected in the GUI till we restart the autodeploy service.

Environment

VMware vCenter Server Appliance 6.7.x

Cause

issue is caused by VPX_EVENT_SEQ values overflow int event keys

Resolution

1- take a snapshot for vcenter 
2- stop vpxd service
3- run the below command
/opt/vmware/vpostgres/current/bin/psql -U postgres VCDB -c "ALTER SEQUENCE VPX_EVENT_SEQ RESTART WITH 1"
4- start vpxd
5- restart autodeploy service