Bug 1708295 - insights-client --display-name returns 404 when routed through satellite
Summary: insights-client --display-name returns 404 when routed through satellite
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Insights
Version: 6.3.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.6.0
Assignee: Rex White
QA Contact: Radovan Drazny
URL:
Whiteboard:
: 1708291 1708292 1708293 1708294 (view as bug list)
Depends On:
Blocks: 1708694
TreeView+ depends on / blocked
 
Reported: 2019-05-09 14:30 UTC by Jeff Needle
Modified: 2019-10-22 19:51 UTC (History)
7 users (show)

Fixed In Version: tfm-rubygem-redhat_access-2.2.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1726823 (view as bug list)
Environment:
Last Closed: 2019-10-22 19:51:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github redhataccess foreman-plugin pull 37 0 None closed Add support for proxying PATCH HTTP request 2020-04-20 15:18:59 UTC
Github redhataccess foreman-plugin pull 41 0 None closed Fixed problem with PATCH payload being converted to json (BZ1708295) 2020-04-20 15:18:59 UTC
Red Hat Knowledge Base (Solution) 4188311 0 Troubleshoot None [Satellite6] Changing display name using insights-client returns 404 if managed by Satellite6 2019-05-31 19:16:49 UTC

Description Jeff Needle 2019-05-09 14:30:43 UTC 
Description of problem:
when routed via satelltite 6.4 and 6.5 (possibly 6.3 as well) the insights-client --display-name option fails with a 404 error after the cutover to cloud.redhat.com. 

Version-Release number of selected component (if applicable):
6.3 and up

How reproducible:
100%

Steps to Reproduce:
1. insights-client --display-name=BugsInSatellitePluginFor1000Alex!
2.
3.

Actual results:
HTTP Status Code: 404 and display name not changed


Expected results:
Display name updated to BugsInSatellitePluginFor1000Alex!

Additional info:
Comment 3 Jeff Needle 2019-05-09 14:38:57 UTC 
*** Bug 1708293 has been marked as a duplicate of this bug. ***
Comment 4 Jeff Needle 2019-05-09 15:17:06 UTC 
*** Bug 1708291 has been marked as a duplicate of this bug. ***
Comment 5 Jeff Needle 2019-05-09 15:17:51 UTC 
*** Bug 1708292 has been marked as a duplicate of this bug. ***
Comment 6 Jeff Needle 2019-05-09 15:18:37 UTC 
*** Bug 1708294 has been marked as a duplicate of this bug. ***
Comment 7 Lindani Phiri 2019-05-09 16:40:00 UTC 
Fix for this issue is available in this PR : https://github.com/redhataccess/foreman-plugin/pull/37
Comment 11 Peter Vreman 2019-06-04 15:58:40 UTC 
With egg 3.0.102 it works again also on Sat6.2 and Sat6.5
Comment 12 Radovan Drazny 2019-06-26 11:26:58 UTC 
Tested with tfm-rubygem-redhat_access-2.2.6-1.el7sat.noarch and Satellite 6.6 Snap 7

[root@rhel7-client ~]# insights-client --register
You successfully registered a0449649-5088-4206-b2ca-cd010518cb3b to account 5779551.
Successfully registered host rhel7-client.example.com
Automatic scheduling for Insights has been enabled.
Starting to collect Insights data for rhel7-client.example.com
Uploading Insights data.
Successfully uploaded report from rhel7-client.example.com to account 5779551.
[root@rhel7-client ~]# insights-client --status                                                                                                                                                                                      
System is registered locally via .registered file. Registered at 2019-06-26T13:08:39.079251
Insights API confirms registration.
# insights-client --display-name='WhatIsABug?'
System display name changed from BugsInSatellitePluginFor1000Alex to WhatIsABug?

The system is now displayed under Insights -> Inventory with the new name.

VERIFIED
Comment 15 Bryan Kearney 2019-10-22 19:51:42 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/RHSA-2019:3172
Note You need to log in before you can comment on or make changes to this bug.