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 1229290 - Syncing a repo with incorrect URL raises error under details but sync_status shouldn't be 'Sync Complete'
Summary: Syncing a repo with incorrect URL raises error under details but sync_status ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact: Sachin Ghai
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-08 11:50 UTC by Sachin Ghai
Modified: 2019-09-26 17:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-25 18:19:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
sync status shown as sync_complete but actual sync doesn't happen because of incorrect URL (25.19 KB, image/png)
2015-06-08 11:50 UTC, Sachin Ghai
no flags Details
when sync_is _not succeeded because of incorrect URL, then status should not be 'success' (49.85 KB, image/png)
2015-06-08 11:57 UTC, Sachin Ghai
no flags Details
Fixed in 6.2 (96.83 KB, image/png)
2016-08-25 18:19 UTC, John Mitsch
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16185 0 None None None 2016-08-18 19:02:03 UTC

Description Sachin Ghai 2015-06-08 11:50:28 UTC
Created attachment 1036326 [details]
sync status shown as sync_complete but actual sync doesn't happen because of incorrect URL

Description of problem:

On Syncing a repo with incorrect URL raises "Yum Metadata: Not Found" under sync_status page under 'Details'.

And result is: Sync Complete'. Please see the screenshot

Version-Release number of selected component (if applicable):
sat6.1 GA snap7

How reproducible:
always

Steps to Reproduce:
1. sync a repo with incorrect URL or URL that doesn't exist
2.
3.

Actual results:
Sync status: "Sync Complete"

Expected results:
status shouldn't be Sync_Complete. Its misleading

Additional info:

Comment 2 Sachin Ghai 2015-06-08 11:57:13 UTC
Created attachment 1036328 [details]
when sync_is _not succeeded because of incorrect URL, then status should not be 'success'

Comment 5 Bryan Kearney 2016-08-04 20:12:55 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 6 John Mitsch 2016-08-18 18:54:48 UTC
Created redmine issue http://projects.theforeman.org/issues/16185 from this bug

Comment 7 John Mitsch 2016-08-25 18:12:58 UTC
Looks like this has been fixed in 6.2.0

Using satellite-6.2.0-21.1.el7sat.noarch

When trying to sync a repo with an invalid URL, the sync status page is showing "Sync Incomplete". here is a screenshot http://imgur.com/a/miR43 

This is the result I would expect.

Comment 8 John Mitsch 2016-08-25 18:19:16 UTC
Created attachment 1194077 [details]
Fixed in 6.2


Note You need to log in before you can comment on or make changes to this bug.