Description of problem: I put Alpha 1-1 image to usb with: livecd-iso-to-disk --reset-mbr --format Fedora-Workstation-Live-x86_64-25_Alpha-1.1.iso /dev/sdb In installation destination I choose one disk and choose to delete all the partitions. Then error appears with message: "autopart failed: /dev/sdd1 is currently mounted and cannot be used for the installation. Please unmount it and retry." /dev/sdd is the media from which I booted the system so it cannot be unmounted. This exact thing happens with two different flash disks and on two different computers. Version-Release number of selected component (if applicable): anaconda-24.20-2.fc25.x86_64 Fedora-Workstation-Live-x86_64-25_Alpha-1.1.iso How reproducible: always Steps to Reproduce: 1. create bootable flash disk by running livecd-iso-to-disk --reset-mbr --format Fedora-Workstation-Live-x86_64-25_Alpha-1.1.iso /dev/<flash disk> 2. Boot, go to the installation destination 3. Choose disk and let anaconda to autopart Actual results: Autopart fails and wants you to unmount usb from which the installation runs. Expected results: Chosen disk is used and parted Additional info: I propose this as beta blocker as it violates the combination of beta criterion: "All release-blocking images must boot in their supported configurations. This criterion differs from the similar Alpha criterion only in that it requires all supported methods of writing a Fedora USB stick to work, not just any single one." and the alpha criterion: "The installer must be able to complete an installation to a single disk using automatic partitioning." Installation works with other methods of writing an image to usb stick.
Created attachment 1193606 [details] anaconda.log
Created attachment 1193607 [details] program.log
Created attachment 1193608 [details] storage.log
Created attachment 1193609 [details] Screenshot of error message
Created attachment 1193610 [details] output of 'mount -a'
+1 beta blocker, also +1 Alpha FE if we wind up slipping and someone wants to fix this this week...
Discussed during the 2016-08-29 blocker review meeting: [1] The decision to classify this bug as an AcceptedBlocker was made as it is a clear violation of the Beta Blocker Criteria, which states "All release-blocking images must boot in their supported configurations. This criterion differs from the similar Alpha criterion only in that it requires all supported methods of writing a Fedora USB stick to work, not just any single one" and "The installer must be able to complete an installation to a single disk using automatic partitioning." [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-08-29/f25-blocker-review.2016-08-29-16.00.txt
I am seeing this same bug on Fedora-Workstation-Live-x86_64-25_Alpha-2.iso.
I can reproduce this. However in the attached logs I see this 01:44:59,594 INFO anaconda: Performing post-installation setup tasks -- DONE 01:44:59,594 INFO anaconda: Thread Done: AnaInstallThread (139661271574272) So the installation completed? That doesn't make sense based on the screen shot and description of it failing within autopart. And I also don't see sda, sdb, sdc, or sdd1 in any of the logs, but foudn in the screenshot. So I'm going to attach a bunch of my own logs that show sdb1 (USB stick) as failing the installation for the same reason; and the storage.log also contains a blivet exception and traceback.
Created attachment 1200675 [details] storage.log cmurphy
Created attachment 1200676 [details] anaconda.log cmurphy
Created attachment 1200677 [details] journal.log cmurphy
Created attachment 1200678 [details] program.log cmurphy
21:35:22,726 INFO blivet: sdb1 looks to be the live device; marking as protected ... 21:35:26,297 INFO program: Running... umount /home 21:35:26,300 INFO program: stderr: 21:35:26,300 INFO program: b'umount: /home: target is busy' ... 21:35:26,416 INFO blivet: teardown of EncHome failed: umount of /home failed (32) ##/home is encrypted on the live media using --home-size-mb option when creating ... 19:36:02,346 DEBUG blivet: removing all non-preexisting partitions ['req0(id 367)', 'req1(id 374)', 'req2(id 381)', 'sdb1(id 11)'] from disk(s) ['sda' .... OK so decent chance comment 9 through comment 13 can be ignored because I used --overlay-size-mb and --home-size-mb and end up with cluttered logs as a result. I get the same failure but possibly for different reasons.
I just retested without --home-size-mb and --overlay-size-mb and get the same results in the logs I attached, minus the complaints about /home.
*** Bug 1369607 has been marked as a duplicate of this bug. ***
Hey Anaconda Devs, After reviewing this bug during the 2016-09-26 Blocker-Review-Meeting, we noticed that there has been no progress made in several days. Is there anything the QA team can do to help get this bug solved? Thanks, Geoff M. - QA IRC: coremodule
Retested with Fedora-Workstation-Live-x86_64-25-20160924.n.0.iso which contains anaconda 25.20.1-1. Used livecd-tools-23.4-1.fc24.x86_64. Same results in the logs as what are attached (by me), including all the blivet exception tracebacks.
https://github.com/rhinstaller/anaconda/pull/817
anaconda-25.20.4-1.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-067d26633e
This worked for me with Beta 1.1.
anaconda-25.20.4-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.