One of the most common issues for Cloud Proxy upgrade failure is due to the provider-runtime.xml file not getting populated correctly or getting corrupted
Exception
"Failure: Error downloading manifest. Please contact your vendor. The requested Url returned error: 404 Not found url https://vapp-updates.vmware.com"
Resolution
Check the contents of provider-runtime.xml
/opt/vmware/var/lib/vami/update/provider/provider-runtime.xml<service>
<properties>
<property name="jobId" value="1" />_
<property name="jobList" value='{ "Check":{ "JobStatus": "Failed", "JobState": 8, "TimeOfLastStateChange": "20210120101111.982008+000", "ErrorCode": 20, "ErrorDescription": "Error downloading manifest. Please contact your vendor. The requested URL returned error: 404 Not Found URL: https:\/\/vapp-updates.vmware.com\/vai-catalog\/valm\/vmw\/a1ba78af-ec67-4333-8e25-a4be022f97c7\/7.2.0.33184.latest\/manifest\/manifest-latest.xml", "TimeBeforeRemoval": "00000000000500.000000:000", "TimeSubmitted": "20210120101031.385064+000", "InstanceID": "VMware-VAMI:Job_1" }}' />_
</properties>
</service>
If the file has contents similar to the above, manually update the file with the following contents and restart the cloud proxy.
<service>
<properties>
<property name="localRepositoryAddress" value="https://ci-data-collector-sandbox.s3.amazonaws.com/upgrade" />
<property name="localRepositoryPasswordFormat" value="base64" />
</properties>
</service>
This should help in fixing the Cloud Proxy Upgrade
Comments