Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1383511 - Update access_insights rpm to 1.0.13
Update access_insights rpm to 1.0.13
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Packaging (Show other bugs)
Unspecified
Unspecified Unspecified
medium Severity medium (vote)
: 6.2.5
: Unused
Assigned To: satellite6-bugs
jcallaha
: Triaged
Depends On:
Blocks: 1394375
  Show dependency treegraph
 
Reported: 2016-10-10 17:18 EDT by dgao
Modified: 2016-12-12 12:14 EST (History)
5 users (show)

See Also:
Fixed In Version: tfm-rubygem-foreman-redhat_access-1.0.13-1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1394375 (view as bug list)
Environment:
Last Closed: 2016-12-12 12:14:34 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2940 normal SHIPPED_LIVE Satellite 6.2.5 Async Bug Release 2016-12-12 17:08:21 EST

  None (edit)
Description dgao 2016-10-10 17:18:43 EDT
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 16:44:53 EST
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 12:14:34 EST
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.