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.
DescriptionElyézer Rezende
2015-02-18 12:06:36 UTC
Description of problem:
When creating a docker registry just its name is required, but having a registry without a URL is not useful. Then the URL should be required and validated during the registry creation.
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-$OS_VERSION-20150217.0
How reproducible:
Aways
Steps to Reproduce:
1. Visit Containers > Registries and click on New registry
2. Fill just the name and submit
Actual results:
The registry is created with a blank URL
Expected results:
The creation should not happen and the form should raise validation errors requiring for a valid URL.
Additional info:
Comment 2Daniel Lobato Garcia
2015-02-19 07:50:06 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/9456 has been closed
-------------
Daniel Lobato Garcia
Applied in changeset commit:foreman-docker|394e988330feccea21993256ff258d525c4abc94.
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-2015:1592