vCenter Upgrade from 7.0U1 to 7.0U2 fails with error "Invalid Type, Expected String, Instead got None Type"

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• You will see the below on the VAMI page during the upgrade  

      

• Checking Patchrunner.log under /var/log/vmware/applmgmt/Patchrunner.log

YYYY-MM-DDTHH:MM:SS content-library:Patch ERROR vmware_b2b.patching.executor.hook_executor Patch hook 'content-library:Patch' failed.
Traceback (most recent call last):
 File "/storage/updatemgr/software-updatex438i2oq/stage/scripts/patches/py/vmware_b2b/patching/executor/hook_executor.py", line 74, in executeHook
  executionResult = systemExtension(args) dynamicProperty = (vmodl.DynamicProperty) [],msg = '',

  faultCause = <unset>,
 faultMessage = (vmodl.LocalizableMessage) [],
  errorMessage = 'Entry with name serviceId: XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX not found.',
  name = 'serviceId: XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX'

Environment

VMware vCenter Server 7.0.x

Cause

Mismatch in content-library service ID.

Resolution

To fix this issue, cis.content-library service ID needs to be changed to match the correctly registered ID

Please follow the below steps for resolution:

Important: Before doing changes (step 4) please make sure to take offline snapshot of vCenter Server Appliance (vCenter Virtual Machine powered off)

1. Get the correct service ID through lstool following the below steps:

- Connect to vCenter Server Appliance through SSH using
- Enable Bash Shell using the below command:
  #  shell

- Run lstool:

 # /usr/lib/vmware-lookupsvc/tools/lstool.py list --url http://localhost:7090/lookupservice/sdk
- Find the cis.cls service attributes:

Example:
Name: cis.content-library.ServiceName
Description: cis.content-library.ServiceDescription
Service Product: com.vmware.cis
Service Type: cis.cls
Service ID: YYYYYYYYY-YYYY-YYYY-YYYY-YYYYYYYYYYYYYY --> This is the correct one
Site ID: default-first-site
Node ID: #########-#####-####-####-#########
Owner ID: vpxd-extension-##########-####-####-####-############@vsphere.local

2. Confirm the incorrect ID in the /etc/vmware-content-library/cls_service_cisreg.spec

# cd /etc/vmware-content-library/

# less cls_service_cisreg.spec

The last line of the file looks like the below:

           cmreg.serviceid = XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX --> This is the incorrect ID reported in the log 

3. Take offline snapshot of vCenter Server Appliance (vCenter Virtual Machine powered off) 
4. Change the service ID in the cls_service_cisreg.spec

- Take backup of the file
  # cp cls_service_cisreg.spec cls_service_cisreg.spec.old

- Replace the service ID with the correct one using text editor

•  # vi cls_service_cisreg.spec
• Press i to enter insert mode
• Delete the incorrect ID: "XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX" and add the correct one "YYYYYYYYY-YYYY-YYYY-YYYY-YYYYYYYYYYYYYY"
• Press ESC to exit insert mode.
• Press wq! to save and exit.

- # less cls_service_cisreg.spec   --> to make sure changes are applied

5. Proceed with the upgrade.