vCenter Server Extension "vService Manager" retains old version after vCenter update

Products

• VMware vCenter Server
• VMware vCenter Server 7.0

Issue/Introduction

After updating vCenter from version 7.0u1 to 7.0u2 or 7.0u2 to 7.0u3, the vCenter Server Extension "vService Manager" remains on the previous version. For example:

Updated vCenter 7.0u1 - 7.0u2: vCenter Extensions -> vService Manager 7.0.1, vSphere ESX Agent Manager 7.0.2
Updated vCenter 7.0u2 - 7.0u3: vCenter Extensions -> vService Manager 7.0.2, vSphere ESX Agent Manager 7.0.3

Environment

 vCenter Server 7.0.x

Cause

It is a purely cosmetic issue for "built-in" extensions.

The vService Manager extension is not a part of VPX_EXT table in vPostgres database, so manual update is not possible.

Resolution

This issue is not an operational problem, and the service will be updated when transitioning to a later version.

VSM is a built-in extension, and its version number does not serve any external purposes