Skip to Content
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.

Yum failed to complete - Scenario 1

The following scenario describes an error where the yum file fails to complete, as well as steps to troubleshoot the issue.

Error Message

{{code language="none"}}
Missing Dependency: [rpm1] = [version] is needed by package [rpm2-version.arch] (installed)
{{/code}}

Description

Both rpm1 of the specified version and rpm2 are installed on the target. A newer version of rpm1 is found in the Catalog and set to be updated. The installed version of rpm1 is also a dependency to rpm2. To approve the installation of a newer rpm1, yum also needs to update rpm2. However, yum cannot find a newer version of rpm2 in repodata.tar.gz, so rpm2 is excluded from analysis.

As a new version of rpm2 is not found, the rpm is not offered an update. Because rpm2 is not updated, yum cannot allow the update of rpm1. An error is logged, alerting that rpm1 needs to remain installed to preserve the dependency of rpm2.

Troubleshooting

To troubleshoot this error, follow these steps:

  1. Validate that rpm2 is missing from the catalog.
  2. If rpm2 is missing from the Catalog, check if it exists in the RHN Channel.
    • If rpm2 is not available in the RHN Channel, it means that the analysis has executed successfully. You can try either of the following to resolve this issue:
      • Although BMC recommends downloading patches only from RHN channels, you may try to raise a request to Red Hat for the missing patch or try to download it from a third-party vendor. You can then use the missing patch to create an offline catalog and update rpm2.
      • You can exclude Rpm1 from the analysis.
        Note that another rpm might require the newer version of the excluded rpm.
      • Uninstall rpm2.
        When you uninstall rpm2, consult your administrator and use caution.
    • If present in RHN Channel, run the Catalog Update Job again.
      • If rpm2 is still not in the catalog, and this is not an RBAC-related issue, then collect logs and contact BMC Support.
      • If rpm2 is now present in the catalog, run the analysis again.
        If Analysis still shows the same error, continue to the next step .
  3. If rpm2 is present in the catalog, check whether rpm2 is present in repodata.tar.gz on the target by running the following command:
    # cd <staging>/LinuxCatalog_XXX_[target]/
    # yum -C -c yum.conf search [rpm2]

    Proceed according to the results that you obtain:
    • If rpm2 is not found, then this could be why it is not offered during Analysis.
    • If rpm2 is found, collect logs and contact BMC Support.

Logs to collect

Log files to collect from the application server

Patch Analysis Job log

Log files to collect from the target
analysis bundle.log (including repodata.tar.gz)

 

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

BMC Server Automation 8.3