Patching Job - Analysis Options for Red Hat Enterprise Linux, Oracle Enterprise Linux, and SUSE Linux Enterprise

A Patching Job checks the configuration of patches on specific servers according to filters defined as part of the job definition.

On the Basic Options tab, you can perform the following actions:

  1. Choose one of the following options:
    • Analyze for missing RPMs and updates available for installed RPMs on a target server (Install Mode).

      Notes

      Do not choose Install Mode if you are including all errata or all RPMs from the catalog. Various conflicts and dependency issues between RPMs may occur because Install Mode attempts to install RPMs for which the base versions or earlier versions are not present.

      You are not required, nor is it recommended, to include the default RPMs Patch smart group that is part of the catalog. If no includes are specified, the analysis will check for the missing patches for the target server OS version and platform. If the include list is specified, there will be an explicit check for each rpm in the patch smart group.

    • Analyze only for updates available for installed RPMs on a target server (Update Mode).

  2. Create an Include/Exclude list for specific patches through the Include or Exclude Selection dialog box to override the default, which includes the entire Patch catalog in the analysis.

On the yum.conf tab, perform either of the following actions:

  • Select the Use Patch Global Configuration File check box if you want to use a yum.conf file with default settings provided with BMC Server Automation.

Or

  • Deselect the Use Patch Global Configuration File check box if you want to use a custom yum.conf file. You can customize the yum.conf file to configure the different patch analysis and deployment parameters. Your desired entries should be added in the text box provided. 

     Click here to see a sample of a yum.conf file.

    [main]
    debuglevel=4
    logfile=/var/log/yum.log
    pkgpolicy=newest
    distroverpkg=RedHat-release
    tolerant=1
    obsoletes=1
    plugins=0
    gpgcheck=0
    bootloader=1

Notes

The system default /etc/yum.conf file is not used in either of the above cases. 

In addition to the options listed in the sample yum.conf above, if you want to avoid the removal of old RPMs during patch analysis when a native yum is used, you can include the installonly_limit option in the yum.conf file. For more information, see the description of this issue in Troubleshooting Patch Management issues.

For more information about all the options that you can include in the yum.conf file, see the yum.conf man page.

The yum.conf tab applies only to Red Hat Enterprise Linux, Oracle Enterprise Linux, and SUSE Linux Enterprise servers. You can also customize the yum.conf file from the Patch Global Configuration option. For more information, see Global Configuration parameter list.

Where to go from here

Patching Job - Remediation Options

Was this page helpful? Yes No Submitting... Thank you

Comments