Red Hat Bugzilla – Bug 882722
'KeyError: None' while trying to install F18 beta
Last modified: 2012-12-12 00:57:56 EST
Description of problem:
Trying to install F18 beta onto a disk that I have already pre-partitioned, and using custom partitioning to try and associate those pre-existing partitions to what I want used for F18.
Version-Release number of selected component:
libreport version: 2.0.17
cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
:The following was filed automatically by anaconda:
:anaconda 18.34 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1679, in _populate_right_side
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1287, in _save_right_side
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2162, in on_page_clicked
: File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/accordion.py", line 119, in _onExpanded
Created attachment 656264 [details]
Created attachment 656265 [details]
Created attachment 656266 [details]
Created attachment 656267 [details]
Created attachment 656268 [details]
Created attachment 656269 [details]
Created attachment 656270 [details]
Created attachment 656271 [details]
Created attachment 656272 [details]
Created attachment 656273 [details]
Created attachment 656274 [details]
Created attachment 656275 [details]
Created attachment 656276 [details]
Created attachment 656277 [details]
Proposing as F18 final blocker, since I was unable to install while reusing an LVM partition from a LUKS-encrypted volume group.
I was using Anaconda to re-use some logical volumes from a previous installation. That part worked fine, but when I went back and clicked on the + sign next to the Fedora 18 volumes/mount points/whatever you want to call them, it crashed :-(
OS Release: Fedora release 18
Please let me know if you want any of my log files, and I'll attach them. (I see that some one else already attached theirs, so I won't duplicate logs unless someone tells me that they're useful.)
I believe that the criterion in question here is from the F18 final release criteria :
The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above.
+1 Final blocker.
The criterion sounds like it is being met to me.
Discussed at 2012-12-05 blocker review meeting - http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-05/f18final-blocker-review-2.2012-12-05-17.01.log.txt . We feel like this is very likely a blocker bug, but we'd just like to be sure of the circumstances that trigger it first. If either reporter or the anaconda team can determine the precise trigger for this - is it any re-use of existing LVs? Encrypted ones only? - we'll be able to make a definite determination.
In my case, I tried to re-use encrypted LVM logical volumes.
As I remember it, as I went in and gave the LVs their label and/or mount point, they appeared on the tree view on the left-hand pane of the installation window. It was when I went to expand the list of *new* (partitions? mount points? volumes?) at the top of the left-hand pane that things exploded.
If I get time this afternoon, I'll try to reproduce it again.
I have a patch here I'll be testing soon.
anaconda-18.36-1.fc18 has been submitted as an update for Fedora 18.
* 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.36-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-18.36-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
This got closed pretty fast, it'd be nice to have verification from the reporters that it's fixed. Jared, Eric - 18.36 is in Final TC1, so can you check with that? Thanks!
I'm planning on testing it Monday, when I have the time...
David, do you have some simple reproducer so that anyone can test it?
As I recall, the following should reproduce it:
1. do an encrypted autopart install
2. start another install
3. enter custom storage spoke
4. decrypt PVs from previous install
5. select any of the LVs from the previous install
6. activate "Reformat"
7. click "Apply Changes"
8. click on the same LV under the "New Fedora" subtree
I'm not sure if 8 is necessary or not. If it hasn't crashed yet when you get to it, do it as well.
Discussed at 2012-12-10 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-10/f18final-blocker-review-3.2012-12-10-17.13.log.txt . Accepted as a blocker per criterion "The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above" in the case of re-using existing encrypted PVs.
(In reply to comment #29)
> As I recall, the following should reproduce it:
> 1. do an encrypted autopart install
> 2. start another install
> 3. enter custom storage spoke
> 4. decrypt PVs from previous install
> 5. select any of the LVs from the previous install
> 6. activate "Reformat"
> 7. click "Apply Changes"
> 8. click on the same LV under the "New Fedora" subtree
> I'm not sure if 8 is necessary or not. If it hasn't crashed yet when you get
> to it, do it as well.
Yes, that matches what I recall when I saw the crash. In the meantime, I upgraded to anaconda 18.37, and retried, and this time was successful. Looks like you did indeed fix it.
So since the fix was in 18.36 and that went stable, let's close this.