-
1. Re: VRealize Orchestrator Appliance 7.3.0 fails to check for updates (404 Not Found)
daphnissov Feb 12, 2018 3:30 PM (in response to PredatorVI)It looks like it's checking the wrong repo or that file is down right now. Either way, that error means it's not finding the manifest that shows the current version at the repo and so it can't check its version against it. It may just be temporary.
-
2. Re: VRealize Orchestrator Appliance 7.3.0 fails to check for updates (404 Not Found)
PredatorVI Feb 12, 2018 3:35 PM (in response to daphnissov)I'll assume the URL is correct since that's what was configured out of the box and (im)patiently wait to see if resolves itself. I tried to validate the URL, but can't find any documentation to help.
-
3. Re: VRealize Orchestrator Appliance 7.3.0 fails to check for updates (404 Not Found)
daphnissov Feb 12, 2018 3:55 PM (in response to PredatorVI)There's no newer update, so I does nothing right now even if that is available.
-
4. Re: VRealize Orchestrator Appliance 7.3.0 fails to check for updates (404 Not Found)
PredatorVI Feb 12, 2018 4:08 PM (in response to daphnissov)True, but I'm new to VRO and there is a level of confidence I'm lacking in my setup if I can't even check for updates.
I went ahead and attempted to configure it via https://10.131.24.26:8283/vco-controlcenter/ it seemed to initially work. I connected it to my vcenter server using administrator@vsphere.local and set my Administrators group to "Administrators" and when I saved the configuration all I get now when hitting the control center URL at https://10.131.24.26:8283/vco-controlcenter/ is yet another 404.
-
5. Re: VRealize Orchestrator Appliance 7.3.0 fails to check for updates (404 Not Found)
daphnissov Feb 12, 2018 4:49 PM (in response to PredatorVI)This is an unrelated issue and so it'd be best to create another thread.
-
6. Re: VRealize Orchestrator Appliance 7.3.0 fails to check for updates (404 Not Found)
Drygast Feb 15, 2018 3:18 AM (in response to PredatorVI)I just installed the latest version of the vRO appliance and recieved the exact same error message. Seems like the manifest file has been removed. I'm on version 7.3.0.21553 so I tried changing the repository URL in the VAMI gui (https://ip.of.vRO:5480) to the build version and now vRO actually checks for new versions.
So log on to VAMI -> Go to the Update tab and select settings -> Under the Update Repository section select "Use Specified Repository" enter https://vapp-updates.vmware.com/vai-catalog/valm/vmw/00642c69-abe2-4b0c-a9e3-77a6e54bffd9/7.3.0.21553.latest/
Click "save settings" and go back to the status page and retry the update
As a test, I downloaded and installed version 7.2, upgraded the appliance using VAMI GUI and when it was upgraded to version 7.3.0.21533 I checked the URL used. When doing an upgrade like this the URL repository is actually the one above. So the problem only occurs for fresh installations of vRO 7.3.0