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.

Description of problem:
Help test for "HTTP proxy" is not correct. As of now, it stated:
~~~
Please note that these HTTP Proxy configurations are only used for requests from Satellite or Satellite plugins. System-wide Capsules must be configured at operating system level.
~~~

It should be:

~~~
Please note that these HTTP Proxy configurations are only used for requests from Satellite or Satellite plugins. System-wide proxy must be configured at operating system level.

~~~



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

6.10

How reproducible: Always

Steps to Reproduce:
1. Go to Infrastructure -> "HTTP proxy"
2. Check the help text on the page


Actual results:
It says "System-wide Capsules must be configured at operating system level."


Expected results:
It should say  "System-wide proxy must be configured at operating system level."

Additional info:

*** This bug has been marked as a duplicate of bug 1929217 ***