Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( 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 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 "", 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.
Bug 1913290 - Settings "Content" page disappeared after setting the http-proxy.
Summary: Settings "Content" page disappeared after setting the http-proxy.
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Settings
Version: 6.9.0
Hardware: x86_64
OS: Linux
Target Milestone: 6.9.0
Assignee: Ondřej Pražák
QA Contact: Devendra Singh
: 1919562 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2021-01-06 13:09 UTC by Devendra Singh
Modified: 2021-04-21 13:25 UTC (History)
6 users (show)

Fixed In Version: foreman-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-04-21 13:25:01 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31603 0 Normal Closed Settings "Content" page disappeared after setting the http-proxy. 2021-02-12 06:43:10 UTC
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:25:18 UTC

Description Devendra Singh 2021-01-06 13:09:14 UTC
Description of problem: Settings "Content" page disappeared after setting the http-proxy.

Version-Release number of selected component (if applicable):
6.9 Snap7

How reproducible:

Steps to Reproduce:
1. Install new satellite
2. Configure http-proxy.
3. Go to Administrator-->Settings--> Content and select the Default HTTP Proxy.
4. Refresh the page
5- Administrator-->Settings--> Content page get disappeared 

Actual results:
Settings content page disappeared.

Expected results:
Settings content page should not be disappeared. 

Additional info:

Comment 2 Tomer Brisker 2021-01-11 06:06:14 UTC
Created redmine issue from this bug

Comment 3 Bryan Kearney 2021-01-11 14:28:12 UTC
Upstream bug assigned to oprazak

Comment 4 Bryan Kearney 2021-01-11 14:28:14 UTC
Upstream bug assigned to oprazak

Comment 5 Bryan Kearney 2021-01-13 13:27:35 UTC
Moving this bug to POST for triage into Satellite since the upstream issue has been resolved.

Comment 6 Justin Sherrill 2021-01-25 18:09:08 UTC
*** Bug 1919562 has been marked as a duplicate of this bug. ***

Comment 8 Devendra Singh 2021-01-29 08:41:22 UTC
Verified on 6.9 Snap 11.

Verification points:

1: Install the satellite with the latest snap 6.9 Snap 11.
2: Go To Infrastructure--> Http-proxies --> create new http proxy.
3- Go to Administer-> Settings -> Content -> Click on "Default HTTP Proxy" -> Set new created proxy
4- Reload the page, the "Default HTTP Proxy" gets changed with the new created proxy.

5- The content page Administer-> Settings -> Content didn't disappear after changing the proxy.
6- Verified the foreman package

# rpm -qa|grep foreman-

Comment 11 errata-xmlrpc 2021-04-21 13:25:01 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 (Moderate: Satellite 6.9 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.

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