(https://[IP_ADDRESS or FQDN]:5480) shows available updates, but clicking Stage or Stage and Install results in the error:"Error copying packages"
/var/log/vmware/applmgmt/update_microservice.log file contains HTTP/1.1 403 Forbidden errors when attempting to resolve RPM locations:YYYY-MM-DDTHH:MM:SS - 59#36 - update_functions:: runCommandAndCheckResult: 373 - DEBUG - runCommandAndCheckResult failed: '--YYYY-MM-DDTHH:MM:SS-- https://dl.broadcom.com/#################################/PROD/COMP/VCENTER/vmw/############/7.0.3.#####/package-pool/VMware-example-upgrade-##-##.##.#-########.x86_64.rpm\nResolving dl.broadcom.com... ###.##.#.###, ###.##.#.###\nConnecting to dl.broadcom.com|###.##.#.###|:443... connected.\nHTTP request sent, awaiting response... \n HTTP/1.1 403 Forbidden\n Date: Sun, DD MMM YYYY HH:MM:SS GMT\n Content-Type: text/plain;charset=UTF-8\n Content-Length: 12\n Connection: keep-alive\n Vary: Accept-Encoding\n Strict-Transport-Security: max-age=31536000; includeSubDomains\n Server: cloudflare\n CF-RAY: ########## ERROR 403: Forbidden.\n\n'YYYY-MM-DDTHH:MM:SS - 59#36 - dbfunctions:: executeDML: 54 - DEBUG - Executing Query {UPDATE meta SET _isdownloaded = 0, _downloadendtime = DATETIME('now') WHERE _name = ? } with parameters ('VMware-example-upgrade-##-##.##.#-########.x86_64.rpm',)YYYY-MM-DDTHH:MM:SS - 59#36 - rpmfunctions:: downloadRpm: 636 - ERROR - {'id': 'com.vmware.appliance.update.download_failed', 'default_message': 'Download failed', 'args': []}YYYY-MM-DDTHH:MM:SS - 59#36 - update_b2b:: _copyPackages:1030 - ERROR - Exception: {'id': 'com.vmware.appliance.update.download_failed', 'default_message': 'Download failed', 'args': []}YYYY-MM-DDTHH:MM:SS - 59#36 - update_b2b:: _copyPackages:1032 - DEBUG - Download/Checksum failed for VMware-example-upgrade-##-##.##.#-########.x86_64.rpm. Will attempt a retry for this rpm.
com.vmware.appliance.update.download_failedThe 403 Forbidden error is caused by a mismatch between the vCenter Server license and the download token used in the repository URL. Broadcom’s software repository validates that the download token and the product license belong to the same Site ID.
Common triggers include:
To resolve this issue, align the download token with the correct Site ID and entitlement.
Step 1: Identify the Correct Site ID
(https://[IP_ADDRESS or FQDN]:5480).Step 2: Generate a Matching Download Token
Step 3: Update vCenter Repository Configuration
If the vCenter license is not visible under the expected Site ID, or if unable access the required Site ID to generate a token, contact the Global Customer Assistance (GCA) team: Submitting product license requests or GCA tickets