Bug 474630

Summary: no updates-newkey in F10
Product: [Fedora] Fedora Reporter: David Juran <djuran>
Component: revisorAssignee: Jeroen van Meeuwen <vanmeeuwen+fedora>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: jonathansteffan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-12-05 03:00:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Juran 2008-12-04 18:03:30 UTC 
Description of problem:
The configuration files for Fedora 10 e.g. /etc/revisor/conf.d/revisor-f10-i386.conf contains references to updates-newkey i.e. sections like 

[updates-newkey]
name=Fedora 10 - i386 - Updates Newkey
baseurl=http://localrepo/fedora/updates/10/i386.newkey/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f10.newkey&arch=i386
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-8-and-10-i386

Since such directories (fortunately) don't exit, revisor fails with the rather cryptic message:

Fatal Error: Unable to retrieve software information.
        This could be caused by one of the following:
         - not having a network connection available,
         - Server refusing connections,
         - Using a mirror that isn't fully synchronized,
         - Misconfigured repositories.


Version-Release number of selected component (if applicable):
revisor-2.1.3-1.fc10

How reproducible:
Every time

Steps to Reproduce:
1. revisor --kickstart=/usr/share/spin-kickstarts/fedora-livedvd-games.ks  --mode=f10-i386 --live-optical
Comment 1 Jeroen van Meeuwen 2008-12-05 03:00:40 UTC 
Fixed in GIT: http://git.fedorahosted.org/git/?p=revisor;a=commitdiff;h=64935726f496ba38507a852174873f97e75b5193

Pending next release
Comment 2 Jeroen van Meeuwen 2008-12-05 03:01:33 UTC 
(In reply to comment #0)
> Since such directories (fortunately) don't exit, revisor fails with the rather
> cryptic message:
> 
> Fatal Error: Unable to retrieve software information.
>         This could be caused by one of the following:
>          - not having a network connection available,
>          - Server refusing connections,
>          - Using a mirror that isn't fully synchronized,
>          - Misconfigured repositories.
> 
> 

FWIW, any recommendations on the error message?
Comment 3 David Juran 2008-12-05 12:42:28 UTC 
In hindsight, the error message _was_ quite accurate (i.e Misconfigured repositories)  But it got me checking and re-checking my proxy configuration and it took a tcpdump for me to realise that it was actually the repository that was wrong. Maybe if revisor could output the yum error verbatim, at least when upping the debug level, it would become clearer.

Nevertheless, I guess this is a discussion better suited for a mailing list, thanks for fixing the repository issue.