Bug 572882 - The number of Devices(and MB) selected displayed incorrectly in Specialized Storage Devices
The number of Devices(and MB) selected displayed incorrectly in Specialized S...
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Chris Lumens
Fedora Extras Quality Assurance
: Reopened
: 576143 589315 (view as bug list)
Depends On:
Blocks: F13Target
  Show dependency treegraph
Reported: 2010-03-12 04:17 EST by He Rui
Modified: 2010-05-24 16:10 EDT (History)
5 users (show)

See Also:
Fixed In Version: anaconda-13.39-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-24 16:10:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
logs under /tmp/ (34.19 KB, application/x-tar)
2010-03-12 04:17 EST, He Rui
no flags Details
error1 in screen (136.00 KB, image/png)
2010-03-12 04:18 EST, He Rui
no flags Details
error2 in screen (137.01 KB, image/png)
2010-03-12 04:18 EST, He Rui
no flags Details
/tmp/* after 'updates' (47.87 KB, application/x-gzip)
2010-03-14 22:00 EDT, He Rui
no flags Details

  None (edit)
Description He Rui 2010-03-12 04:17:05 EST
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):
anaconda 13.32

How reproducible:

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.
Additional info:
Error screens are attached as well as logs under /tmp/.
Comment 1 He Rui 2010-03-12 04:18:13 EST
Created attachment 399596 [details]
error1 in screen
Comment 2 He Rui 2010-03-12 04:18:45 EST
Created attachment 399597 [details]
error2 in screen
Comment 3 Chris Lumens 2010-03-12 10:04:56 EST
Does updates=http://clumens.fedorapeople.org/568875.img fix this?
Comment 4 He Rui 2010-03-14 21:59:03 EDT
(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.
Comment 5 He Rui 2010-03-14 22:00:13 EDT
Created attachment 400095 [details]
/tmp/* after 'updates'
Comment 6 Chris Lumens 2010-03-15 15:14:45 EDT
Thanks for the explicit steps to reproduce.  Much easier to figure out exactly what's going on that way.
Comment 7 Chris Lumens 2010-03-23 10:01:34 EDT
*** Bug 576143 has been marked as a duplicate of this bug. ***
Comment 8 He Rui 2010-04-22 04:26:06 EDT
Still reproducible when testing anaconda 13.37.2 of F13 Beta
Comment 9 James Laska 2010-04-22 10:30:26 EDT
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
Comment 10 James Laska 2010-04-22 10:32:35 EDT
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.
Comment 11 Chris Lumens 2010-04-23 10:47:17 EDT
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.
Comment 12 Fedora Update System 2010-04-28 17:08:39 EDT
anaconda-13.39-1.fc13 has been submitted as an update for Fedora 13.
Comment 13 Chris Lumens 2010-05-05 16:19:33 EDT
*** Bug 589315 has been marked as a duplicate of this bug. ***
Comment 14 James Laska 2010-05-24 16:09:54 EDT
Confirmed fix in 13.42

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