Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Troubleshooting Linux patching


The following table discusses issues that you might encounter when performing Linux patching.

Issue

Description

Yum failed to execute

Scenario 1STDERR: cat: rpm-includes.lst: No such file or directory ERROR::YUM dry run failed. ERROR::cmd:  failed!

For more information, see Yum-failed-to-execute-Scenario-1.

Scenario 2Could not find repodata.tar.gz corresponding to OsArch: 

‘[ARCH]' in the catalog ( at location '//<repo>/catalog_XXX/[ARCH]/repodata.tar.gz').

For more information, see Yum-failed-to-execute-Scenario-2.

Yum failed to complete

Scenario 1Missing Dependency: [rpm1] = [version] is needed by package [rpm2-version.arch] (installed)

For more information, see Yum-failed-to-complete-Scenario-1.

Scenario 2Missing Dependency: [rpm1] = [version] is needed by package [rpm2-version.arch] (repo)

For more information, see Yum-failed-to-complete-Scenario-2.

Scenario 3[rpm1] conflicts with [rpm2]

For more information, see Yum-failed-to-complete-Scenario-3.

Deploy Job failed

Scenario 1[rpm-version.arch]: Caching enabled but no local cache of //<staging>/blrepos/repo/packages/[rpm-version.arch].rpm from repo.

For more information, see Deploy-Job-failed-Scenario-1.

Scenario 2Transaction Check Error: package [rpm-version] is already installed.

For more information, see Deploy-Job-failed-Scenario-2.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Server Automation 8.3