Bug 1278520 - Attempting to sync a password protected repo results in miss leading result status
Summary: Attempting to sync a password protected repo results in miss leading result s...
Keywords:
Status: CLOSED DUPLICATE of bug 1174948
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Ohad Levy
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-05 17:00 UTC by Stuart Auchterlonie
Modified: 2019-12-16 05:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-22 18:31:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2137231 0 None None None 2016-01-24 22:11:54 UTC

Description Stuart Auchterlonie 2015-11-05 17:00:10 UTC
Description of problem:

Customer has a repository (upstream hardware vendor firmware)
which is username / password protected.

The URL for the product therefore must include the username/password
in the URL.

When attempting (and failing) to sync the repo, on the sync status
page, the details component for the repository is correct, stating
"Yum Metadata: Authorization Required", whilst the Result Column
is incorrect, stating "Syncing Complete".

The sync has not completed, it has actually failed, so the result
of the sync is incorrect

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

6.1.2

How reproducible:

100% for customer

Steps to Reproduce:
1. Add a repo that needs authorization. Provide incorrect credentials
2. Sync repo.
3.

Actual results:

Sync Status details will report "Yum Metadata: Authorization Required" *CORRECT*
Sync Status result will report "Syncing Complete" *WRONG*

Expected results:

Sync Status details will report "Yum Metadata: Authorization Required"
Sync Status result will report "Syncing Failed"



Additional info:


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