Bug 1517734 - after changing http proxy pulp importers use old setting till service restart
Summary: after changing http proxy pulp importers use old setting till service restart
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Lukas Pramuk
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-27 10:42 UTC by Lukas Pramuk
Modified: 2019-09-26 14:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 22392 0 None None None 2018-01-23 19:09:53 UTC

Description Lukas Pramuk 2017-11-27 10:42:21 UTC
Description of problem:
After changing http proxy settings by installer the new settings are effective only in katello (cdn scan, repo enable, insights...) while in pulp (repo sync) the old settings are still in effect till next service restart.

The installer is probably missing to ensure a restart of some/all pulp services.
The issue is a regression against Sat6.2 


Version-Release number of selected component (if applicable):
Satellite 6.3 Beta

How reproducible:
deterministic

Steps to Reproduce:
1. Run installer to force SAT to communicate over http proxy
2. Trigger CDN reposet scan or repository enablement and watch traffic actually hittng http proxy
3. Trigger a repo sync and watch traffic not hitting proxy

Workaround:
4. Restart services (particularly Pulp ones)
5. Trigger a repo sync and watch traffic finally hitting proxy



Actual results:
very illusory result since only some of actions are actually using new http proxy settings

Expected results:
after installer run all actions should use new proxy http settings

Comment 3 Satellite Program 2018-01-25 17:12:36 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22392 has been resolved.

Comment 4 Lukas Pramuk 2018-02-05 13:07:58 UTC
VERIFIED.

@satellite-6.3.0-23.0.el7sat.noarch (Snap 34)
katello-installer-base-3.4.5.26-1.el7sat.noarch

by the manual reproducer described in comment#0:

1. Run installer to force SAT to communicate over http proxy
# satellite-installer --katello-proxy-url="http://proxy.example.com" --katello-proxy-port="3128" --katello-proxy-username="admin" --katello-proxy-password="pass"

2. Trigger CDN reposet scan or repository enablement and watch traffic actually hittng http proxy

3. Trigger a repo sync and watch traffic also hitting http proxy
# watch "netstat -pnt |grep :3128"
tcp        0      0 <SAT_IP>:53514       <PROXY_IP>:3128          ESTABLISHED 10114/python        
tcp        0      0 <SAT_IP>:53518       <PROXY_IP>:3128          ESTABLISHED 10114/python        
tcp        0      0 <SAT_IP>:53524       <PROXY_IP>:3128          ESTABLISHED 10114/python        
tcp        0      0 <SAT_IP>:53520       <PROXY_IP>:3128          ESTABLISHED 10114/python        
tcp        0      0 <SAT_IP>:53608       <PROXY_IP>:3128          TIME_WAIT   -                   
tcp        0      0 <SAT_IP>:53614       <PROXY_IP>:3128          TIME_WAIT   -                   
tcp        0      0 <SAT_IP>:53522       <PROXY_IP>:3128          ESTABLISHED 10114/python        
tcp        0      0 <SAT_IP>:53610       <PROXY_IP>:3128          TIME_WAIT   -                 

>>> after changing http proxy settings pulp importers use it and the extra service restart is no longer needed

Comment 5 Satellite Program 2018-02-21 16:54:17 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-2018:0336


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