- #Vcenter 6.5 cannot access appliance api backup job 403 update
- #Vcenter 6.5 cannot access appliance api backup job 403 iso
You just login to the vCenter VAMI -> Update -> Settings -> copy the Default Repository URL -> Paste this into the “Specified” repository setting and hit Save. There are two methods to fix this, I actually converged a couple of environments this week, and I have encountered that I had to use both. 428Z INFO converge Cleanup successful with partial flag = True. T08:37:21.770Z INFO converge Unsetting the converge running flag T08:37:21.767Z ERROR converge Pre-checks failed for converge. T08:37:21.764Z INFO converge The vCenter Server appliance build number does not match with the vCenter Server appliance configured in the update repository. T08:37:21.764Z INFO converge Returning None T08:37:21.764Z INFO converge Couldn't open T08:37:21.763Z INFO converge Couldn't get : HTTP Error 404: Not Found T08:37:21.523Z INFO converge Fetching substring-after(/update/fullVersion/text(), "Build ") T08:37:21.522Z INFO converge Getting value 'password' from '/etc/applmgmt/appliance/nf' This file is located in “ # tail -f /var/log/vmware/converge/converge.log We can also see this from the converge.log logfile on the vCenter Server. It seems that the vCenter Server is actually still using the 6.5 repository, which makes sense when looking at the error message we were receiving. vCenter Server update repository settings on the CLIĪlright now we are getting somewhere. Just login through SSH on your vCenter Server and issue the following command update.get, before you enter the Bash Shell. But why is it telling me it’s not correct? Let’s check the settings on the CLI. The vCenter Server is using a 6.7 repository on the version it is running. This can easily be done by logging into the VAMI, going to Update and clicking on Settings: vCenter Server VAMI update repository settingsĪlright, this seems legit. Since I did not change anything on this environment, I checked the repository settings in the vCenter VAMI. The vCenter Server can update itself through an ISO, or through a connected online repository. So as a good engineer let’s start troubleshooting.
Well at least it’s a pretty good error message which indicates what’s happening, or not happening if we’re accurate. VCenter Server PSC Convergence error message The vCenter Server appliance build number does not match with the vCenter Server appliance configured in the update repository. This was all good until I clicked “Converge” I got hit pretty instantly with the following error message: vSphere Client Converge to embedded window When you hit this screen up you acknowledge that this operation will introduce downtime for the vCenter services, just enter the current vSphere SSO Domain administrator user and password, select a replication partner (if required), decide whether or not you want to join AD while you are at it, and acknowledge that you have a backup. So I started ahead and went to the Administration -> System Configuration part in the vSphere Client, selected the desired vCenter to converge and hit “Converge to Embedded”. Like I said earlier, everything can now be done from the vSphere Client and you don’t need a command line utility anymore. Disable vCenter HA before you start to converge the vCenter Server.
#Vcenter 6.5 cannot access appliance api backup job 403 iso
Make sure you download the exact same ISO for the vCenter Server version you are running. If your vCenter Server has no internet access, you should download the vCenter Server ISO beforehand.Make sure you have a backup for all the PSC’s and connected vCenters in the SSO domain.
Check all of the A and PTR DNS records.PSC Convergence Prerequisitesīefore trying to converge your external PSC configuration to an embedded one you should (at least) meet the following prerequisites to be sure you are good to go: I honestly never had the opportunity to use the vcsa-util cli tool together with a json file back in the day, but it seemed pretty straightforward to me, especially since it’s now all in the vSphere Client. In the release we are running (most current 6.7 U3 release) VMware has a nice build-in PSC Convergence tool right within the vSphere Client. The other day I had to converge a couple of vCenters to an embedded Platform Services Controller (PSC) configuration, because we updated all the vCenter’s and since VMware is moving away from the External PSC configuration.