Cause: HTTPS proxy enabled on 6.15.0
Consequence: The manifest refresh button is disabled
Result: Repo sync works, but the manifest refresh button is disabled with the message "This is disabled because no connection could be made to the upstream Manifest."
Created attachment 2015572[details]
manifest refresh button is disabled
Description of problem:
Reporting this in response to https://bugzilla.redhat.com/show_bug.cgi?id=1993917#c124 testing and discussion.
Version-Release number of selected component (if applicable):
Satellite 6.15.0
How reproducible:
Always
Steps to Reproduce:
1. Configure authenticated/un-authenticated https-proxy
2. Import manifest and enable RH repos
3. Configure setting content_default_http_proxy and http_proxy for created https proxy.
4. Update enabled repos to use specific https proxies and try sync.
5. Navigate to Content -> Subscriptions -> Manage Manifest -> Refresh
Actual results:
Repo sync works, but manifest refresh buttion is disabled with message "This is disabled because no connection could be made to the upstream Manifest."
Expected results:
Manifest refresh also works with https-proxies, like http-proxies
Additional info:
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.