Bug 1276676 - Red Hat Insights Proxy for CFME throws exception when creating report subsets
Red Hat Insights Proxy for CFME throws exception when creating report subsets
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: rubygem-foreman-redhat_access (Show other bugs)
6.1.3
Unspecified Unspecified
high Severity high (vote)
: 6.1.5
: --
Assigned To: Lindani Phiri
Anisha Narang
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-30 09:14 EDT by Lindani Phiri
Modified: 2017-02-23 14:43 EST (History)
3 users (show)

See Also:
Fixed In Version: rubygem-foreman-redhat_access-0.2.4-1, rubygem-redhat_access_lib-0.0.6-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-15 04:20:20 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)

  None (edit)
Description Lindani Phiri 2015-10-30 09:14:08 EDT
Description of problem:
A CloudForms appliance registered to a Satellite should be able to use Satellite as a proxy to get Insights reports and registered system lists.
This does not work as ( a HTTP 400 bad request is returned when attempting to create a report subset).
Comment 4 Anisha Narang 2015-12-08 10:15:23 EST
Can view the registered system lists and Insights reports on a Cloudforms appliance registered to a satellite, satellite is behaving as a proxy.

Verified with redhat-access-insights client rpm version: 1.0.5 on rhel 67 machine,
http://download.devel.redhat.com/brewroot/packages/ruby193-rubygem-foreman-redhat_access/0.2.4/1.el7sat/noarch/ruby193-rubygem-foreman-redhat_access-0.2.4-1.el7sat.noarch.rpm
http://download.devel.redhat.com/brewroot/packages/ruby193-rubygem-redhat_access_lib/0.0.6/1.el7sat/noarch/ruby193-rubygem-redhat_access_lib-0.0.6-1.el7sat.noarch.rpm
Comment 6 errata-xmlrpc 2015-12-15 04:20:20 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/RHSA-2015:2622

Note You need to log in before you can comment on or make changes to this bug.