Bug 1382493 - [RFE] bootstrap.py script should be aware of PROXY settings in yum.conf
Summary: [RFE] bootstrap.py script should be aware of PROXY settings in yum.conf
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Bootstrap
Version: 6.2.0
Hardware: x86_64
OS: Linux
low
low vote
Target Milestone: Unspecified
Assignee: Rich Jerrido
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-06 19:45 UTC by Reartes Guillermo
Modified: 2022-03-13 14:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 19:10:14 UTC
Target Upstream Version:


Attachments (Terms of Use)
output of bootstrap.py on a host with a proxy setting in yum.conf (2.26 KB, text/plain)
2016-10-06 19:45 UTC, Reartes Guillermo
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-8959 0 None None None 2022-03-13 14:26:30 UTC
Red Hat Knowledge Base (Solution) 3897361 0 None None None 2019-02-09 10:41:44 UTC

Description Reartes Guillermo 2016-10-06 19:45:08 UTC
Created attachment 1208029 [details]
output of bootstrap.py on a host with a proxy setting in yum.conf

Description of problem:

When a proxy is specified in yum.conf, the bootstrap.py script fails to complete.

The proxy is not needed to reach the Sat6 instance.


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

How reproducible:
tried once

Steps to Reproduce:
1. prepare a host-group, activation-key to register a rhel7
2. try to register the host to the sat6 instance via bootstrap.py (proxy is set in yum.conf)
3. bootstrap.py fails, cannot download packages.

Actual results:

bootstrap.py script fails when a proxy in yum.conf is specified. But it also fails to take action, either inform that there is an unneeded proxy is setup in yum.conf or to remove/comment the proxy setting in yum.conf.

Expected results:

detect/be aware that there is a proxy specified in yum.conf 
the proxy is not needed to reach the satellite (otherwise the bootstrap.py script would not have executed up to the point it fails).
remove the proxy setting from yum.conf (sat6 should use rhsm.conf --and normally without proxy-- ?)


Additional info:
* host was registered to a previous sat5
* host has a proxy in yum.conf (and no proxy in rhsm.conf)

* Once the proxy setting is removed, the script completes ok.

Comment 1 Rich Jerrido 2016-10-06 21:30:25 UTC
if the user has a proxy defined in yum.conf (or in /etc/sysconfig/rhn/up2date), I think a reasonable default would to 'carry over' that configuration and add it to rhsm.conf. Bootstrap.py can take a system from RHN->Sat6, Sat5->Sat6, and I cannot guarantee that a proxy that was used previously is (or isn't) still valid. 

Additionally, I can see giving the user the ability to override the defaults to set a different proxy, or no proxy at all (which in that case, we'd remove the proxy from yum.conf)

Comment 2 Bryan Kearney 2018-09-04 18:58:34 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 3 Bryan Kearney 2018-09-04 19:10:14 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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