Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1336831

Summary:	passenger rpms appear to have mismatches between 6.1 and 6.2
Product:	Red Hat Satellite	Reporter:	Brad Buckingham <bbuckingham>
Component:	Upgrades	Assignee:	Eric Helms <ehelms>
Status:	CLOSED ERRATA	QA Contact:	Sachin Ghai <sghai>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	cwelton, sghai
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-passenger-4.0.18-22	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:24:19 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:
Bug Depends On:
Bug Blocks:	1335807

Description Brad Buckingham 2016-05-17 14:04:55 UTC

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

Comment 1 Brad Buckingham 2016-05-17 14:22:25 UTC

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

Comment 3 Sachin Ghai 2016-05-20 09:22:32 UTC

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

Comment 4 Sachin Ghai 2016-05-26 08:12:06 UTC

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

Comment 5 Bryan Kearney 2016-07-27 11:24:19 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-2016:1501