Changes made to /usr/lib/vco/app-server/bin/setenv.sh file is not persistent.
search cancel

Changes made to /usr/lib/vco/app-server/bin/setenv.sh file is not persistent.

book

Article ID: 409732

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Values added to /usr/lib/vco/app-server/bin/setenv.sh within the vco-container were not persisting after changes.

Environment

Aria Automation 8.18.x
Aria Orchestrator 8.18.x

 

Cause

The Update Manager plug-in (vum.dar) build ID did not align with the out-of-box (OOB) build ID of the Aria Automation Orchestrator Update Manager plug-in.
Due to this mismatch, changes made to the configuration were not persistent.

Resolution

Note: Mare sure to take snapshot (Without Memory) of all the Aria Automation | Orchestrator nodes 

 

  • Removed the Update Manager plug-in and waited for the vco pod to restart
  • Removed remnants related to vum or update-manager dar files using:
find /data/vco -iname "*vum*.dar" -delete
find /data/vco -iname "*update-manager*.dar" -delete
  • Re-installed the Update Manager plug-in and waited for the vco pod to restart
  • Deleted all VUM (Update Manager) endpoint resource configurations from Resources → VUM → Configuration
  • Verified functionality by expanding vSphere vCenter Server plug-in endpoints in the Inventory
  • Verified functionality by expanding vSphere Update Manager plug-in endpoints in the Inventory.