Bug 540549

Summary: Python error
Product: [Fedora] Fedora Reporter: Martin Ellison <m.e>
Component: preupgradeAssignee: Seth Vidal <skvidal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-23 11:38:49 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Martin Ellison 2009-11-23 11:27:34 EST
Description of problem: preupgrade gives a python error

Version-Release number of selected component (if applicable): latest for F-11

How reproducible: occurs for me now everytime I run preupdate

Steps to Reproduce:
1. run preupdate
Actual results: run through cleanly to reboot button (then reboot and install)

Expected results: produces error messages. Skips most of preupgrade steps. Shows reboot button but on reboot anaconda does not work properly.

Additional info:

previously had run preupdate and got the not-enough-space-on-/boot message

now have 300MB on /boot but it appears not to make any difference

anaconda fails as it cannot configure network

Python error text:

unknown metadata being downloaded: metalink
Traceback (most recent call last):
  File "/usr/share/preupgrade/preupgrade-gtk.py", line 240, in on_assistant_apply
  File "/usr/share/preupgrade/preupgrade-gtk.py", line 259, in _do_main
  File "/usr/share/preupgrade/preupgrade-gtk.py", line 436, in main_preupgrade
  File "/usr/lib/python2.6/site-packages/preupgrade/__init__.py", line 130, in setup
  File "/usr/lib/python2.6/site-packages/preupgrade/__init__.py", line 328, in complete_repo_setup
    repo._grabfunc.opts.user_agent = __user_agent__
AttributeError: 'NoneType' object has no attribute 'opts'
Comment 1 seth vidal 2009-11-23 11:38:49 EST

*** This bug has been marked as a duplicate of bug 538118 ***