Description of problem: Start installer from rawhide boot.iso. Click Installation Destination. Click Done. Version-Release number of selected component: anaconda-20.6-1 The following was filed automatically by anaconda: anaconda 20.6-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/size.py", line 136, in __new__ raise SizeNotPositiveError("bytes= param must be >=0") File "/usr/lib/python2.7/site-packages/blivet/size.py", line 155, in __radd__ return Size(bytes=Decimal.__radd__(self, other, context=context)) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 177, in _get_sw_needs_text "total": required_space_text + auto_swap, File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 239, in refresh sw_text = self._get_sw_needs_text(required_space, auto_swap) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 848, in on_back_clicked self.encrypted) SizeNotPositiveError: bytes= param must be >=0 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x20rawhide\x20x86_64 quiet BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.0-0.rc5.git2.1.fc20.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: rawhide
Created attachment 787130 [details] File: anaconda-tb
Created attachment 787131 [details] File: anaconda.log
Created attachment 787132 [details] File: environ
Created attachment 787133 [details] File: lsblk_output
Created attachment 787134 [details] File: nmcli_dev_list
Created attachment 787135 [details] File: os_info
Created attachment 787136 [details] File: program.log
Created attachment 787137 [details] File: storage.log
Created attachment 787138 [details] File: syslog
Created attachment 787139 [details] File: ifcfg.log
Created attachment 787140 [details] File: packaging.log
Tested with: $ qemu-kvm -m 4096 -hda f18-test-2.img -cdrom ~/xfr/fedora/rawhide/boot.iso -vga std -boot menu=on The rawhide boot.iso does not have a version number, so these are a substitute: $ file boot.iso boot.iso: # ISO 9660 CD-ROM filesystem data 'Fedora rawhide x86_64 ' (bootable) $ sha256sum boot.iso 1e9b4df158d51dcdf8f245c1a0eba4aa190e044e7d296e5df3eacbcc05ebcbe7 boot.iso $ isoinfo -lR -i boot.iso | egrep 'vmlinuz|squashfs' -rwxr-xr-x 2 0 0 5653880 Aug 14 2013 [ 31326 00] vmlinuz -rw-r--r-- 1 0 0 222838784 Aug 15 2013 [ 49515 00] squashfs.img -rwxr-xr-x 2 0 0 5653880 Aug 14 2013 [ 31326 00] vmlinuz $ file boot-loop/isolinux/vmlinuz boot-loop/isolinux/vmlinuz: Linux kernel x86 boot executable bzImage, version 3.11.0-0.rc5.git2.1.fc20.x86_64 (mockbuild.fedor, RO-rootFS, swap_dev 0x5, Normal VGA
Built a live image with today's Rawhide packages, booted it, went through gnome-initial-setup (which is a bug itself - #998083), then run 'sudo liveinst', completed language selection, and tried to do disk selection. Crash occurred at that point IIRC. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.utf8 cmdline_file: initrd=initrd0.img root=live:CDLABEL=20130816-desktop-x86_64 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 slub_debug=- BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 3.11.0-0.rc5.git3.1.fc20.x86_64 other involved packages: python-blivet-0.19-1.fc20.noarch package: anaconda-20.6-1.fc20.x86_64 packaging.log: product: Fedora reason: SizeNotPositiveError: bytes= param must be >=0 release: Fedora release 20 (Rawhide) version: rawhide
This appears to be a showstopper that's hit two people at least. Nominating as an Alpha blocker.
Error occurred after confirming custom partititioning with ``DONE''. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.utf8 cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-20-Nightly-x86_64-Live-de rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 3.11.0-0.rc5.git3.1.fc20.x86_64 other involved packages: python-blivet-0.19-1.fc20.noarch package: anaconda-20.6-1.fc20.x86_64 packaging.log: product: Fedora reason: SizeNotPositiveError: bytes= param must be >=0 release: Fedora release 20 (Rawhide) version: rawhide
Created attachment 788148 [details] proposed patch: drop unneeded variable required_space_text It would be helpful if someone could apply this and test it.
With the patch applied, I get Installation Options, after clicking Done in Installation Destination, instead of a SizeNotPositiveError exception. The next problem is that after clicking Custom Partitioning, I get an all-white screen instead of the Custom Partitioning dialog. There is no anaconda-tb-* file, however. This could be related to my choice of initial disk configuration ... will retest with a default, msdos-labeled disk configuration. Tested with: A pre-partitioned GPT disk image. $ qemu-kvm -m 8192 -hda f19-test-3.img -cdrom ~/xfr/fedora/nightly-composes/Fedora-20-Nightly-x86_64-Live-desktop-20130816.11-1.iso -vga std -boot menu=on
Confirming that the patch fixes this bug. Procedure: $ qemu-img create f20-test-1.img 12G Do a minimal F19 install with default storage configuration. $ qemu-kvm -m 8192 -hda f20-test-1.img -cdrom ~/xfr/fedora/nightly-composes/Fedora-20-Nightly-x86_64-Live-desktop-20130816.11-1.iso -vga std -boot menu=on Start patched anaconda-20.6-1 installer. Click Installation Destination. Installation Destination dialog is displayed. Click Done. The SizeNotPositiveError exception does not occur here. Installation Options dialog is displayed. What follows appears to be a different bug: Click Cancel ... Click Done. Click Reclaim Space. Reclaim Disk Space dialog is displayed. Click Cancel. Click Done. Click Custom partitioning. Installation Summary is unexpectedly displayed with all elements grayed. The pointer is responsive, but no links respond to clicks, and no tooltips are displayed. From a terminal, it can be seen that there is no anaconda-tb-* in /tmp. Attaching to anaconda with strace shows the it is rapidly receiving repeated SIGSEGVs.
(In reply to Steve Tyler from comment #18) ... > What follows appears to be a different bug: ... Bug 998687 - SIGSEGV storm instead of Manual Partitioning
Discussed at 2013-08-21 blocker review meeting [1]. This is accepted as an Alpha blocker, because it violates the following F20 alpha release criterion: "The installer must be able to complete an installation to a single disk using automatic partitioning." [2] [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-08-21/ [2] https://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria#Disk_layouts
*** Bug 1000914 has been marked as a duplicate of this bug. ***
I'm pretty sure this should be marked fixed at this point.
reported this bug in bugzilla from CD of netinstall Alpha TC-4 but do not see the entries.....fails at reclaim disk. (Bugzilla found this bug number)
(In reply to satellit from comment #23) > reported this bug in bugzilla from CD of netinstall Alpha TC-4 but do not > see the entries.....fails at reclaim disk. (Bugzilla found this bug number) Thanks for your report. Reopening. The bug was closed, so no comments for dupes are appended. Could you attach /tmp/anaconda-tb, if possible?
I was trying to reclaim space on my existing hard disk partition and when I did a "delete all", I ran into this crash. Screencast link will be attached. cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Scientific-KDE-x86_6 rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 hashmarkername: anaconda kernel: 3.11.0-3.fc20.x86_64 other involved packages: python-blivet-0.20-1.fc20.noarch package: anaconda-20.10-2.fc20.x86_64 packaging.log: product: Fedora reason: SizeNotPositiveError: spec= param must be >=0 release: Fedora release 20 (Null) version: 20
(In reply to Amit Saha from comment #25) > I was trying to reclaim space on my existing hard disk partition and when I > did a "delete all", I ran into this crash. > > Screencast link will be attached. http://www.youtube.com/watch?v=isHmVG2sRzw I was attempting to installed Fedora 20 TC4.
Does reclaim fits Alpha criteria with automatic partitioning? Even as referenced, just rewriting existing data should be enough for Alpha.
Please, someone who is still seeing this crash, attach the /tmp/anaconda-tb-* file. It is impossible to fix this without it.
I'm having a lot of trouble reproducing this. Following the video listed in c#26, I created a vm with a 70G disk and have been using the F20 alpha TC4 x64 KDE live. Even following the steps shown in the video almost verbatim (down to deselecting and reselecting the install target disk), I can't get anything to crash - the install proceeds without issue. I'll do a few more installs but I'm sceptical that I'm going to get a repo here.
Created attachment 795781 [details] Anaconda traceback with TC5 This is the requested file with TC5 while attempting to delete all partitions
I can't reproduce it too. I followed the video from comment 26 but I had no luck. I tested it on bare metal and on virtual machine.
Given that most people cannot reproduce this, it may be that there is something specific to Amit's disk layout that is triggering the crash. It may be worth noting that the crash is in signal handler code that's triggered when the user moves the resize slider. (Yes -- I realize that the resize slider does not even appear in the reproducer video.)
started install with F20 alpha RC1 x86_64 DVD burned to a USB stick using livecd-iso-to-disk and booted with EFI. I selected a disk, and standard partition autopart. After selecting "delete all" on the existing partitions, I got the crash after clicking on "reclaim space" cmdline: /usr/bin/python /sbin/anaconda cmdline_file: BOOT_IMAGE=/syslinux/vmlinuz inst.stage2=hd:UUID=5F18-9593 quiet hashmarkername: anaconda kernel: 3.11.0-300.fc20.x86_64 package: anaconda-20.14-1 product: Fedora reason: SizeNotPositiveError: spec= param must be >=0 release: Cannot get release name. version: 20-Alpha
anaconda-20.15-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.15-1.fc20
I re-confirmed that I could reproduce this bug with F20 alpha RC1 (anaconda-20.14-1.fc20) before attempting an install with F20 alpha RC2 (anaconda-20.15-1.fc20). Confirmed that the fix works, moving to VERIFIED
anaconda-20.16-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.16-1.fc20
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
Guest has W7 default install, i tried to install F20a RC2 to test dualboot. Tried to reclaim space with automatic partitioning (default scheme: lvm) and set the partition to resize. Anaconda crashed immediately. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Alpha\x20x86_64 quiet BOOT_IMAGE=vmlinuz hashmarkername: anaconda kernel: 3.11.0-300.fc20.x86_64 package: anaconda-20.15-1 product: Fedora reason: SizeNotPositiveError: spec= param must be >=0 release: Cannot get release name. version: 20-Alpha
Created attachment 798366 [details] anaconda-tb-*
anaconda-20.17-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.17-1.fc20
Installed Fedora 20 Scientific Alpha RC3 and performed the "Delete all" operation to reclaim space. No crash. Worked as expected.
I re-tested (Comment #38) with F20a RC3 and Anaconda did not crash. The re-size operation with automatic partitioning ended ok.
anaconda-20.17-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.