Bug 536

Summary: Fedora 9 update repositories not usable in Anaconda
Product: Infrastructure Reporter: John Beranek <john>
Component: GeneralAssignee: Thorsten Leemhuis <fedora>
Status: RESOLVED FIXED    
Severity: major CC: lxtnow, matthias
Priority: P5    
Version: NA   
Hardware: All   
OS: GNU/Linux   
namespace:
Attachments: Anaconda error in Fedora 9 kickstart
Anaconda error in Fedora 9 kickstart - repository config

Description John Beranek 2009-04-09 12:48:48 CEST
I maintain a kickstart infrastructure, to allow automated installations of various Fedora versions.

For Fedora 9/10 we add the Rpmfusion repositories into the kickstart configuration, so that we can install rpmfusion-free-release and rpmfusion-nonfree-release.

Yesterday it was noticed that the Fedora 10 kickstart was failing, when trying to add the Rpmdfusion repositories. This was fixed by resyncing our mirror of the repo's, which downloaded only repodata changes.

Also yesterday it was noted that a Fedora 9 kickstart fell over in a similar way. I've now resynced (from download1.rpmfusion.org) 3 times over the last 12 hours, and the problem is still there.

The error in Anaconda is:

Unable to read package metadata. This may be due to a
missing repodata directory. Please ensure that your
install tree has been correctly generated.

'NoneType' object has no attribute 'cursor'

[Exit installer] [Edit] [Retry] [Continue]
Comment 1 John Beranek 2009-04-09 12:55:34 CEST
Clicking 'Edit' shows that it is trying to add the 'rpmfusion-free-updates' repository of ours, which is at the following location on our mirror server:

/sites/download1.rpmfusion.org/free/fedora/updates/9/i386/
Comment 2 Thorsten Leemhuis 2009-04-09 13:04:32 CEST
we had to disable the comps.xml creation for F9 and F10 temporary due to 
https://bugzilla.rpmfusion.org/show_bug.cgi?id=496

I guess that's the reason for your problems (albeit I would have assumed it works for F10 if the Everything repo is enabled).

Anyway, hopefully above bug can be fixed soon
Comment 3 John Beranek 2009-04-09 13:16:35 CEST
(In reply to comment #2)
> we had to disable the comps.xml creation for F9 and F10 temporary due to 
> https://bugzilla.rpmfusion.org/show_bug.cgi?id=496
> 
> I guess that's the reason for your problems (albeit I would have assumed it
> works for F10 if the Everything repo is enabled).
> 
> Anyway, hopefully above bug can be fixed soon

OK, thanks for verifying the problem - I'll just hang on tight for the fix.

While I'm here, is it expected that you can't added the Fedora 9 rpmfusion _release_ repositories into a kickstart configuration? A while ago this stopped working, so I was forced to disable the empty release repo's.
Comment 4 Thorsten Leemhuis 2009-04-10 12:10:20 CEST
(In reply to comment #3)
> (In reply to comment #2)
> > we had to disable the comps.xml creation for F9 and F10 temporary due to 
> > https://bugzilla.rpmfusion.org/show_bug.cgi?id=496

applied a different workaround which should fix this bug but might hurt those with proxys a bit...

> While I'm here, is it expected that you can't added the Fedora 9 rpmfusion
> _release_ repositories into a kickstart configuration? A while ago this stopped
> working, so I was forced to disable the empty release repo's.

Not sure, but I guess it should work -- I need a more detailed description to know what's wrong. But note, those repos are empty anyway so there is no real point in adding them.

Comment 5 John Beranek 2009-04-14 14:18:11 CEST
Hmm, that doesn't fix our kickstart here. It still produces the same error when it comes to adding the 'free-updates' and 'nonfree-updates' repositories.

Our mirror of download1.rpmfusion.org _does_ have comps.xml and comps.xml.gz though...
Comment 6 Thorsten Leemhuis 2009-04-14 14:25:31 CEST
/me confused

But whatever. I applied the real createrepo fix half an hour ago and new repodata for the updates-testing repos is uploading right now; if no problems show up over the next 24 hours I'll recreate the repodata for the main repos, Then this problem hopefully vanishes... 
Comment 7 John Beranek 2009-04-14 14:26:58 CEST
Made subject more explicit
Comment 8 John Beranek 2009-04-14 14:28:20 CEST
OK, thanks - I mid-air-collisioned changing the subject ;)
Comment 9 Thorsten Leemhuis 2009-04-15 20:39:22 CEST
Does it work now? (Note that another repo push is in progress right now)
Comment 10 John Beranek 2009-04-15 22:25:28 CEST
(In reply to comment #9)
> Does it work now? (Note that another repo push is in progress right now)
> 

Unfortunately not - still failing with the same error. I've ensured our repository was synced up too.

Turned on debug logging in Anaconda, but couldn't find any more information in the logs to help diagnose the problem. :(
Comment 11 Thorsten Leemhuis 2009-04-16 08:16:01 CEST
(In reply to comment #10)
>
> Unfortunately not - still failing with the same error. I've ensured our
> repository was synced up too.
> 
> Turned on debug logging in Anaconda, but couldn't find any more information in
> the logs to help diagnose the problem. :(

Odd. Just to get things straight: can you please post the error message once more and show how you enabled RPM Fusion in the kickstart file?

Comment 12 John Beranek 2009-04-16 13:07:01 CEST
(In reply to comment #11)
> (In reply to comment #10)
> >
> > Unfortunately not - still failing with the same error. I've ensured our
> > repository was synced up too.
> > 
> > Turned on debug logging in Anaconda, but couldn't find any more information in
> > the logs to help diagnose the problem. :(
> 
> Odd. Just to get things straight: can you please post the error message once
> more and show how you enabled RPM Fusion in the kickstart file?
> 

OK, I'll attach 2 screenshots.

The anaconda config is shown below, note how I've disabled the release repositories, as I've said they don't work when enabled and are unnecessary anyway.

## base
#repo --name=rpmfusion-free --baseurl=http://mirror.office.example.com/sites/do
wnload1.rpmfusion.org/free/fedora/releases/9/Everything/i386/os/
#repo --name=rpmfusion-nonfree --baseurl=http://mirror.office.example.com/sites
/download1.rpmfusion.org/nonfree/fedora/releases/9/Everything/i386/os/
## updates
repo --name=rpmfusion-free-updates --baseurl=http://mirror.office.example.com/sites/download1.rpmfusion.org/free/fedora/updates/9/i386/
repo --name=rpmfusion-nonfree-updates --baseurl=http://mirror.office.example.com/sites/download1.rpmfusion.org/nonfree/fedora/updates/9/i386/

Apologies for the line-wrapping.
Comment 13 John Beranek 2009-04-16 13:07:43 CEST
Created attachment 160 [details]
Anaconda error in Fedora 9 kickstart
Comment 14 John Beranek 2009-04-16 13:08:09 CEST
Created attachment 161 [details]
Anaconda error in Fedora 9 kickstart - repository config
Comment 15 Thorsten Leemhuis 2009-04-23 20:35:26 CEST
does it work right now? I ran into more problems with the latest createrepo and went back to a old one for F9 and F10; I guess that might fix this bug as well, but I have no easy way to test
Comment 16 John Beranek 2009-05-01 13:57:30 CEST
(In reply to comment #15)
> does it work right now? I ran into more problems with the latest createrepo and
> went back to a old one for F9 and F10; I guess that might fix this bug as well,
> but I have no easy way to test
> 

Sorry, for the delay - I'd implemented a workaround (rpm -ivh on the release RPMs in the %post section) so I wasn't feeling the pain.

Just did a clean kickstart with the repositories added and it's got through to installing packages. Excellent, many thanks.
Comment 17 John Beranek 2009-05-08 12:18:40 CEST
After your latest update on https://bugzilla.redhat.com/show_bug.cgi?id=494951 I guess you've moved to the updated 'createrepo'...and that's made this problem come back. :(

I've gone back to my workaround.
Comment 18 Thorsten Leemhuis 2009-05-11 21:01:53 CEST
(In reply to comment #17)
> I guess you've moved to the updated 'createrepo'...and that's made this problem
> come back. :(

Can you give it one more try please? I think I've found and worked around the last problem (yet one more yum fix I had to import as it is not yet in rawhide)
Comment 19 John Beranek 2009-05-14 22:50:36 CEST
(In reply to comment #18)
> (In reply to comment #17)
> > I guess you've moved to the updated 'createrepo'...and that's made this problem
> > come back. :(
> 
> Can you give it one more try please? I think I've found and worked around the
> last problem (yet one more yum fix I had to import as it is not yet in rawhide)
> 

Working again for me too - thanks!