Bug 207281

Summary: bad anaconda-base-200609190431.i386.repo repo
Product: [Fedora] Fedora Reporter: Steve Dickson <steved>
Component: anacondaAssignee: Peter Jones <pjones>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: nobody+pnasrat, triage
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: bzcl34nup
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-24 12:51:06 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:
Attachments:
Description Flags
the corrupted repo none

Description Steve Dickson 2006-09-20 13:53:13 UTC
Description of problem:
Yum fails due to corrupt repo


Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. yum -y update
2.
3.
  
Actual results:
Deprecated constant TYPE_INTERFACE during plugin initialization.
Please use TYPE_INTERACTIVE instead.
Loading "installonlyn" plugin
Repository 'anaconda-base-200609190431.i386' is missing name in configuration,
using id
Setting up Update Process
Setting up repositories
file:///mnt/source/./repodata/repomd.xml: [Errno 5] OSError: [Errno 2] No such
file or directory: '/mnt/source/./repodata/repomd.xml'
Trying other mirror.
Error: Cannot open/read repomd.xml file for repository:
anaconda-base-200609190431.i386


Expected results:
to work... 

Additional info:
Fresh install of today's (Sept 20, 06) Rawhide

Comment 1 Steve Dickson 2006-09-20 13:53:13 UTC
Created attachment 136734 [details]
the corrupted repo

Comment 2 Paul Nasrat 2006-09-20 13:55:41 UTC
The repo conf is written out by anaconda but it should be disabled.  I'll look into.

Comment 3 Red Hat Bugzilla 2007-08-21 05:26:44 UTC
User pnasrat's account has been closed

Comment 4 Bug Zapper 2008-04-03 18:16:14 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 5 Joel Andres Granados 2008-04-24 12:51:06 UTC
I can do a yum update from a freshly installed rawhide with no error that
resembles the one described in the original comment.  Please reopen the issue if
you still see the same behavior.