Created attachment 399595 [details]
logs under /tmp/
Description of problem:
'0 device(s)(0MB) selected' displayed when actually one device was selected and '-1 device(s)(-8192 MB) selected' displayed when no device selected. Please refer to the attachment.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.During f13-alpha-rc4 installation, select 'Specialized Storage Devices' and click 'next'
2.Select any device(s) and click 'next'
3.When it prompted to 'Fresh installation or Upgrade' screen, click 'back'
4.The error displayed
Note that step 2,3 is essential.
Error screens are attached as well as logs under /tmp/.
Created attachment 399596 [details]
error1 in screen
Created attachment 399597 [details]
error2 in screen
Does updates=http://clumens.fedorapeople.org/568875.img fix this?
(In reply to comment #3)
> Does updates=http://clumens.fedorapeople.org/568875.img fix this?
Thanks, but the same issue still happens.
/tmp/* is attached.
Created attachment 400095 [details]
/tmp/* after 'updates'
Thanks for the explicit steps to reproduce. Much easier to figure out exactly what's going on that way.
*** Bug 576143 has been marked as a duplicate of this bug. ***
Still reproducible when testing anaconda 13.37.2 of F13 Beta
I see this as well during the Storage Test Day (anaconda-13.37.2). The reproducer for me is ...
1) Boot a system with 1 local drive and 1 remote iSCSI drive
2) Select 1 of 2 devices
3) Click Next
4) Click Back
5) Deselect the only selected device
Observe the -1 disk count
This should get on F13Blocker or CommonBugs. I'm adding it to F13Target so that we can pull any fix in, but it currently wouldn't block the release.
Certainly would be nice to fix, but I think we can clearly articulate the cause of this failure, so worst case we'll document the issue.
Okay, this just needed to be cherry-picked over from master. I've pushed that and updated the Fixed In Version: field to reflect this.
anaconda-13.39-1.fc13 has been submitted as an update for Fedora 13.
*** Bug 589315 has been marked as a duplicate of this bug. ***
Confirmed fix in 13.42