Bug 1592764

Summary: yum Update from satellite 6.3.1 to 6.4 failed at dependency resolution
Product: Red Hat Satellite Reporter: Nikhil Kathole <nkathole>
Component: PackagingAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Nikhil Kathole <nkathole>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4CC: chrobert, inecas, mbacovsk, pcreech
Target Milestone: 6.4.0Keywords: Triaged, Upgrades
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: https://projects.theforeman.org/issues/24021
Whiteboard:
Fixed In Version: katello-3.7.0-3.rc1, katello-installer-base-3.7.0-1.rc1.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 18:54:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nikhil Kathole 2018-06-19 09:10:51 UTC
Description of problem: Yum update on 6.3.1 failed at dependency resolution

--> Finished Dependency Resolution
Error: rh-mongodb34-mongodb-syspaths conflicts with mongodb-2.6.11-2.el7sat.x86_64
Error: rh-mongodb34-mongodb-server-syspaths conflicts with mongodb-server-2.6.11-2.el7sat.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

# yum repolist
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
repo id                                           repo name                                                                                 status
rhel-7-server-extras-rpms/x86_64                  Red Hat Enterprise Linux 7 Server - Extras (RPMs)                                            838
rhel-7-server-rpms/x86_64                         Red Hat Enterprise Linux 7 Server (RPMs)                                                  20,501
rhel-server-rhscl-7-rpms/x86_64                   Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server                   10,023
sat6                                              satellite 6                                                                                  369
sat6-maintenance                                  Satellite 6 Maintenance                                                                       14

# yum whatprovides mongodb
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
mongodb-2.6.11-2.el7sat.x86_64 : High-performance, schema-free document-oriented database
Repo        : @rhel-7-server-satellite-6.2-rpms

# yum whatprovides mongodb-server
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
mongodb-server-2.6.11-2.el7sat.x86_64 : MongoDB server, sharding server and support scripts
Repo        : @rhel-7-server-satellite-6.2-rpms


# yum whatprovides rh-mongodb34-mongodb-syspaths
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
rh-mongodb34-mongodb-syspaths-3.4.9-1.el7.x86_64 : Convenient wrappers for the rh-mongodb34-mongodb package; replaces the mongodb package
Repo        : rhel-server-rhscl-7-rpms

Version-Release number of selected component (if applicable):
Satellite 6.4 snap 8

How reproducible: always

Steps to Reproduce:
1. yum update

Actual results: 

Yum update failed 

--> Finished Dependency Resolution
Error: rh-mongodb34-mongodb-syspaths conflicts with mongodb-2.6.11-2.el7sat.x86_64
Error: rh-mongodb34-mongodb-server-syspaths conflicts with mongodb-server-2.6.11-2.el7sat.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


Expected results: Successful yum update.


Additional info:

Comment 3 Nikhil Kathole 2018-06-26 02:58:53 UTC
VERIFIED

Version tested:
Sat 6.4 snap 9

yum update Complete!
Time taken for satellite packages update- 0:24:42
HIGHLIGHT:upgrade_logging:Time taken for satellite packages update- 0:24:42

Comment 4 Bryan Kearney 2018-10-16 18:54:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927