Bug 1383511 - Update access_insights rpm to 1.0.13
Summary: Update access_insights rpm to 1.0.13
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: jcallaha
URL:
Whiteboard:
Depends On:
Blocks: 1394375
TreeView+ depends on / blocked
 
Reported: 2016-10-10 21:18 UTC by dgao
Modified: 2019-09-25 21:20 UTC (History)
5 users (show)

Fixed In Version: tfm-rubygem-foreman-redhat_access-1.0.13-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1394375 (view as bug list)
Environment:
Last Closed: 2016-12-12 17:14:34 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2940 0 normal SHIPPED_LIVE Satellite 6.2.5 Async Bug Release 2016-12-12 22:08:21 UTC

Description dgao 2016-10-10 21:18:43 UTC 
Recently we've encountered a bz regarding access_insights returning an "500 Internal Server Error" when attempting to register from a RHV deployment. Below is the bugzilla link on the specific issue:

https://bugzilla.redhat.com/show_bug.cgi?id=1367762

Speaking with lphiri, he informed us that this issue was resolved in v1.0.13 of access_insights. Can we have the updated rpms included in the next Satellite 6.2.x release so QCI can consume it downstream?
Comment 2 jcallaha 2016-11-30 21:44:53 UTC 
Verified in Satellite 6.2.5

# rpm -qa | grep access
tfm-rubygem-foreman-redhat_access-1.0.13-1.el7sat.noarch

# rpm -qa | grep access
tfm-rubygem-foreman-redhat_access-1.0.13-1.el6sat.noarch
Comment 3 errata-xmlrpc 2016-12-12 17:14:34 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:2940
Note You need to log in before you can comment on or make changes to this bug.