Sun Management Center 3.5 Update 1b Release Notes

Base-Only Installation Using Agent-Update Fails to Add Essential Patches (6219534)


Note –

If you create an agent-update image that included the base product and any add-on product, this information does not apply. This information applies when you use either es-imagetool or es-gui-imagetool to create an agent-update image of the base product only (that is, no add-ons in the image).


Workaround: There are two scenarios, depending on the operating system you are using.

To deploy Solaris 2.6 to Solaris 9 base agent images from a from a 3.5.1a server (Solaris 8 Sun Management Server with patch 118388-03, Solaris 9 or Solaris 10 Sun Management Server with patch 118389-03) using agent-update.bin or Job Manager, follow these steps:

  1. Deploy the agent image on the target host.

  2. Deploy the patch image on the target host.

To deploy Solaris 10 base agent only image from a Sun Management Center 3.5 Update 1a server (Solaris 8 Sun Management Server with patch 118388-03, Solaris 9 or Solaris 10 Sun Management Server with patch 118389-03) using agent-update.bin, follow these steps:

  1. Pull the agent image using agent-update.bin and ignore the following message at the end of agent-update.bin:

    es-inst command will be timed out in 3600 seconds

    es-inst passed

    Doing setup of base product ...

    setup of base product will be timed out in 1800 seconds

    base setup failed

    install scripts failed

    Error: running InstallClient

    Error: running InstallClient with error code -1

  2. Apply the patch for the base agent on Solaris 10 (patch 118389-03) located on the second CD at:

    <mount-point>/image/Patches/Essential/Solaris_9

  3. Run es-setup and complete the agent installation.