Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

Patch Installation Using esxupdate Fails Because 2nd-Level Dependency Is Not Installed

Details

When you use esxupdate to install a patch bundle with more than one level of dependencies, the installation fails with error messages when the 2nd-level dependency has not been installed.

For example, suppose Bundle-A requires Bundle-B and Bundle-B requires Bundle-C. When you use "esxupdate -d <depot-dir> -b Bundle-A " to install Bundle-A when Bundle-C has not been installed, the installation fails.

The following output shows an actual example of this issue:

# esxupdate -d depot -b ESX350-200808407-BG update
INFO: Configuring...
ERROR: [ESX350-200808407-BG] requires ESX350-200808402-BG, but it is not applicable.
[ESX350-200808402-BG] requires ['ESX350-200808201-UG'] but these bundles cannot be found. Please make sure they are in the depot and specified in the bundle list.
 
Here, ESX350-200808402-BG requires ESX350-200808201-UG and ESX350-200808408-BG. ESX350-200808408-BG is installed because ESX350-200808407-BG requires it, but ESX350-200808201-UG is not installed. This causes the failure.

Solution

To resolve this issue, install the lower-level dependency first.
 
Continuing with the example previously shown, run the following command to install the lower-level dependency ESX350-200808201-BG first, followed by the patch that initially failed to install:
 
# esxupdate -d depot -b ESX350-200808201-BG -b ESX350-200808407-BG update

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 1007060
  • Updated: Aug 14, 2009
  • Products:
    VMware ESX
  • Product Versions:
    VMware ESX 3.0.x
    VMware ESX 3.5.x