Troubleshooting Redhat Patch Analysis yum dry run failed errors
A Redhat Patch Analysis job fails with "YUM dry run failed" error against one or more target servers.
This topic helps the reader to locate and review the appropriate log files to determine why the Redhat Patch Analysis job failed and either identify and resolve the issue or create a BMC Customer Support case.
Issue symptoms
A Redhat Patch Analysis job fails against one or more target servers with the "YUM dry run failed" error.
The following image shows how the failure is represented in the job run log.
Or
The "YUM dry run failed" error is usually followed by one of two different detailed errors. The following highlighted section indicates the type of error:
- Dependency problem
STDERR: ERROR::YUM dry run failed. For more details, please execute job in debug mode and check yum.err.logERROR::Package: subscription-manager-1.24.26-3.el7_8.x86_64 (repo)
- Multilib problem
Error 15 Sep, 2017 11:52:24 PM STDERR: cat: parsed-include.lst: No such file or directory ERROR::YUM dry run failed.
For more details, please execute job in debug mode and check yum.err.logERROR::Multilib version problems found.
This often means that the rootERROR:: yum will tell you what the root cause is
(which packageERROR:: message showing the root cause of the problem.
ERROR::Protected multilib versions: augeas-libs-1.4.0-2.el7.i686 != augeas-libs-1.1.0-17.el7.x86_64
Issue scope
- The issue may occur on a single or multiple Redhat target servers.
- The issue may occur for a single or multiple Redhat patches.
Diagnosing and reporting an issue
Task | Action | Steps | Reference |
|---|---|---|---|
1 | Understand problem scope | Do the following:
| |
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:
Review the following entries to know the specific RPMs: For example,
| |
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. | |
5 | Creating a BMC Support Case | Provide the following information and log files when creating a case with BMC Customer Support:
|
Resolutions for common issues
Symptom | Action | Reference |
|---|---|---|
Package Dependency issue STDERR: ERROR::YUM dry run failed. For more details, please execute job in debug mode and check yum.err.logERROR::Package: subscription-manager-1.24.26-3.el7_8.x86_64 (repo) | Review the embedded video, which walks your through the process of reviewing the logs to determine the reason for failure. | |
Multilib issue: Error 15 Sep, 2017 11:52:24 PM STDERR: cat: parsed-include.lst: No such file or directory ERROR::YUM dry run failed. | Review the embedded video, which walks your through the process of reviewing the logs to determine the reason for failure. |