Handling Installation Issues

If the job failed during installation, use these checks to find a solution.

• Check the permissions needed by the component for install. The permissions might conflict with the permissions of the logged-in user. The Job Log of the failed host will show permissions as the reason for failure.

• Try to install the component manually with Linux terminal commands. Afterwards, run a Check System (see Running Predefined Profiles) to handle dependency issues.

  If the installation fails for an NCO (non-certified component), the Job Log might provide one of the following reasons.

  • Conflict with. Listed NCO has possible conflicts with a component from the To Do list.

  • Downgrade. Listed NCO appears to be a newer version of a component from the To Do list.

  • Possible Unavailability. Installing one of the components from the To Do list might cause the listed NCO to become inoperable.

• Run the Local Software Review predefined profile and replace NCOs with COs, or uninstall the NCOs.

• Make sure that the NCO has been detected and added to the components list. If the local software package is not under Local RPMs or Local PKGs, search for it under a CO listing in Software (see To Find Components). If the NCO is not in the components list, add it (see Adding Undetected Linux Software).