Description of problem:
The text 'GLobal HTTP Capsule' is strange to read. It shall be 'Global HTTP Proxy' and not being part of the Proxy->Capsule replacements.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Edit repository in UI
2. Look at the option names below 'Sync Settings' and search for the http proxy
There is 'Ignore Global HTTP Capsule'
It shall be ;Ignore Global HTTP Proxy'
Bug 1657302 - HTTP Proxies option called "HTTP Capsules" in menus.
Still not fixed in 6.5
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
In 6.6 the check box title is now:
Ignore Global HTTP Proxy
[root@dhcp-3-191 ~]# rpm -q tfm-rubygem-foreman_theme_satellite
[root@dhcp-3-191 ~]# rpm -q satellite
6.7 there is a menu called "HTTP Proxy" and all the options do not mention Capsule
[root@dhcp-3-165 ~]# rpm -q tfm-rubygem-foreman_theme_satellite
[root@dhcp-3-165 ~]# rpm -q satellite
Checked on Sat 6.7 Snap 15 (tfm-rubygem-foreman_theme_satellite-22.214.171.124-1.el7sat.noarch). The configuration menu for repo HTTP proxy has following items:
- Global Default
- No HTTP Proxy
- Use specific HTTP Proxy
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.