Description of problem: I ran into this while rying to customize the automatic partitioning scheme that Anaconda selected for me. I am using Fedora 20 Scientific Spin Test Compose 3 (x86-64). Version-Release number of selected component: anaconda-20.10-1.fc20.x86_64 The following was filed automatically by anaconda: anaconda 20.10-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1948, in copy root.swaps = [new.devicetree.getDeviceByID(d.id) for d in root.swaps] File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 767, in _save_devicetree _blivet_copy = self.storage.copy() File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 704, in configure self._save_devicetree() File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1924, in factoryDevice factory.configure() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1069, in _replace_device new_device = self.__storage.factoryDevice(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1360, in _save_right_side selector=selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2398, in _save_current_selector self._save_right_side(self._current_selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2409, in on_selector_clicked self._save_current_selector() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/accordion.py", line 216, in _onSelectorClicked cb(selector) AttributeError: 'NoneType' object has no attribute 'id' Additional info: 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 executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.0-3.fc20.x86_64 other involved packages: python-blivet-0.20-1.fc20.noarch product: Fedora release: Fedora release 20 (Null) type: anaconda version: 20
Created attachment 793915 [details] File: anaconda.log
Created attachment 793916 [details] File: environ
Created attachment 793917 [details] File: lsblk_output
Created attachment 793918 [details] File: messages
Created attachment 793919 [details] File: nmcli_dev_list
Created attachment 793920 [details] File: os_info
Created attachment 793921 [details] File: program.log
Created attachment 793922 [details] File: storage.log
Created attachment 793923 [details] File: ifcfg.log
Created attachment 793924 [details] File: anaconda-tb
Attempt to encrypt all partitions and logical volumes. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Alpha-TC4\x20x86_64 quiet BOOT_IMAGE=vmlinuz hashmarkername: anaconda kernel: 3.11.0-3.fc20.x86_64 package: anaconda-20.10-1 product: Fedora reason: AttributeError: 'NoneType' object has no attribute 'id' release: Cannot get release name. version: 20-Alpha-TC4
Created attachment 794389 [details] anaconda-tb for Comment 11
Comment on attachment 794389 [details] anaconda-tb for Comment 11 Tested with: $ qemu-kvm -m 4096 -hda f20-test-3.img -cdrom ~/xfr/fedora/F20/Alpha/Fedora-20-Alpha-TC4-x86_64-DVD.iso -vga std -boot menu=on
python-blivet-0.22-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/python-blivet-0.22-1.fc20
Package python-blivet-0.22-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-blivet-0.22-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16042/python-blivet-0.22-1.fc20 then log in and leave karma (feedback).
*** Bug 1004846 has been marked as a duplicate of this bug. ***
Custom partition, re-use existing ext4 partition as root. Delay, then error comes up. 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.14-1 product: Fedora reason: AttributeError: 'NoneType' object has no attribute 'id' release: Cannot get release name. version: 20-Alpha
Looks like the python-blivet fix wasn't what was needed for this. If it was in the Alpha candidate. I would hope that each new test candidate would pull in all the updates in updates-testing before being created. That's the point of having tests, right? Can someone confirm? So, same behavior as TC5. Failed when creating the root partition from an existing ext4 partition when in the manual partition screen. It failed once when selecting a /boot partition also. The behavior is strange. I select an existing partition, then click +. The popup to create a mount point comes up, I select the mount point, leave the size blank as recommended, and click create mount point. Up comes the information in the upper right hand corner, but nothing shows up under F20 in the upper left, and the mount point isn't filled in on the upper right. And the selection popup becomes part of the page under the information in the upper right. But it won't let me select a new partition. Sometimes it will let me fill in the mount point on the upper right, sometimes not. Because I read that anaconda now requires formatting on the root partition, I selected that, and after a delay, the display refreshed with the box checked. But then everything was frozen except the mouse. Eventually, the error showed up.
I suspect you don't have python-blivet-0.22-1, which is what you need to get the fix. FWIW anaconda has required creating a new root filesystem for several years now.
I always re-format anyway, so I wouldn't have noticed. I just mentioned it for completeness of the description. In case it mattered to the error. Obviously it doesn't if I was using the broken version of the program that is causing the error. :-)
Come on guys! Still? All I am trying to do is what worked flawlesslly in 19: select a single disk, btrfs fs, custom paritioning. Click +, select / and request 50GB. Errors out every time. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:UUID=a9901eab-13b6-4f9d-8a40-991dd02acaa2 selinux=0 BOOT_IMAGE=vmlinuz hashmarkername: anaconda kernel: 3.11.0-300.fc20.x86_64 package: anaconda-20.14-1 product: Fedora reason: AttributeError: 'NoneType' object has no attribute 'id' release: Cannot get release name. version: 20-Alpha
*** Bug 1007094 has been marked as a duplicate of this bug. ***
Assigning / to existing ext4 partition in custom partitioning. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Alpha\x20x86_64 rd.live.check quiet BOOT_IMAGE=vmlinuz hashmarkername: anaconda kernel: 3.11.0-300.fc20.x86_64 package: anaconda-20.15-1 product: Fedora reason: AttributeError: 'NoneType' object has no attribute 'id' release: Cannot get release name. version: 20-Alpha
same ol' same ol'. Tried to create btrfs / on empty (except for bios-boot partition) disk. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:UUID=a9901eab-13b6-4f9d-8a40-991dd02acaa2 selinux=0 BOOT_IMAGE=vmlinuz hashmarkername: anaconda kernel: 3.11.0-300.fc20.x86_64 package: anaconda-20.15-1 product: Fedora reason: AttributeError: 'NoneType' object has no attribute 'id' release: Cannot get release name. version: 20-Alpha
This was with Alpha TC2. The file size was the same as Alpha TC1, but the checksum was different (Alpha TC1 failed), so I assume I was using the right file. Anyhow, still has the error. Not sure if this image had python-blivet-0.22-1 in it. Probably not, given the result. Is there a time frame for when that version will go into the images? After release? i.e. is the image now frozen until after release? But the iso images don't change after release, do they? F21?
confirm fixed using live cd from 20130914 updated with python-blivet-0.22-1.fc20.noarch, anaconda-20.16-1.fc20.x86_64. Other probs tho; off to search for bzs.
I looked at the pull request for Alpha RC3 and didn't see python-blivet-0.22-1 mentioned at all, though anaconda is up to 20.17-1. Before I download and try, can someone confirm whether the fix for this bug is in the new Alpha RC3. Thanks.
Just testing on the off-chance python-blivert-0.22-1 had been included. One wonders why a fix is not included when the fix has been shown to fix a problem. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:UUID=a9901eab-13b6-4f9d-8a40-991dd02acaa2 selinux=0 BOOT_IMAGE=vmlinuz hashmarkername: anaconda kernel: 3.11.0-300.fc20.x86_64 package: anaconda-20.18-1 product: Fedora reason: AttributeError: 'NoneType' object has no attribute 'id' release: Cannot get release name. version: 20-Alpha
*** Bug 1010441 has been marked as a duplicate of this bug. ***
"One wonders why a fix is not included when the fix has been shown to fix a problem." One could instead just read the policy: https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process It is not a hard page to find: https://fedoraproject.org/wiki/Special:WhatLinksHere/QA:SOP_freeze_exception_bug_process If anyone had bothered to nominate this as a freeze exception issue it would likely have made Alpha. But no-one did.
*** Bug 1011423 has been marked as a duplicate of this bug. ***
(In reply to Adam Williamson from comment #30) > "One wonders why a fix is not included when the fix has been shown to fix a > problem." > > One could instead just read the policy: > > https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process > > It is not a hard page to find: > > https://fedoraproject.org/wiki/Special:WhatLinksHere/QA: > SOP_freeze_exception_bug_process > > If anyone had bothered to nominate this as a freeze exception issue it would > likely have made Alpha. But no-one did. Nice to know. No need for sarcasm. Looks like this bz was reviewed after the fix as confirmed by Fedora QA and Anaconda folks who could have just stepped in and pushed the fix.
*** Bug 1011598 has been marked as a duplicate of this bug. ***
No sarcasm intended, just explaining the situation. The intent is that no-one 'just steps in and pushes fixes'. That's the point of having a freeze exception process in the first place: when we just relied on people in the loop exercising 'common sense' in choosing what fixes to push, what we got was a mess with lots of needless breakage. So we came up with a policy and process to deal with it instead, and that's what the FE process is. With a process we can always track precisely what issues we will and will not take fixes for during freezes, and the policy aids us in deciding which fixes we ought to take and which we shouldn't, and doing that consistently and sensibly. (anaconda doesn't actually obey the alpha freeze entirely, they put non-FE changes into builds during the freeze, which we in QA aren't entirely happy with, but we can see their reason for doing so. but since there was no blocker or FE bug which caused us to pull a new python-blivet into the RC builds, this fix didn't make it.)
(In reply to Adam Williamson from comment #34) > <snip> Thanks. Makes sense. I just couldn't understand why the fix wasn't pushed. There is a workaround if you use one of the nightly live isos and yum update python-blivet and that allowed me to provide positive karma. I see now that koji msged that python-blivet can be pushed if the maintainer desires. We'll see what happens.
Discussed in 2013-09-25 Blocker Review Meeting [1]. Acknowledged as an AcceptedBlocker - Violates the follwing F20 beta release criterion: "When using the custom partitioning flow, the installer must be able to ... Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions" [2][3]. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-09-25/ [2] https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria#Custom_partitioning [3] https://fedoraproject.org/wiki/Fedora_20_Beta_Release_Criteria#Guided_partitioning
Custom partitioning, standard partitions, root and swap on sda, omit install of bootloader. cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:LABEL=Fedora\x2020-Alpha\x20x86_64 BOOT_IMAGE=vmlinuz hashmarkername: anaconda kernel: 3.11.0-300.fc20.x86_64 package: anaconda-20.18-1 product: Fedora reason: AttributeError: 'NoneType' object has no attribute 'id' release: Cannot get release name. version: 20-Alpha
python-blivet-0.22-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1015817 has been marked as a duplicate of this bug. ***
*** Bug 1034997 has been marked as a duplicate of this bug. ***