I have an isolated VCSA which has no access to the Internet.
I have mounted a full patch ISO : VMware-vCenter-Server-Appliance-18.104.22.168100-15505668-patch-FP.iso
However when I run "software-packages stage --iso"
I get the following response:
[2020-02-05T14:53:28.036] : ISO mounted successfully
[2020-02-05T14:53:30.036] : ISO unmounted successfully
[2020-02-05T14:53:30.036] : Target patch version is not supported.
What am I missing here? Is there a trick to get this working?
what build number are you upgrading from?
you need to upgrade to 6.7 U1b before you can upgrade to U3+
I tried "VMware-vCenter-Server-Appliance-22.214.171.12400-11726888-patch-FP.iso" and that worked.
I then tried the "VMware-vCenter-Server-Appliance-126.96.36.199100-15505668-patch-FP.iso" and this still brings up "Target patch version is not supported"
So I tried "VMware-vCenter-Server-Appliance-188.8.131.52000-14070457-patch-FP.iso" and that also gave "Target patch version is not supported".
So I tried "VMware-vCenter-Server-Appliance-184.108.40.206000-13010631-patch-FP.iso", which then worked
Back to build 15505668? Nope still doesn't work.
So I do "VMware-vCenter-Server-Appliance-220.127.116.11000-14070457-patch-FP.iso", which works.
Back to build 15505668 again? which still doesn't work.
Now its late and I give up for now.
Annoyingly there are no release notes for U3c yet so its unclear whether there are any other pre-requisites.... Just out of interest, have you tried installing it via the VAMI?
You can still use VAMI when using the offline patch, you can specificy the CD drive when searching for updates rather than using the web. Unless youre saying even the VAMI is inaccessible from your network
IMO the documentation is really vague regarding updating/patching the vCSA.
On some places it states that all patches are cumulative, which apparently is not the case, and on others they write about difference between builds that are released on the download page vs. the patch portal, and then you have the release notes which sometimes contain information about unsupported updates, ...
For me it definitely requires clarification in a way everyone can understand!
Anyway, from what I read between the lines, it should be possible to update directly to the latest build that's available on the download page- currently is 18.104.22.168000-15132721 - which states "Use this package to update from any released VMware vCenter Server Appliance 6.7 to VMware vCenter Server 6.7U3b Appliance".
Assuming that the fp.iso has the same content as the updaterepo.zip, the fp.iso should work too. If it doesn't, then - as a last resort - the initial Update 3 release 22.214.171.124000-14367737 is what you may use as an intermediate step to Update 3c.
Note: From what I undaerstand, installation images on the patch portal, which are not available from the download page, are only meant for recovery/restore purposes.
It has just successfully done "VMware-vCenter-Server-Appliance-126.96.36.199000-14367737-patch-FP.iso".
So I'd guess the latest will now work, I'll try shortly to see if it at least stages, once it has finished rebooting.
I hadn't looked at using the VAMI, because in the past I had thought that it needed an Internet connection to be useful. Secondly, we try and use techniques that we can eventually script, as all this stuff may need to be automated at some point, which makes GUI based techniques unattractive.
So after doing "VMware-vCenter-Server-Appliance-188.8.131.52000-14367737-patch-FP.iso" I mounted "VMware-vCenter-Server-Appliance-184.108.40.206100-15505668-patch-FP.iso".
I did a stage of the iso on the CLI and this time no complaints, it staged correctly. I then unstaged it and had a look at the VAMI update. Yeah it looks pretty, but as I thought it would be tricky to automate, I would also argue that even to produce step-by-step written instructions would be easier using the CLI method, but maybe that's just me.
In any event at least the VCSA is up-to-date now.
We have a very similar issue here.
I have two Vcenter Servers both on 220.127.116.11000 - Build - 16046470
(These servers are in seperate physical locations)
I am trying to patch to "VMware-vCenter-Server-Appliance-18.104.22.168000-18485166-patch-FP" on both.
The first Vcenter Server (Lets call it Vcenter_1) Fails with the following :
Command> software-packages stage --iso
[2021-11-05T13:09:15.309] : ISO mounted successfully
[2021-11-05T13:09:16.309] : ISO unmounted successfully
[2021-11-05T13:09:16.309] : Target patch version is not supported.
The second Vcenter Server ( Lets call it Vcenter_2) doesnt have this issue and stages the iso without issues - Output below :
Command> software-packages stage --iso
[2021-11-05T13:09:06.309] : ISO mounted successfully
VMWARE END USER LICENSE AGREEMENT .......ect
Press ENTER key for more or Ctrl+c to quit
My Question is how is it possible that Vcenter_1 fails when Vcenter_2 sucseeds and stages the iso but both Vcenter servers are the same Version and Build?
I personally cant understand why one would work and one doesnt
Any assistance would be appriciated.
VCSA 22.214.171.12400 build 10244857 >> This is 6.7 U1
VMware-vCenter-Server-Appliance-126.96.36.199100-15505668-patch-FP.iso >> 6.7 U3c >>This includes Photos OS security patch .
This path is unsupported. You should always update the base version to 6.7 U3 and then the security patch. Its been same for ages now. https://docs.vmware.com/en/VMware-vSphere/6.7/rn/vcenter-server-appliance-photonos-security-patches....
In short anything which you see below for 6.7 is base versions. You can go to the specific base version of that update. Like U3/U3a/U3b then to a security patch like U3c/U3d.
https://customerconnect.vmware.com/en/downloads/details?downloadGroup=VC67U3O&productId=742&rPId=760... (All base versions)
vCSA/ESXi security patches will always be available here only.
I think you might have my comment confused with the origional posters issue.
My issue is similar but retains to different versions.
I have opened a new forurm question to resolve the confusion if you would like to reply with more correct or relatable information that might help my issue.
Apologies for the confusion.