Yum failed to complete - Scenario 3

Error Message

Description

Rpm2 is installed on the target, while rpm1 is not. Yum attempts to offer rpm1 to be installed or updated, but then yum detects that some of the files to be updated by rpm1 are used by rpm2. Therefore, yum rejects the installation or update of rpm1. An error is logged, alerting that rpm1 cannot be installed. In general, the conflict suggests that rpm1 and rpm2 cannot coexist if rpm versions matter.

Troubleshooting

1. Check the RHN site for known conflict issues.
   A conflict may arise if either rpm1 or rpm2 are not in the repository.
2. Validate that the rpm is in RHN channel, in the Catalog, and in repodata.tar.gz, as described in scenario 2.
   Note that resolution cannot be guaranteed if the RPMs come from different channels.
3. Proceed according to your needs:
   • If rpm1 must be installed, check whether rpm2 can be uninstalled, downgraded, or upgraded to a non-conflicting version.
   • If rpm2 must be preserved, consider the following actions:
     • Check whether rpm1 can be excluded. Note that another rpm might require the newer version of the excluded rpm.
     • Check whether another non-conflicting version of rpm1 can be installed.
     • Check whether multiple versions of rpm2 are installed, where the conflicting one can be uninstalled.
4. If the previous steps do not resolve the problem, collect logs and contact BMC Support.

Logs to collect

• analysis bundle.log (including repodata.tar.gz)
• rpm –qa