VUM/VLCM sync update fail: A depot is inaccessible or has invalid contents
search cancel

VUM/VLCM sync update fail: A depot is inaccessible or has invalid contents

book

Article ID: 366910

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Sync update task fails in the VC when VC try to sync the VUM/VLCM updates from online portal with the below error
  • A general system error occurred: A depot is inaccessible or has invalid contents. Make sure an official depot source is used and verify connection to the depot

Environment

Error :- A general system error occurred: A depot is inaccessible or has invalid contents. Make sure an official depot source is used and verify connection to the depot

Log Snippets :- 

Filepath: /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log

2024-04-17T10:01:24.877Z warning vmware-vum-server[28824] [Originator@6876 sub=VumVapi::Lib::Utils] [EmbeddedPyServiceProvider 472] Connecting to https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/vmw-depot-index.xml failed, err: curl_easy_perform() failed: cURL Error: Timeout was reached, Failed to connect to hostupdate.vmware.com port 443 after 3001 ms: Timeout was reached
2024-04-17T10:01:24.877Z warning vmware-vum-server[28824] [Originator@6876 sub=VumVapi::Lib::Utils] [EmbeddedPyServiceProvider 425] Failed 10 times when connecting online depot https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/vmw-depot-index.xml
2024-04-17T10:01:24.877Z error vmware-vum-server[28824] [Originator@6876 sub=ServiceProvider] [EmbeddedPyServiceProvider 1570] At least one online depot is  not accessible: https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/vmw-depot-index.xml, https://hostupdate.vmware.com/software/VUM/PRODUCTIO
N/main/vmw-depot-index.xml, https://hostupdate.vmware.com/software/VUM/PRODUCTION/iovp-main/vmw-depot-index.xml, https://hostupdate.vmware.com/software/VUM
/PRODUCTION/vmtools-main/vmw-depot-index.xml
2024-04-17T10:01:24.878Z error vmware-vum-server[28824] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SyncDepotsTask] [SyncDepotsTask 221] Failed to sync depots. Merged depot content is invalid: Error:
-->    com.vmware.vapi.std.errors.error
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.depotContent.ValidationError<A depot is inaccessible or has invalid contents. Make sure an official depot source is
 used and verify connection to the depot.>
--> 
2024-04-17T10:01:24.882Z info vmware-vum-server[28824] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SyncDepotsTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SyncDepotsTask ID:52389bf9-1bef-5bbe-1c75-02d99f916369. Finalizing Task
2024-04-17T10:01:24.882Z info vmware-vum-server[28824] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SyncDepotsTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SyncDepotsTask ID:52389bf9-1bef-5bbe-1c75-02d99f916369. Task Finalization completed.
2024-04-17T10:01:24.882Z error vmware-vum-server[28824] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.SyncDepotsTask] [Task, 524] Task:com.vmware.vcIntegrity.lifecycle.SyncDepotsTask ID:52389bf9-1bef-5bbe-1c75-02d99f916369. Task Failed. Error: Error:
-->    com.vmware.vapi.std.errors.error
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.depotContent.ValidationError<A depot is inaccessible or has invalid contents. Make sure an official depot source is used and verify connection to the depot.>
--> 
2024-04-17T10:01:24.884Z warning vmware-vum-server[28726] [Originator@6876 sub=TaskStatsCollector] [taskStatsCollector 190] Task type or creation time not present
2024-04-17T10:01:24.887Z info vmware-vum-server[28824] [Originator@6876 sub=PM.AsyncTask.SyncDepotsTask{10}] [vciTaskBase 1496] SerializeToVimFault fault:
--> (vmodl.fault.SystemError) {
-->    faultCause = (vmodl.MethodFault) null, 
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vcIntegrity.lifecycle.depotContent.ValidationError", 
-->          arg = <unset>, 
-->          message = <unset>
-->       }
-->    ], 
-->    reason = "vLCM Task failed, see Error Stack for details."
-->    msg = "{
-->     "data": null,
-->     "error_type": "ERROR",
-->     "messages": [
-->         {
-->             "args": [],
-->             "default_message": "A depot is inaccessible or has invalid contents. Make sure an official depot source is used and verify connection to the depot.",
-->             "id": "com.vmware.vcIntegrity.lifecycle.depotContent.ValidationError"
-->         }
-->     ]
--> }"
--> }
--> Converted fault:
--> (vim.fault.ExtendedFault) {
-->    faultCause = (vmodl.MethodFault) null, 
-->    faultMessage = (vmodl.LocalizableMessage) [
-->       (vmodl.LocalizableMessage) {
-->          key = "com.vmware.vcIntegrity.lifecycle.depotContent.ValidationError", 
-->          arg = <unset>, 
-->          message = <unset>
-->       }
-->    ], 
-->    faultTypeId = "SystemError", 
-->    data = (vim.KeyValue) [
-->       (vim.KeyValue) {
-->          key = "faultCause", 
-->          value = ""
-->       }, 
-->       (vim.KeyValue) {
-->          key = "reason", 
-->          value = "vLCM Task failed, see Error Stack for details."
-->       }
-->    ]
-->    msg = "{
-->     "data": null,
-->     "error_type": "ERROR",
-->     "messages": [
-->         {
-->             "args": [],
-->             "default_message": "A depot is inaccessible or has invalid contents. Make sure an official depot source is used and verify connection to the depot.",
-->             "id": "com.vmware.vcIntegrity.lifecycle.depotContent.ValidationError"
-->         }
-->     ]
--> }"
--> }

Cause

  • This error appears if the customer has firewall between VC and https://hostupdate.vmware.com and if the customer not allowed the IPs of https://hostupdate.vmware.com in their firewall.

Resolution

Add the allow rules in firewall to allow https and http (443 and 80) traffic from VC to hostupdate.vmware.com 

IPv4
162.159.140.167
172.66.0.165

IPv6
2a06:98c1:58::a5
2606:4700:7::a5

 

Please do refer the article :- https://kb.vmware.com/s/article/82205 for the Changes on the IP List changes.

Additional Information

Please do refer the article :- https://kb.vmware.com/s/article/82205 for the Changes on the IP List changes.