Description of problem: Description of Problem: Dual boot Installation of F18 beta TC2 did not finish successfully. I have an allocated empty partition to install this pre release from dvd iso. At the installation stage the progress bar filled to the end indicating all packages were installed. Possibly among others, after "installing bootloader", installation hanged at "Configuring installed system" and won't respond for more than half an hour. I didn't think this is normal behaviour, force shut and attempt retry installation. Error popped out after clicked "reclaiming space". Guess my partition was corrupted again. Version-Release number of selected component: anaconda-18.12 Additional info: libreport version: 2.0.14 cmdline: /usr/bin/python /sbin/anaconda kernel: 3.6.0-1.fc18.x86_64 description: :The following was filed automatically by anaconda: :anaconda 18.12 exception report :Traceback (most recent call first): : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/size.py", line 79, in _parseSpec : raise ValueError("invalid size specification", spec) : File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/size.py", line 137, in __new__ : self = Decimal.__new__(cls, value=_parseSpec(spec)) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 55, in size_str : return str(Size(spec=spec)).upper() : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 128, in populate : _("%s of %s") % (size_str(freeSize), size_str(dev.size)), : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 160, in refresh : self.populate(disks) : File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 592, in on_continue_clicked : resizeDialog.refresh(disks) :ValueError: ('invalid size specification', '-186.0 mb')
Created attachment 622719 [details] File: anaconda-tb
Created attachment 622720 [details] File: product
Created attachment 622721 [details] File: type
Created attachment 622722 [details] File: ifcfg.log
Created attachment 622723 [details] File: storage.log
Created attachment 622724 [details] File: version
Created attachment 622725 [details] File: environ
Created attachment 622726 [details] File: anaconda.log
Created attachment 622727 [details] File: syslog
Created attachment 622728 [details] File: hashmarkername
Created attachment 622729 [details] File: packaging.log
Created attachment 622730 [details] File: cmdline_file
Created attachment 622731 [details] File: release
Created attachment 622732 [details] File: program.log
Sorry, I have additional information. The installation was not corrupted. As soon as I attempted to boot from local drive the F18 apparently was installed and boot normally and asked for new user creation. It seems this bug was only that installation hangs at the end and did not eject dvd gracefully to reboot, leaving me no choice but to forcefully shut down.
*** Bug 865197 has been marked as a duplicate of this bug. ***
partitioning 2 disks with previous autopart install on them, using custom live with anaconda 18.22-1 Package: anaconda-18.22-1.fc18.x86_64 OS Release: Fedora release 18
the hang-at-the-end-of-install that efreeti encountered was the known bug 862801 which we fixed a while back, but obviously, anaconda failing to correctly interpret a disk it laid out itself looks like a problem. To me this looks rather similar to https://bugzilla.redhat.com/show_bug.cgi?id=866115 , which was a similar issue for 'b' / 'B'. Proposing as a blocker, as this seems to have affected at least three configurations.
Discussed at 2012-11-05 QA meeting acting as a blocker review meeting. We were worried about several similar-looking bugs here, but dlehman believes they are several separate bugs and most of them are fixed. The case efreeti hit may well be fixed by now. bcl's may not be, but without logs from that case he cannot really fix it. In general, we don't think this is likely to be common enough with 18.22+ to merit blocker status. We can re-visit this decision if more cases emerge.
Created attachment 639791 [details] [18.26 log anaconda-tb-rXLBiG] ValueError: ('invalid size specification', '-0.4 mb') anaconda 18.26 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/size.py", line 79, in _parseSpec raise ValueError("invalid size specification", spec) File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/size.py", line 137, in __new__ self = Decimal.__new__(cls, value=_parseSpec(spec)) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 54, in size_str return str(Size(spec=spec)).upper() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 140, in populate _("%s of %s") % (size_str(freeSize), size_str(dev.size)), File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/resize.py", line 186, in refresh self.populate(disks) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 734, in on_continue_clicked resizeDialog.refresh(disks) ValueError: ('invalid size specification', '-0.4 mb') Local variables in innermost frame: m: None spec: -0.4 mb
(In reply to comment #20) > Created attachment 639791 [details] > [18.26] ValueError: ('invalid size specification', '-0.4 mb') ... This was identified as a duplicate.
Steve, do you still have the logs from this test, or can you reproduce it? If so, could you attach them? It would really help. Thanks!
Comment 20 is an attachment comment. Suggestion: Log a timestamp with the traceback itself: 22:41:26,945 anaconda 18.26 exception report ^^^^^^^^^^^^ Traceback (most recent call first): ...
Oh right, sorry, it has all the logs in it. Missed that. thanks!
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.