Bug 872012 - anaconda crashes if the thing returned when it tries to retrieve the .treeinfo file is not, in fact, a .treeinfo file
Summary: anaconda crashes if the thing returned when it tries to retrieve the .treeinf...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-01 01:08 UTC by Adam Williamson
Modified: 2012-12-20 16:23 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-20 16:23:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2012-11-01 01:08:14 UTC
This bug splits out the _original_ issue from https://bugzilla.redhat.com/show_bug.cgi?id=868558 , which we've turned into a report about the specific case of mirror list URLs.

The initial case in that bug seems to have been one where something funky happened in the selection of a mirror, and when anaconda's code to grab the .treeinfo file from the remote mirror fired, what anaconda wound up with was some random page from somewhere related to the server http://geoadserving.coffeetree.info/ . There is apparently no sanity check that what has been retrieved _actually is_ a .treeinfo file before anaconda tries to treat it as one - it just goes ahead and assumes that whatever it got was a .treeinfo file. When it does this to something that's not a .treeinfo file, it blows up prettily.

The question is exactly how to handle this better than crashing; pop up an error? What should the error say?

It's not a high priority issue because this should happen fairly rarely.

Comment 1 Fedora Update System 2012-11-08 03:34:19 UTC
anaconda-18.27-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.27-1.fc18

Comment 2 Adam Williamson 2012-11-08 04:54:22 UTC
for testing purposes, what should the fix for this do exactly? I can probably test it by faking up a repo with a bogus .treeinfo file.

Comment 3 Fedora Update System 2012-11-09 03:21:37 UTC
Package anaconda-18.27-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.27-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17823/anaconda-18.27-1.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-11-10 19:36:35 UTC
Package anaconda-18.28-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.28-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17823/anaconda-18.28-1.fc18
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2012-12-20 16:23:11 UTC
anaconda-18.28-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


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