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.
Environment: Satellite 6.14
Problem:
The concern stems from the BZ https://bugzilla.redhat.com/show_bug.cgi?id=2275964 and it's RCA which can be found in https://bugzilla.redhat.com/show_bug.cgi?id=2275964#c5 .
Now, It's clear that, when The SmartProxy name is smartproxy.example.com but the URL is https://cname-smartproxy.example.com:9090, That change in the URL can affect many things i.e.
* Selection of content source during registration
* Change of Published At URLs for all the Pulp repos
* Communication to stop working with the SmartProxy when the URL is wrong\unreachable
etc ..
One may not immediately be able to notice or identify the reason as they will look at the name of SmartProxy and that may seem fine but in fact, the URL is different. The fact that We can keep the name and URL both different, is itself a generator of inconsistency here.
Solution proposed:
For the SmartProxy Object:
* It should have the option to define the name
* It should have an option to define protocol [ HTTPS is default ]
* It should have an option to define port [ 9090 is default ]
* The URL should be formed automatically based on the three selections above.
* If the name is updated, The same should be reflected in the URL on its own.
In that way:
* We only need to deal with just the name change and the change can be easily identified
* That would be reflected automatically for the URL as well
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.