After updating to vCenter Server 8.0 u2 or later, "Scan Entity" task is not started and remains in Recent Tasks tab.

Products

• VMware vCenter Server 8.0

Issue/Introduction

After updating to vCenter server 8.0 u2 or later (e.g., from 8.0 U1 b to 8.0 U3), you may encounter the following issues:

- "Scan entity" task(s) remain in "Queued" status in the [Recent Tasks] tab.
- The initiator is displayed as "Automatic compliance check".
- When you navigate to vCenter Server > [Configure] > [Scheduled Tasks] in vSphere Client, and start "Automatic compliance check" manually, the "Run scheduled task" task completes successfully, but the additional "Scan entity" task is queued in [Recent Tasks].

You will see the following messages in vmware-vum-server.log, located at /storage/log/vmware/vmware-updatemgr/vum-server.

YYYY-MM-DD HH:MM:SS info vmware-vum-server[10919] [Originator@6876 sub=InventoryMonitor] [InventoryMonitor 804] Event value type: vim.event.ScheduledTaskStartedEvent
YYYY-MM-DD HH:MM:SS info vmware-vum-server[10919] [Originator@6876 sub=InventoryMonitor] [InventoryMonitor 1726] UpdateHandler: Last updateSet
YYYY-MM-DD HH:MM:SS info vmware-vum-server[11407] [Originator@6876 sub=VumVapi::Lib::Utils::EventListener] [EventListener 167] Received an event callback.
YYYY-MM-DD HH:MM:SS info vmware-vum-server[12853] [Originator@6876 sub=ScheduledHclTaskManager] [ScheduledHclTaskManager 388] Find ScheduledTaskStartedEvent.
YYYY-MM-DD HH:MM:SS info vmware-vum-server[12853] [Originator@6876 sub=ScheduledHclTaskManager] [ScheduledHclTaskManager 415] ScheduledTaskStartedEvent is not generated by ScheduledHclTask.
YYYY-MM-DD HH:MM:SS error vmware-vum-server[13231] [Originator@6876 sub=Default] [ufaCrypt,457] UfaPublicKey::Verify <---
YYYY-MM-DD HH:MM:SS warning vmware-vum-server[13231] [Originator@6876 sub=ScheduledTaskMgr] [scheduledTaskMgr 1325] Custom fields have been modified by others. <---

Environment

vCenter Server 8.0 U2 or later.

Cause

This issue is caused by the change in the signature algorithm starting with vCenter Server 8.0 U2. If a Automatic Compliance Check is created in a version earlier than vCenter Server 8.0 U2, and the system is updated to vCenter Server 8.0 u2 or later, the validation of the task will fail due to differences in signature algorithms. As a result, the Automatic Compliance Check task will not be executed.

Resolution

To resolve this issue, delete "Automatic compliance check" and recreate it.

1. Log in to vSphere Client.
2. Navigate to vCenter Server > [Configure] > [Scheduled Tasks].
3. Select "Automatic compliance check" and click [REMOVE].
4. Select the ESXi host or cluster where you want to configure the automatic compliance check, and navigate to the [Updates] tab.
5. Navigate to [Hosts] > [Baselines] window, then click [SCHEDULE] on a tile.
6. (Optional) Set the frequency for running the compliance check and update the name of the task.
7. Click [SAVE] and complete the [Automatic compliance check] window.
8. Restart vpxd and update manager service to clear the stuck Scan entity Queued tasks.

service-control --stop vmware-vpxd
service-control --start vmware-vpxd

service-control --stop vmware-updatemgr 
service-control --start vmware-updatemgr