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 805177 - URL Validation at Sync Time could be issue
Summary: URL Validation at Sync Time could be issue
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Jason E. Rist
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-20 16:06 UTC by Jason E. Rist
Modified: 2013-08-16 18:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-10 23:12:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jason E. Rist 2012-03-20 16:06:28 UTC 
Description of problem: Add   repo does not test to verify that you have given valid repo URL -   this   is only done at sync time, and if the sync fails you do not get   an   obvious indication of why



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


How reproducible: Always


Steps to Reproduce:
1. Custom product
2. Add Repo
3. Enter a wrong URL
4. Sync
  
Actual results: fails.


Expected results: doesn't let you sync? validates at save time?


Additional info:
Comment 2 Mike McCune 2012-05-10 23:12:18 UTC 
Problem is, people may want to setup repos even when they are not available or are in the process of being created.

I think we should just leave this at sync time to validate.
Comment 3 Mike McCune 2013-08-16 18:11:56 UTC 
getting rid of 6.0.0 version since that doesn't exist
Note You need to log in before you can comment on or make changes to this bug.