1. Automatically Installing Oracle Solaris 11.4 Systems
  2. Troubleshooting Automated Installations
  3. SPARC and x86 Error Messages
  4. Package Not Found

Package Not Found

If one of the packages specified in the AI manifest cannot be located in the IPS repositories, then the installer fails before installing any packages on the disk. In the following example, the installer could not find the package mypkg in the IPS repository. The following output is an example of what is displayed on the console: 

14:04:02    Failed Checkpoints:
14:04:02
14:04:02        generated-transfer-1230-1
14:04:02
14:04:02    Checkpoint execution error:
14:04:02
14:04:02        The following pattern(s) did not match any allowable packages.  Try
14:04:02        using a different matching pattern, or refreshing publisher information:
14:04:02
14:04:02                pkg:/mypkg
14:04:02
14:04:02    Automated Installation Failed.  See install log at /system/volatile/install_log

The following output is an example of a portion of the /system/volatile/install_log log file: 

PlanCreationException: The following pattern(s) did not match any allowable packages.
Try using a different matching pattern, or refreshing publisher information:

pkg:/mypkg

A related error occurs when you use AI to uninstall packages. The operation fails and the screen displays messages similar to the following example:

Failed Checkpoints: 
generated-transfer-809-1 
Checkpoint execution error: 
'pkg:library/python/python-compizconfig-27' matches no installed packages 
'pkg:/desktop/compiz/*' matches no installed packages 
Automated Installation Fails. See install log at 
/system/volatile/install.log 
application/auto-installer:default failed fatally: transitioned to 
maintenance

The AI manifest might contain the following definitions related to the package:

<software_data action=install"> 
<name>pkg:/entire@0.5.11-0.175.3</name> 
<name>pkg:/group/system/solaris-large-server</name> 
<name>pkg:/group/system/solaris-desktop</name> 
<name>pkg:/ncia/nisp/system/firstboot</name> 
<name>pkg:/system/device-allocation</name> 
</software_data> 
<software_data action=uninstall"> 
<name>pkg:/security/sudo</name> 
<name>pkg:/library/python/python-compizconfig-27</name> 
<name>pkg:/desktop/compiz/*</name> 
<name>pkg:/desktop/compiz</name> 
</software_data>

In this example, the AI is attempting to remove a package that does not actually exist on the system. Consequently, AI fails.

A case where this error risks occurring is if you uninstall packages using a generic manifest for both SPARC and x86 systems. Both platforms do not entirely share the same packages. Thus, AI would complete on one platform but fail on the other.

A number of workarounds are available to resolve this issue.

  • In the case of a missing package from the IPS repository, check whether the package in question is a valid package. If this package is available from a different IPS repository, add that IPS repository in the AI manifest by adding another publisher element to the source element.

  • In the case of the uninstalling of non-existing packages, adopt one of the following options before uninstalling:

    • Use the <reject> tag in the manifest to list packages to be excluded in the operation.

      Refer to the instructions in the /usr/share/auto_install/manifest/ai_manifest.xml sample file for the proper use of this tag.

    • Define your own group package within your own publisher that references the desired packages while omitting the undesired ones.

    • Use a different manifest for each platform.

For an optimal solution, consider using derived manifests that generate manifests specifically based on whatever conditions are desired for particular clients. See Chapter 4, Using a Script to Customize an Installation in Customizing Automated Installations With Manifests and Profiles.