Bug 1874422

Summary: Hits Sync uses only old proxy setting
Product: Red Hat Satellite Reporter: Mirek Długosz <mzalewsk>
Component: RH Cloud - InventoryAssignee: Shimon Shtein <sshtein>
Status: CLOSED ERRATA QA Contact: Mirek Długosz <mzalewsk>
Severity: medium Docs Contact:
Priority: high    
Version: 6.8.0CC: ahumbe, aruzicka, jjeffers
Target Milestone: 6.8.0Keywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_rh_cloud-2.0.12 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1884006 (view as bug list) Environment:
Last Closed: 2020-10-27 13:06:41 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:

Description Mirek Długosz 2020-09-01 10:26:31 UTC
Inventory upload uses new proxy setting (Settings -> Content -> Default HTTP Proxy) by default; if it's not present, it will fall back to old setting (Settings -> General -> HTTP(S) proxy).

Insights hits sync (Configure -> Insights) uses only old setting. New proxy setting is ignored.

All network-related functionality in plugin should use the same algorithm for picking proxy - try new setting by default, and fall back to old if it's not present.


Found on:
pulp-server-2.21.2-1.el7sat.noarch
foreman-2.1.2.1-1.el7sat.noarch
katello-3.16.0-0.4.rc4.el7sat.noarch
satellite-6.8.0-1.el7sat.noarch
tfm-rubygem-foreman_rh_cloud-2.0.10-1.el7sat.noarch

Comment 1 Mirek Długosz 2020-09-01 15:01:11 UTC
Same problem in "Sync inventory status" (Configure -> Inventory upload). It only uses old setting, new proxy setting is ignored by this action.

Comment 2 Brad Buckingham 2020-09-03 12:37:26 UTC
*** Bug 1874417 has been marked as a duplicate of this bug. ***

Comment 3 Mirek Długosz 2020-10-02 12:38:21 UTC
All network-related operations (Inventory upload, Hits sync and Inventory status sync) try to use new proxy setting first (Settings -> Content -> Default HTTP Proxy). If it is not set, old setting will be used as fallback (Settings -> General -> HTTP(S) proxy). If that is not set either, proxy will not be used.


Tested on:
Satellite 6.8 snap 17
satellite-6.8.0-1.el7sat.noarch
katello-3.16.0-1.el7sat.noarch
foreman-2.1.2.17-1.el7sat.noarch
pulp-server-2.21.3-1.el7sat.noarch
tfm-rubygem-foreman_rh_cloud-2.0.12-1.el7sat.noarch

Comment 6 errata-xmlrpc 2020-10-27 13:06:41 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 (Important: Satellite 6.8 release), 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-2020:4366