# esxupdate -d http://blahblah.com/esx35/ESX350-200904201-SG/ --test update
INFO: No -b specified, selecting all bundles in depot.
INFO: Configuring...
ERROR: Descriptor release (ESX350-200904201-SG) doesnt match directory name (/var/spool/esxupdate)
When I run it with -r it's fine. But running -r is no good because it doesn't do dependencies.
I've also verified that all xml files on host esx001 and remote depot is identical.
Anyone know why it's doing this? Please help!
Dependencies are in orange.
ESX350-200904201-SG - PATCH
Product : ESX 3.5
md5sum: 8ca2816aacf2436ce8b346861a553394
Download Size: 7.3M Description : Updates VMX RPM
System Impact : VM Shutdown & No Host Reboot
KB/Release Notes :
Build Number: 158869
KB 1009852
04/10/2009 ESX350-200802411-BG
ESX350-200804402-BG
ESX350-200806405-BG SECURITY
ESX350-200810201-UG ESX350-200903201-UG ESX350-200903202-UG
Hi RParker,
But those orange existencies exist already on my esx box.
ESX350-200810201-UG 11:31:49 04/01/09 Updates VMkernel, Service Console, hostd
ESX350-200903201-UG 11:31:49 04/01/09 Updates VMkernel, Service Console, hostd
ESX350-200903202-UG 11:31:49 04/01/09 Updates ESX Scripts
They were already installed when we installed the latest ESX version. Do you mean I have to have those patch files on my remote depot?
Thank you.
They were already installed when we installed the latest ESX version. Do you mean I have to have those patch files on my remote depot?
NO.
You said you couldn't run esxupdate -r, now you can since you know the dependencies are there. So when you install this patch, you should be fine.
Ah I see what you're saying, yes I can run them with -r, and I'll probably end up doing that. This patch requires esx maint. mode so I'll have do that first.
Still curious to know why -d won't work properly, but will do the above method for now.
Thank you for the input.
Still curious to know why -d won't work properly, but will do the above method for now.
Great let me know if it works or not.