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.

Bug 1777306

Summary: Correct "Default http Capsule => Default Http Proxy" and "Http Capsule Policy" to "Http Proxy Policy" and "Manage Http Capsule" => "Manage Http Proxy"
Product: Red Hat Satellite Reporter: vijsingh
Component: BrandingAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Jameer Pathan <jpathan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: inecas, jjeffers, pcreech, sghai, sshtein
Target Milestone: 6.7.0Keywords: AutomationBlocker, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_theme_satellite-5.0.1.7-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:27:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1774324    

Description vijsingh 2019-11-27 11:16:08 UTC
Description of problem:
Correct "Default http Capsule => Default Http Proxy" and "Http Capsule Policy" to "Http Proxy Policy" and  "Manage Http Capsule" => "Manage Http Proxy"

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

@Satellite 6.7.0 snap 3.0

How reproducible:

Always

Steps to Reproduce:
Correct "Default http Capsule => Default Http Proxy" and "Http Capsule Policy" to "Http Proxy Policy" and  "Manage Http Capsule" => "Manage Http Proxy" ..

1. Administer => Settings => Content => See "Default http Capsule"
2. Content => Product => Drag/Drop 'Select Action' => See "Manage Http Capsule"
3. Content => Product => Drag/Drop 'Select Action' => 'Manage Http Capsule' => See "Http Capsule Policy"


Additional info:

Related to 'Content Management: HTTP Proxy Updates for Repositories'

Comment 3 vijsingh 2019-11-27 11:47:54 UTC
Correction require at below path too:

4. Change 'Http Capsule' => 'Http Proxy' at below path:

   Content => Product => Select Product => Create Repository => Select Type 'Yum' =>  Under "Http Capsule Policy" Select 'Use Specific Http Proxy' => See 'HTTP Policy'
 
5. Change "Http Capsule Policy" => 'Http Proxy Policy':

  Content => Product => Select Product => Create Repository => Select Type 'Yum' =>  Now see "Http Capsule Policy"

Comment 5 James Jeffers 2019-12-05 19:45:02 UTC
This appears to be correct on upstream 3.13.x, so perhaps the issue is introduced during the satellite theme process?

Comment 9 Jameer Pathan 2020-01-21 06:38:12 UTC
Verified:

Verified with:
- Satellite 6.7.0 snap 9

Observation:
- All naming issues related to Http proxy feature seems to be resolved.

Comment 12 errata-xmlrpc 2020-04-14 13:27:30 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, 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/RHSA-2020:1454