Bug 853636
Summary: | poor checking of storage config against software set space needs | ||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Flóki Pálsson <flokip> | ||||||||||||||||||||||||||||||||||||||||||||||||
Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||||||||||||||||||||||||||||||||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||||||||||||||||||||||||||||
Version: | 18 | CC: | allinux4, awilliam, caf, costashu, deep64blue, g.kaviyarasu, info, jim.owenby, jonathan, kparal, kvolny, lnykryn, mbanas, pbrobinson, psimerda, robatino, rtguille, satellitgo, stephent98, twu, vanmeeuwen+fedora | ||||||||||||||||||||||||||||||||||||||||||||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||||||||||||||||||||||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||||||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||||||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||||||||||||||||||||||||||||
Whiteboard: | abrt_hash:12d779e671efd28070ce3591644748a290ffc27d0d30e08f510d68a037fd244f AcceptedBlocker | ||||||||||||||||||||||||||||||||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||||||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||||||||||||||||||||||||||||
Last Closed: | 2013-03-14 00:56:10 UTC | Type: | --- | ||||||||||||||||||||||||||||||||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||||||||||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||||||||||||||||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||||||||||||||||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||||||||||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||||||||||||||||||||||||||
Embargoed: | |||||||||||||||||||||||||||||||||||||||||||||||||||
Bug Depends On: | |||||||||||||||||||||||||||||||||||||||||||||||||||
Bug Blocks: | 752661 | ||||||||||||||||||||||||||||||||||||||||||||||||||
Attachments: |
|
Description
Flóki Pálsson
2012-09-01 16:22:44 UTC
Created attachment 608916 [details]
File: ifcfg.log
Created attachment 608917 [details]
File: anaconda-tb
Created attachment 608918 [details]
File: environ
Created attachment 608919 [details]
File: type
Created attachment 608920 [details]
File: storage.log
Created attachment 608921 [details]
File: version
Created attachment 608922 [details]
File: program.log
Created attachment 608923 [details]
File: product
Created attachment 608924 [details]
File: syslog
Created attachment 608925 [details]
File: hashmarkername
Created attachment 608926 [details]
File: anaconda.log
Created attachment 608927 [details]
File: release
Created attachment 608928 [details]
File: description
PackageSackError: <class 'yum.Errors.PackageSackError'> YumBaseError: <class 'yum.Errors.YumBaseError'> error: ('installing package kernel-3.6.0-0.rc2.git2.1.fc18.x86_64 needs 250MB on the / filesystem', (9, '/', 262017024L)) script_log: <closed file '<fdopen>', mode 'w+b' at 0x47d5390> YumRPMTransError: <class 'yum.Errors.YumRPMTransError'> rpmcb: <pyanaconda.packaging.yumpayload.RPMCallback object at 0x440e090> 1. Start installation 2. Proceed to main hub 3. Select partitioning, create custom partitioning 4. Let anaconda create basic partitioning for you 5. Resize / partition to 2GB 6. Proceed with installation 7. Traceback while preparing transaction Package: anaconda-18.11 OS Release: Fedora release 18-Beta-TC1 Happened while preparing transaction from installation source tc1 netinst 64 bit Package: anaconda-18.11 OS Release: Fedora release 18-Beta-TC1 Original reporter had a 500MB root filesystem. The payload's space requirement was around 650MB. We need to make sure we're updating the space check whenever software selection or storage setup changes. Just trying to install a standard gnome install on a KVM VM using all defaults for partitioning etc Package: anaconda-18.12 OS Release: Fedora release 18-Beta-TC2 set KDE desktop set argentina / buenos aires (no ntp) set keyboard spanish and then i reclaimed space deleting previous fedora install, (or at leas i belive to have done so) Package: anaconda-18.14 OS Release: Fedora release 18-Beta-TC3 Created attachment 624390 [details]
snapshot, during root password
attempting to reproduce bug 866204 using clean, default, minimal f16 install as starting point first attempt resulted in a black display; anaconda, x gone restarted without cleaning up the target disc image Package: anaconda-18.16 OS Release: Fedora release 18-Beta-TC4 Created attachment 627144 [details]
anaconda.log (18.16)
Created attachment 627145 [details]
ifcfg.log (18.16)
Created attachment 627146 [details]
packaging.log (18.16)
Created attachment 627147 [details]
program.log (18.16)
Created attachment 627148 [details]
storage.log (18.16)
Created attachment 627149 [details]
syslog (18.16)
Created attachment 627150 [details]
X.log (18.16)
Created attachment 627151 [details] ps-ef-1.txt ("ps -ef" after screen went black; 18.16) (In reply to comment #21) > attempting to reproduce bug 866204 > using clean, default, minimal f16 install as starting point > first attempt resulted in a black display; anaconda, x gone > restarted without cleaning up the target disc image > > > Package: anaconda-18.16 > OS Release: Fedora release 18-Beta-TC4 I was mistaken. Xorg is running. anaconda and metacity are not. Both /mnt/sysimage/etc/ and /mnt/sysimage/boot/ have F16 files: $ cat etc-fedora-release-1.txt Fedora release 16 (Verne) $ cat ls-lF-boot-1.txt total 19832 -rw-------. 1 root root 2458775 Nov 1 2011 System.map-3.1.0-7.fc16.x86_64 -rw-r--r--. 1 root root 118511 Nov 1 2011 config-3.1.0-7.fc16.x86_64 drwxr-xr-x. 2 root root 1024 Oct 14 21:59 grub/ drwxr-xr-x. 3 root root 7168 Oct 14 22:01 grub2/ -rw-r--r--. 1 root root 13575517 Oct 14 22:00 initramfs-3.1.0-7.fc16.x86_64.img drwx------. 2 root root 12288 Oct 14 21:57 lost+found/ -rwxr-xr-x. 1 root root 4125616 Nov 1 2011 vmlinuz-3.1.0-7.fc16.x86_64* Reproduced twice. i tried automatic partitioning type btrfs ona a preexisting dualboot guest choose preserve for the ntfs, and delete for the others except shrink for the last i noticed that a previous biosboot partition was incorrecly show as a previous /, maybe anaconda mistook it for the / filesystem (for which i choose shrink) Package: anaconda-18.24 OS Release: Fedora release 18-Beta-TC7 Created attachment 638147 [details]
storage.log
(In reply to comment #30) > i tried automatic partitioning type btrfs ona a preexisting dualboot guest > choose preserve for the ntfs, and delete for the others except shrink for > the last > i noticed that a previous biosboot partition was incorrecly show as a > previous /, maybe > anaconda mistook it for the / filesystem (for which i choose shrink) > This is not at all related to the bug in which you are reporting it. Please open a new bug report for your issue. (In reply to comment #32) > (In reply to comment #30) > > i tried automatic partitioning type btrfs ona a preexisting dualboot guest > > choose preserve for the ntfs, and delete for the others except shrink for > > the last > > i noticed that a previous biosboot partition was incorrecly show as a > > previous /, maybe > > anaconda mistook it for the / filesystem (for which i choose shrink) > > > > This is not at all related to the bug in which you are reporting it. Please > open a new bug report for your issue. These strings in Comment 30 indicate a software-assisted bug report that was classified as a duplicate of this bug report: Package: anaconda-18.24 OS Release: Fedora release 18-Beta-TC7 See also: Comment 15, Comment 16, Comment 18, Comment 19, Comment 21 OT Comment: These mini-reports need to be better identified. What would you like to see them contain? i believe that it happened because i choose minimal, select a disks with free space and then went again and selected kde with all addons, hoping that the 'plenty of free space' was refering to minimal. All was ok in the main hub, so i started installing and kaboooom. Maybe i was right. Package: anaconda-18.24 OS Release: Fedora release 18-Beta-TC7 @David Lehman Please note that both comment #34 and #30 were done by ABRT. (I attached the log manually to #31 later). Attempting to reproduce Bug 875422. Package: anaconda-18.28 OS Release: Fedora release 18-Beta-TC8 *** Bug 873852 has been marked as a duplicate of this bug. *** anaconda-18.37.1-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2012-19991/anaconda-18.37.1-1.fc18 I've just tried to install F18 ... I guess the installer shouldn't just stop working here without giving any chance to retry .. Package: anaconda-18.36 OS Release: Fedora release 18 (In reply to comment #39) > I've just tried to install F18 ... I guess the installer shouldn't just stop > working here without giving any chance to retry .. > > Package: anaconda-18.36 > OS Release: Fedora release 18 hm, I'm not sure if abrt chosen the right bug to append a dupe to, but I really do not have problems with space in / ... my root partition is about 600 GiB big! Discussed at 2012-12-12 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-12/f18final-blocker-review-4.2012-12-12-17.01.log.txt . Accepted as a blocker per criterion "The installer's custom partitioning mode must be capable of the following ... Rejecting obviously invalid operations without crashing". Package anaconda-18.37.2-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.37.2-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19991/anaconda-18.37.1-1.fc18 then log in and leave karma (feedback). anaconda-18.37.2-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. Can somebody please verify this is fixed with the new version? Thank you! Hi Kamil, I'm not able to reproduce this, since anaconda now doesn't allow me to continue with only 2GB on / partition (comment 15). Checking seems to be OK, I tried the exact size of / which anaconda told me is required and it worked. Tested on Fedora-18-TC2 Great, thanks Martin. Closing. (In reply to comment #39) > I've just tried to install F18 ... I guess the installer shouldn't just stop > working here without giving any chance to retry .. > > Package: anaconda-18.36 > OS Release: Fedora release 18 Agreed. Plus when anaconda doesn't find a package (cracklib-dicts in my case), it allows to file a bug report and it says it would be duplicate to this one. That looks completely broken. Have just hit this problem in F18 using the DVD installer. I don't see a comment from libreport saying you hit this bug, which makes me sceptical that you actually hit what was fixed in this report. Could you please provide more details and, ideally, logs? Thanks. Hi Adam I think you are right, have used this DVD a few times and it has been fine. After hitting this issue twice today I noticed some marks on the DVD, cut a new one and it worked fine. Thanks! OK, so let's close this again. I have hit this bug today. Logfiles should be provided in the automatic bug report. (In reply to comment #52) > I have hit this bug today. Logfiles should be provided in the automatic bug > report. After reading the comments closely, I also checked my installation media. The instalation check of the DVD failed! So this is not a Fedora bug. |