TaskActionStepsReference1

Understand problem scope

Do the following:

• Identify whether the issue affects all or subset of targets.
• Identify whether specific RPMs are affected by this issue.

2

Identify and locate the logs.

The Job Log Package for the Redhat Patch Analysis job captures all the log files required to troubleshoot the issue.

See the attached reference for more information.

3

Review the log files to know the full error message and affected patches

The following entries in the log file indicate the type of error:

• • Package error: YUM dry run failed. For more details, please execute job in debug mode and check yum.err.logERROR::Package: 
  • Multilib error: YUM dry run failed. For more details, please execute job in debug mode and check yum.err.logERROR::Multilib version problems found.
    

Review the following entries to know the specific RPMs: For example,

• Package: subscription-manager-1.24.26-3.el7_8.x86_64 (repo)
• ERROR::Protected multilib versions: augeas-libs-1.4.0-2.el7.i686 != augeas-libs-1.1.0-17.el7.x86_64

4

Analysis

Review the information in the "Resolutions for common issues" section to understand the issues that can result in the "YUM dry run failed" errors and how they are typically resolved.

If you are unable to identify and resolve the problem, create a BMC Support Case.

5Creating a BMC Support Case

Provide the following information and log files when creating a case with BMC Customer Support:

• Scope of the issue as identified in step 1
• Logs collected in step 2
• The Application Server OS vendor and version
• The Application Server product version
• The filters selected in the Patch Catalog