This service will be undergoing non-disruptive maintenance at 07:20 UTC, 2018-12-14. It is expected to last approximately 30 minutes

Bug 236768

Summary: package retry button crashes anaconda
Product: [Fedora] Fedora Reporter: mail <mail>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-11.2.0.56-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-24 16:22:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
Anaconda Crash dump from f7t3 none

Description mail@romal.de 2007-04-17 16:00:54 UTC
Description of problem:

Anaconda is crashing when booting with kernel-param noprobe and manually
selecting the storage-drivers.

Anaconda does see the harddisk, creates the partitions, ... and then crashes.

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

devel 2007-04-17

How reproducible:

Every time.


Steps to Reproduce:
1. install rawhide with kernel param noprobe
2. 
3. 
  
Actual results:


Expected results:


Additional info:

Comment 1 mail@romal.de 2007-04-17 16:00:54 UTC
Created attachment 152829 [details]
Anaconda Crash dump from f7t3

Comment 2 Chris Lumens 2007-04-20 15:40:31 UTC
dlehman - urlgrabber appears to maintain two lists of mirrors.  One list is an
immutable list of all the mirrors, and the other is subtracted from as mirrors
are tried.  When this second list is exhausted, that's when
YumBackend.mirrorFailureCB is called.  The problem here is that we're not
repopulating the second mirror list  when the retry button is clicked, so kaboom.

Comment 3 David Lehman 2007-05-24 16:22:34 UTC
Mirror failure handling has improved as of anaconda-11.2.0.56-1. This specific
case is covered by these changes. Please reopen this bug if you find that the
problem persists.