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.
Created attachment 1942911[details]
altcontentsource
Description of problem:
when adding alternative content source, it is possible to save it even, if baseurl path is red, if IP address instead of fqdn is specified in path. Which is fine. However valid IP address should be a option along with fqdn.
There are deployments without DNS
Also not-having DNS as single point of failure for alternative content source, can be good practice.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1.create new content source
2.as a path https://10.37.195.233./pulp/content/ instead of https://rhui-server.example.com/pulp/content
3.next
Actual results:
Red warning appears, yet it allows to save the content source
Expected results:
Valid IP shows as green as well as valid fqdn.
Additional info:
If back button is pressed, and than again next, red warning does not appear
Clarification: the red flag is not due to the IP address, it's due to the extra '/' at the end. We don't validate anything other than that http or https is there and that at the end there us /pulp/content.
The main issue is that we allow the user to continue if the URL is malformed. If this is fixed, the issue around returning to the page to see the red flag is missing will also be fixed.
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 (Important: Satellite 6.13 Release), 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-2023:2097