Troubleshooting Patch Management for Solaris 11
This topic contains troubleshooting information for issues that might occur when performing patch analysis for Solaris 11 using the scripts provided in BMC Server Automation. The topic includes the following sections:
Wrong repository set on target server
If a previous setting on the target server points to the wrong repository location, patch analysis for Solaris 11 might fail, with the error message "The path... does not contain a valid package repository."
To resolve this issue, manually unset the publisher on the target server, and then try running patch analysis again. Perform the following steps:
- To obtain the name of the publisher, run the following command:
- To unset the publisher on the target server, execute the following command (where <publisher name> is the name that you obtained in the previous step).
pkg unset-publisher <publisher name>
Package dependency issues due to version constraints
Patch analysis for Solaris 11 fails with an error regarding required package dependencies that were not found:
"require dependency on pkg:<pkg name and version> cannot be found"
To resolve such issues, you need to apply changes to package configuration at the Solaris 11 target to relax version constraints. For information about such issues and workarounds, refer to Oracle Solaris documentation about the Image Packaging System (IPS), such as https://blogs.oracle.com/Solaris11Life/entry/solaris_11_and_ips_potential. Further information about relaxing version constraints can be found in the Oracle Solaris Information Library, in https://docs.oracle.com/cd/E53394_01/html/E54739/gmias.html.