Red Hat Bugzilla – Bug 812528
creating LV partitions sometimes overwrites previous definitions
Last modified: 2012-05-12 12:21:52 EDT
Created attachment 577456 [details]
bug video demonstration
Description of problem:
When I do a custom layout and create new LV partitions, I have found a way where first I create root partition and then I try to add swap partition, but the swap partition definition overwrites the root partition definition (the root partition disappears). It's more obvious from the attached video.
Simple workaround is present, just name your partition differently from default "lv". It is then not overwritten.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. follow the steps in the video
Even though this bug is not critical, it might be confusing (people might not notice that some partitions were overwritten by another ones). Proposing as at least NTH. A full blocker may be discussed as well.
Would be useful to get the anaconda logs when this happens. Any chance you can upload those?
I suspected it as a UI bug, so I didn't expect anything useful to be shown in logs. Also it can be extremely easily reproduced. But here you go.
PS: X crashed when I switched to console, but that is not relevant in this case.
Created attachment 578255 [details]
Created attachment 578256 [details]
Created attachment 578257 [details]
Created attachment 578258 [details]
Created attachment 578259 [details]
Created attachment 578260 [details]
I reproduced exactly the same as you see in the video, then hit OK in the VG creation dialog and collected the logs.
Discussed at 2012-05-04 NTH review meeting. This is accepted as NTH as it's a significant installer bug, but please note we are agreed that it would be bad to poke this code very late: let's say we take it as an NTH for the first week or so of the freeze, but after that, we might not want to take a change. Anaconda team, please check with QA and releng before pushing a fix for this into f17-branch. thanks!
Fedora Bugzappers volunteer triage team
anaconda-17.26-1.fc17 has been submitted as an update for Fedora 17.
This bug seems to be fixed in 17.26-1
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-17.26-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-17.26-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.