Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
1. Proposed title of this feature request
RFE satellite maintain to unset any proxy environment variable, as a pre-upgrade check
2. What is the nature and description of the request?
If the proxy environment variable is set, the installer run will fail, with the below message.
=====
# satellite-installer
Please unset the following environment variables before running the installer: http_proxy, https_proxy, ssl_cert_file, HTTP_PROXY, HTTPS_PROXY, SSL_CERT_FILE
Your system does not meet configuration criteria
=====
3. Why does the customer need this? (List the business requirements here)
Since satellite maintain takes care of end to end upgrade, it should also have an additional check to unset an environment variable along with alerting the user.
The addition of this check will ensure that we can avoid the installer execution failure and fixing a potential issue at the pre-upgrade stage.
Currently, it can be executed only on-demand [https://bugzilla.redhat.com/show_bug.cgi?id=1861256#c5]
4. How would the customer like to achieve this? (List the functional requirements here)
Additional check-in pre-upgrade to identify any proxy environment variable
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
NA
6. Is there already an existing RFE upstream or in Red Hat Bugzilla?
NA
7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5,RHEL6)?
Good to have this implemented sooner
Verified.
Tested on Satellite 6.10.0 Snap 8.0
Steps:
1. Export any environment variable from [http_proxy, https_proxy, ssl_cert_file, HTTP_PROXY, HTTPS_PROXY, SSL_CERT_FILE]
2. satellite-installer
Observations:
satellite-installer unsets system proxy and SSL environment variables only for the duration of install and sets back those in the end.
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 (Satellite 6.10 Satellite Maintenance 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/RHBA-2021:4697