Updating esxupdate database building a good dating profile
To fix this issue, you need to make some changes to the file in the Cisco patch bundle, but you also need to deinstall and reinstall Update Manager to be able to add the modified extension.(you can not remove an imported patch or extension….) First time I choose to keep the Update Manager database at the reinstall (the KB article was not clear on this) but still could not import the modified extension bundle.Vsphere doesn't give much information on this but it shows "The host returns esxupdate error code:15. Check the update manager logs and esxupdate log files for more details" I cant see anything useful in the update manager logs.Below is part of the file the update section that contains errors.This is something I have reported internally and hopefully will be fixed in a future update.
One of the new features that I am most excited about is the ability to upgrade ESXi itself using the "Update" feature which was first introduced in EHC v3.
The description of the cause of the problem is: This issue occurs due to the difference in the way that Cisco and Update Manager create folder names for the repository.
Update Manager creates folder in lowercase (csco), whereas the metadata from this patch looks for an uppercase folder.
Command: update Args: ['update'] Options: 2013-10-16TZ esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/boot Option', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.
2013-10-16TZ esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/boot Option', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.
You can either specify a local datastore path to the such as the following: /vmfs/volumes/datastore1/ESXi600-201510001/or you can specify an HTTP(s) URL to the like the following: 4 - Once you click the "Update" button, you will be asked to confirm and then you should see task kicked off called "Install Host Patch V2".