Description of problem: It appears that with Satellite 6.2, the current compose may be downgrading some of the passenger-related rpms. This appears to affect upgrades from 6.1 to 6.2. The specific issues observed during the upgrade are failure to register the proxy and then access to UI/CLI. Version-Release number of selected component (if applicable): Satellite 6.2 Beta snap 11 How reproducible: Always Packages observed on a clean 6.1 install: # rpm -qa|grep passenger|sort mod_passenger-4.0.18-21.el7sat.x86_64 ruby193-rubygem-passenger-4.0.18-21.el7sat.x86_64 ruby193-rubygem-passenger-native-4.0.18-21.el7sat.x86_64 ruby193-rubygem-passenger-native-libs-4.0.18-21.el7sat.x86_64 rubygem-passenger-4.0.18-21.el7sat.x86_64 rubygem-passenger-native-4.0.18-21.el7sat.x86_64 rubygem-passenger-native-libs-4.0.18-21.el7sat.x86_64 Packages observed on a clean 6.2 install: # rpm -qa|grep passenger|sort mod_passenger-4.0.18-9.10.el7sat.x86_64 rubygem-passenger-4.0.18-9.10.el7sat.x86_64 rubygem-passenger-native-4.0.18-9.10.el7sat.x86_64 rubygem-passenger-native-libs-4.0.18-9.10.el7sat.x86_64 tfm-rubygem-passenger-4.0.18-9.10.el7sat.x86_64 tfm-rubygem-passenger-native-4.0.18-9.10.el7sat.x86_64 tfm-rubygem-passenger-native-libs-4.0.18-9.10.el7sat.x86_64 Packages observed after a 6.1 to 6.2 upgrade:# rpm -qa|grep passenger|sort mod_passenger-4.0.18-21.el7sat.x86_64 rubygem-passenger-4.0.18-21.el7sat.x86_64 rubygem-passenger-native-4.0.18-21.el7sat.x86_64 rubygem-passenger-native-libs-4.0.18-21.el7sat.x86_64 tfm-rubygem-passenger-4.0.18-9.10.el7sat.x86_64 tfm-rubygem-passenger-native-4.0.18-9.10.el7sat.x86_64 tfm-rubygem-passenger-native-libs-4.0.18-9.10.el7sat.x86_64 Note: Observe the 4.0.18-9.10 vs 4.0.18-21
Note: performing the following prior to the satellite-installer --upgrade will address the issue observed: yum downgrade mod_passenger rubygem-passenger rubygem-passenger-native rubygem-passenger-native-libs
Yeah, I tried the given workaround in comment1 with snap12 and this addresses the issue related to failure on registering with the proxy. ERROR 2016-05-19 06:01:31 main] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[qe-sat6-upgrade-rhel7.satqe.lab.eng.rdu2.redhat.com]: Could not evaluate: Proxy qe-sat6-upgrade-rhel7.satqe.lab.eng.rdu2.redhat.com cannot be registered (500 Internal Server Error): N/A [ERROR 2016-05-19 06:01:32 main] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[qe-sat6-upgrade-rhel7.satqe.lab.eng.rdu2.redhat.com]: Failed to call refresh: Proxy qe-sat6-upgrade-rhel7.satqe.lab.eng.rdu2.redhat.com cannot be registered (Proxy qe-sat6-upgrade-rhel7.satqe.lab.eng.rdu2.redhat.com cannot be registered (500 Internal Server Error): N/A): N/A
Verified with upgrade from sat6.1.9 -> sat6.2 snap13.1 The issue reported with upgrade in comment3 has now been fixed with following version: [root@qe-sat6-upgrade-rhel7 ~]# rpm -qa | grep rubygem-passenger tfm-rubygem-passenger-4.0.18-22.el7sat.x86_64 rubygem-passenger-native-libs-4.0.18-22.el7sat.x86_64 tfm-rubygem-passenger-native-4.0.18-22.el7sat.x86_64 tfm-rubygem-passenger-native-libs-4.0.18-22.el7sat.x86_64 rubygem-passenger-native-4.0.18-22.el7sat.x86_64 rubygem-passenger-4.0.18-22.el7sat.x86_64
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-2016:1501