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.
DescriptionBrad Buckingham
2021-10-08 17:59:30 UTC
Description of problem:
There is currently a bugzilla for Satellite 6.10 (bug 1993917) that results in the Satellite not supporting a proxy that has been defined with an HTTPS URL.
Work has been done to resolve it; however, it will not be available for the Satellite 6.10 GA. As a result, we need to provide a mechanism to support users with that configuration.
For those users, the plan is to document a post-upgrade procedure that will allow the user to support HTTPS proxies.
Since this procedure will require additional steps by the user, we want to have a foreman-maintain check that identifies if there are any 'HTTP Proxies' configured for HTTPS and if so,
- pause the upgrade
- warn the user that they have an HTTPS proxy defined (this could include listing the proxies e.g. id/name/url)
- allow the user to continue or cancel the upgrade
Note: at a minimum, a KCS will be created to document the procedures as well as a reference to it from the Release Notes. As of this time, those procedures must be done after the upgrade is completed.
Version-Release number of selected component (if applicable):
6.10
Verified.
Tested on Satellite 6.9.7 Snap 1.0
Version: rubygem-foreman_maintain-0.8.20-1.el7sat.noarch (From Satellite 6.10 Snap 24)
Setup:
1. Create HTTP Proxy with HTTPS URL (Infrastructure > Http Proxies)
Steps:
1. foreman-maintain upgrade check --target-version 6.10
Observation:
Check `https_proxies` added to 6.10 upgrade scenarios, which detects/queries DB for http_proxies with https:// in http_proxies.url, then shows users a proxy name with suggested KCS in pre-upgrade check, and asks for confirmation to proceed as a question, Not as a warning.
As this check covers upgrades, can we add the same in release notes/docs for new installs of Satellite 6.10.0?
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