Bug 768069 - Net install is broken for Fedora 16
Summary: Net install is broken for Fedora 16
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-15 17:05 UTC by Scott Baker
Modified: 2011-12-15 21:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-15 21:17:52 UTC
Type: ---


Attachments (Terms of Use)
anaconda.log from a failed install (11.17 KB, text/x-log)
2011-12-15 18:40 UTC, Scott Baker
no flags Details
/tmp/syslog from a failed install (113.20 KB, application/octet-stream)
2011-12-15 18:41 UTC, Scott Baker
no flags Details

Description Scott Baker 2011-12-15 17:05:37 UTC
Description of problem:
Net install is broken right now

How reproducible:
Easy

Steps to Reproduce:
1. Try and do a net install
  
Actual results:
"Unable to read package metadata..." Looks like the repo is screwed up? It's been messed up for two days now.

Expected results:
The install completes correctly.

Additional info:

Comment 1 Chris Lumens 2011-12-15 17:56:21 UTC
Please attach /tmp/anaconda.log and /tmp/syslog to this bug report.

Comment 2 Scott Baker 2011-12-15 18:40:29 UTC
Created attachment 547429 [details]
anaconda.log from a failed install

Comment 3 Scott Baker 2011-12-15 18:41:07 UTC
Created attachment 547430 [details]
/tmp/syslog from a failed install

Comment 4 Scott Baker 2011-12-15 18:41:59 UTC
It's worth noting this exact config worked two days ago.

Comment 5 Scott Baker 2011-12-15 18:55:59 UTC
It appears the /development/16/ directory is missing from the three mirrors I checked. This looks like a mirror infrastructure thing.

Comment 6 Scott Baker 2011-12-15 21:17:52 UTC
Disregard, my kickstart file was pointing at the wrong url.


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