Service deployment is struck at Upgrade in progress.

Products

• VMware vDefend Firewall

Issue/Introduction

• Service deployment is struck at Upgrade in progress.
• Service Instances are up and running. VMs themselves are not showing any issues or going through upgrade and traffic redirection is working properly.
• For DUI you can see deployment/upgrade is in progress.
  
  INFO EamPollingThread AgencyMonitoringService 4429 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Looks like deployment/upgrade is in progress for DUI DeploymentUnitInstance/3aac9dcf-####-####-####-6dc23f7dd5ac


• NSX manager logs show Spec {0} is already deployed, and is not in UPGRADE_FAILED state. Nothing to upgrade.
  
  Operation:'POST@/api/v1/serviceinsertion/services/01a14758-####-####-####-c92c01a86016/service-deployments/b356b1f6-####-####-####-170af5448518' Operation status: 'failure' Error: Spec {0} is already deployed, and is not in UPGRADE_FAILED state. Nothing to upgrade.


• InstanceRuntime table from Corfu shows deployment successful.
  
  /opt/vmware/bin/corfu_tool_runner.py -o showTable -n nsx -t InstanceRuntime

  "deploymentState": "VM_DEPLOYMENT_STATE_DEPLOYMENT_SUCCESSFUL",
  "runtimeState": "VM_RUNTIME_STATE_IN_SERVICE",

Environment

VMware NSX 4.x

Cause

When cluster SVMs are upgraded partially (some upgraded and some failed). On next upgrade with same OVF URL, successful agents will be put in failed state.

Resolution

This issue is resolved in VMware NSX 4.2.0

Workaround:
The workaround is to move the appliance OVF URL to a new location and update SVMs again from NSX manager UI. This process triggers deployments for all queued/successful/failed VMs. All agents state will change to success if upgraded successfully.

Additional Information

Trend Micro service deployment can be affected