Bug 1646741

Summary: While upgrading satellite from 6.3->6.4, satellite-installer does not perform remove_legacy_mongo step in some situations which results in error
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: UpgradesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Jitendra Yejare <jyejare>
Severity: high Docs Contact:
Priority: high    
Version: 6.4CC: ahumbe, aperotti, chrobert, cmarinea, inecas, ktordeur, mbacovsk, mmccune, mmello, pcreech, pdwyer, rbertolj, sghai, snemeth, vijsingh, zhunting
Target Milestone: 6.4.1Keywords: PrioBumpGSS, Triaged, Upgrades
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: https://projects.theforeman.org/issues/25336
Whiteboard:
Fixed In Version: katello-installer-base-3.7.0.11-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1640686 Environment:
Last Closed: 2018-12-06 22:32:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1647339    

Comment 2 Jitendra Yejare 2018-11-16 06:02:14 UTC 
Verified!

@ Satellite 6.4 snap 1


Steps:

1. Satellite 6.3 CDN installed
2. Upgrade to 6.4.1 snap 1


Observation:

1. The issue is not reproducible on the machine where it was reproducible:
yum remove -y mongodb-2* mongodb-server-2* > /dev/null 2>&1 finished successfully!
rm -rf /etc/mongod.conf /var/log/mongodb finished successfully!

2. Also, the issue with 'yum install -y -q rh-mongodb34-syspaths failed! C' is now solved.
# rpm -qa | grep syspath
rh-mongodb34-mongo-tools-syspaths-3.4.7-1.el7.x86_64
rh-mongodb34-mongodb-server-syspaths-3.4.9-1.el7.x86_64
rh-mongodb34-syspaths-3.0-14.el7.x86_64
rh-mongodb34-mongodb-syspaths-3.4.9-1.el7.x86_64
Comment 4 errata-xmlrpc 2018-12-06 22:32:53 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/RHBA-2018:3799