Content Library Sync/Publish fails with "Reason: The operation failed due to The operation is not supported on the object"

Products

• VMware vSphere ESXi

Issue/Introduction

When publishing or syncing library objects, the operation will fail with a similar message in the vSphere Client UI:

"A general system error occurred:
Failed to publish library "content.library-name" (ID:
########-####-####-####-############) to subscribed library "content.library-name" (ID:
########-####-####-####-############) on vCenter
Server vCenterServer.domain.com. Reason: The operation failed due to The operation is not supported on the object."

Environment

vSphere ESXi 8.0.1
vSphere ESXi 8.0.2

Cause

The provisioning vmnic has a null value set in vsish while on ESXI 7.0 versions, which triggers the failure when the hosts are upgraded to 8.0 version/builds before 8.0 U3 because of a change in how this configuration is kept.

/var/log/vmkernel.log (source side of the content-library nfc transfer task)

<YYYY-MM-DD>T<time>Z In(182) vmkernel: cpu13:2100329 opID=XXXXX)Migrate: 102: ########-####-####-####-############ S: MigrateState: Starting migration off
<YYYY-MM-DD>T<time>Z Wa(180) vmkwarning: cpu13:2100329 opID=XXXXX)WARNING: Nfc: 330:  ########-####-####-####-############  S: failed to resolve net stack instance due to mismatch with vMotion server. Migration instance: vSphereProvisioning (0x431c47ab4b00). S$

Resolution

The issue is fixed in 8.0 U3 builds of ESXi. 

 

Workaround: 

To manually provision the net stack configuration with vmkX

vsish -e set /config/Net/strOpts/ProvisioningVmknics vmkX (replace x with the number of the provisioning vmk)

Additional Information

Same issue cause, but where cold migrations of VMs fail:  Cold Migration fails The operation is not supported on the object