+++ This bug was initially created as a clone of Bug #1019322 +++ Description of problem: Kickstart btrfs installation fails. Version-Release number of selected component (if applicable): anaconda-20.25.1-1 How reproducible: always Steps to Reproduce: 1. Prepare kickstart containing following lines: zerombr clearpart --all --initlabel part btrfs.01 --size=6000 --ondisk=vda part btrfs.02 --size=6000 --ondisk=vdb btrfs none --data=0 --metadata=1 --label=rhel btrfs.01 btrfs.02 btrfs / --subvol --name=root LABEL=rhel 2. Prepare a machine with two empty unformatted discs. 3. Start the first installation use prepared kickstart. Installation is successful. 4. Start the second installation, use the same kickstart on the same machine (discs are not empty now). Actual results: During second kickstart installation unknown error occurs. Expected results: No errors. Kickstart installation should be successful. Additional info:
Anaconda is currently preferring existing devices when resolving device specs, which is a problem when you are removing a device with the same spec (label, in this case) as one you are creating. It should prefer whatever is in the devicetree at the time it is resolving the spec. I have a patch for this, but I have not tested it yet.
Discussed at 2013-10-23 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-10-23/f20-blocker-review.2013-10-23-16.00.log.txt . As we still do not have detailed kickstart criteria, this was evaluated subjectively on its merits, and accepted as a blocker bug. We noted that it seems reasonable to apply the 'interactive' criteria to kickstart installs, so far as storage goes, and this would violate the criterion "When using the custom partitioning flow, the installer must be able to: Remove existing storage volumes and Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes" in an interactive install.
anaconda-20.25.4-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.25.4-1.fc20
Package anaconda-20.25.4-1.fc20, pykickstart-1.99.44-1.fc20, python-blivet-0.23.2-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 anaconda-20.25.4-1.fc20 pykickstart-1.99.44-1.fc20 python-blivet-0.23.2-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20033/pykickstart-1.99.44-1.fc20,python-blivet-0.23.2-1.fc20,anaconda-20.25.4-1.fc20 then log in and leave karma (feedback).
I tried to verify using reproducer in comment 0, but Anaconda presents an error during the first installation attempt: > The following problem occurred on line 18 of the kickstart file: > Tried to use undefined partition btrfs.01 in BTRFS volume specification Is the kickstart sample wrong?
Created attachment 817886 [details] anaconda.log
Created attachment 817887 [details] program.log
Created attachment 817888 [details] storage.log
Created attachment 817889 [details] syslog
Created attachment 817890 [details] minimal.ks
(In reply to Kamil Páral from comment #5) > I tried to verify using reproducer in comment 0, but Anaconda presents an > error during the first installation attempt: > > > The following problem occurred on line 18 of the kickstart file: > > Tried to use undefined partition btrfs.01 in BTRFS volume specification There was an error in my original patch. I have just pushed a followup patch that fixes the problem for me.
David, is the patch part of anaconda 20.25.5-1.fc20 (Beta RC2)? Or is there some updates.img available? Can you provide it so that we can check the fix in advance? Thanks.
The fix is in 20.25.6-1. Here's a link to the commit/patch: https://git.fedorahosted.org/cgit/anaconda.git/commit/?h=f20-branch&id=79caf94fc54d8afe4e3fb991c441123795539ed6
http://koji.fedoraproject.org/koji/buildinfo?buildID=475300 is 20.25.6, but it doesn't appear to be in an update yet.
anaconda-20.25.4-1.fc20, pykickstart-1.99.44-1.fc20, python-blivet-0.23.2-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
python-blivet-0.23.3-1.fc20, anaconda-20.25.6-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/FEDORA-2013-20387/anaconda-20.25.6-1.fc20,python-blivet-0.23.3-1.fc20
Petr tried to verify this with Beta RC2 and was stopped by bug 1026825. It might be caused by the fix in comment 13.
I have verified that this is fixed with Beta RC4. However, during boot I see an error message > error: no such device: root. right after selecting Fedora item in grub. If I hit a key or wait a while, the boot continues as normal and the system seems to be working OK.
Created attachment 820264 [details] grub error after install
I can confirm that problem is fixed. I have also met 'no such device' problem as Kamil in comment 18.
Please open a bug for the grub issue and include a screenshot without quiet or graphical mode (if possible) in addition to the following files: /var/log/anaconda/anaconda.program.log /boot/grub2/grub.cfg Thanks.
python-blivet-0.23.3-1.fc20, anaconda-20.25.6-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.