Bug 1329690 - Some repositories are never sync'd
Summary: Some repositories are never sync'd
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: Installation - RHELOSP
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ga
: 1.0
Assignee: John Matthews
QA Contact: Tasos Papaioannou
Dan Macpherson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-22 15:16 UTC by Thom Carlin
Modified: 2016-09-13 16:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-13 16:28:23 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1862 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.0 2016-09-13 20:18:48 UTC

Description Thom Carlin 2016-04-22 15:16:27 UTC 
Description of problem:

5 repositories never start sync'ing

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

TP3 RC4

How reproducible:

Just once so far

Steps to Reproduce:
1. Install QCI and TripleO ISOs
2. Log into run launch-fusor*installer
3. Deploy Openstack

Actual results:

See screenshot

Expected results:

Successful sync

Additional info:

Low severity since it only occurred once.  Logfiles to follow
Comment 2 Thom Carlin 2016-04-22 15:23:38 UTC 
Now displays all repositories as sync'd.  Sosreport being attached
Comment 4 John Matthews 2016-06-03 16:09:44 UTC 
Moving to ON_QA so we can re-test with 1.2 composes (Sat 6.2).

This BZ was originally filed on the TP3 ISO, Sat 6.1.
Comment 5 Tasos Papaioannou 2016-07-07 18:39:35 UTC 
I haven't seen this issue in QCI 1.2 at all. Moving to Verified.
Comment 11 errata-xmlrpc 2016-09-13 16:28:23 UTC 
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/RHEA-2016:1862
Note You need to log in before you can comment on or make changes to this bug.