Description of problem: anaconda ext4 shrink "Error checking storage configuration"
Version-Release number of selected component (if applicable):
fc21 pre_GA TC2 iso from http://ppc.koji.fedoraproject.org/stage/21_TC2/
Steps to Reproduce: following the steps described in https://fedoraproject.org/wiki/QA:Testcase_partitioning_guided_shrink
1. install a ppc64le guest with ext4 FS, verify that able to boot.
2. re-install the same guest and try to shrink the / (root) fs
The Installation Summary GUI reports "Error checking storage configuration"
* The same problem is reported if using ppc64 iso in place of ppc64le iso
* If the guest is initially installed with ext3 in place of ext4, then no such error.
I gathered in attached tarball vm46_error_checking_storage.tgz all the logs from anaconda /tmp/ directory And appended in same tarball some image captures of vnc GUI
Created attachment 962004 [details]
Proposed as a Blocker for 21-final by Fedora user michelmno using the blocker tracking app because:
This is a blocker as per criteria of https://fedoraproject.org/wiki/QA:Testcase_partitioning_guided_shrink
Failure reported for ppc64 and ppc64le secondary architectures with ext4 FS.
I do not know if cause of the problem, but the anaconda.log has only one "ERR" line as extracted here:
04:59:33,514 INFO anaconda: setting <pyanaconda.ui.gui.spokes.storage.StorageSpoke object at 0x3fff88c12e50> status to: Saving storage configuration...
04:59:33,623 ERR anaconda: storage configuration failed: Unable to allocate requested partition scheme.
04:59:33,705 INFO anaconda: setting <pyanaconda.ui.gui.spokes.storage.StorageSpoke object at 0x3fff88c12e50> status to: Failed to save storage configuration...
This cannot be a blocker unless it is reproduced on a primary architecture. Can you please test as similar as possible a scenario on an x86 or ARMv7 system? Thanks.
For the record, the anaconda team prefers the logs attached individually as text files, not as one big tarball glob.
To be clear - by marking this as blocking the 'FinalBlocker / F21FinalBlocker' bug, you've proposed it as a blocker for the official, primary arch Fedora 21 release. If you wanted to propose it as a blocker for the PPC64 release, I believe there is a different tracker bug you should mark it as blocking instead. The blocker proposal webapp that you used doesn't currently support proposing blockers for secondary arch releases, I'm afraid.
I am changing manually the blocker bug ref from primary bug 1043129 to secondary bug 1146698 as suggested in comment 5.
I tried to reproduce with iso TC2 on a ppc64 LPAR.
I got the same behavior with following partitions scheme:
sda1 10 MiB PReP Boot
sda2 512 MiB /boot
sda3 27 GiB /
sda5 8 GiB /home
sda6 2 GiB swap
sda7 12 GiB /data
During the reinstall, I asked to shrink sda2, and let anaconda perform an automatic LVM partitionning for the new install. Then the "Error checking storage configuration" occured.
But interestingly, if the test is performed with a much simpler initial partition scheme like:
sda1 10 MiB PReP Boot
sda2 50 GiB /
Then for reinstall, Anaconda is able to shrink the 50 GiB sda2 partition, create the LVM layout and perform the whole installation without any problem. And at the end, partitions are:
sda1 10 MiB PReP Boot
sda2 12 GiB / (root of the first install)
sda3 512 MiB /boot (second install, boot outside LVM)
sda5 38 GiB Linux LVM (second install)
dropping from Final Blocker as with a simple existing disk layout the shrinking works, but keeping open to track the more complex layout
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 21 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.