Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1023192

Summary: FSError: filesystem already exists
Product: Red Hat Enterprise Linux 7 Reporter: David Lehman <dlehman>
Component: python-blivetAssignee: David Lehman <dlehman>
Status: CLOSED CURRENTRELEASE QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.0CC: anaconda-maint-list, dshea, mganisin, mkolman, mruckman, savsingh, sbueno
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: abrt_hash:4cef3b27011be6b42a02f849aba2279dc1742e845e17387f7ea52d2335407679 AcceptedBlocker
Fixed In Version: python-blivet-0.18.8-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1012504 Environment:
Last Closed: 2014-06-13 13:17:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1012504    
Bug Blocks:    

Description David Lehman 2013-10-24 20:29:54 UTC
+++ This bug was initially created as a clone of Bug #1012504 +++

Description of problem:
Many attempts to get the layout I wanted in Manual partitioning, followed by Reset All, followed by another attempt. Installation had begun, and then installer crashed while creating ext4 on /dev/sda6.

Version-Release number of selected component:
anaconda-20.18-1.fc20.x86_64

The following was filed automatically by anaconda:
anaconda 20.18-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 779, in create
    raise FSError("filesystem already exists")
  File "/usr/lib/python2.7/site-packages/blivet/deviceaction.py", line 471, in execute
    options=self.device.formatArgs)
  File "/usr/lib/python2.7/site-packages/blivet/devicetree.py", line 237, in processActions
    action.execute()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 310, in doIt
    self.devicetree.processActions()
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 169, in turnOnFilesystems
    storage.doIt()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line 142, in doInstall
    turnOnFilesystems(storage, mountOnly=flags.flags.dirInstall)
  File "/usr/lib64/python2.7/threading.py", line 764, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 168, in run
    threading.Thread.run(self, *args, **kwargs)
FSError: filesystem already exists

Additional info:
cmdline:        /usr/bin/python  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8
cmdline_file:   BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-Desktop-x86_64-20-Al ro rd.live.image quiet rhgb
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         3.11.0-300.fc20.x86_64
other involved packages: python-libs-2.7.5-7.fc20.x86_64, python-blivet-0.20-1.fc20.noarch
product:        Fedora
release:        Fedora release 20 (Heisenbug)
type:           anaconda
version:        20

--- Additional comment from Reartes Guillermo on 2013-10-20 19:26:24 EDT ---

Here are the most simple steps to reproduce it. 

0. Boot Fedora 20b TC5 (no kernel parameter, either on a new guest or on an unpartitioned disk)

1. Reach the Welcome Hub (either use the default -English- or select your language -mine is Spanish-)

2. Leave defaults for Date & Time, Language Support, Keyboard, Installation Source, Software Selection, Network Configuration.

3. Enter Installation Destination Spoke.

4. The single disk is already selected. Press 'done'

5. On Installation Options Dialog, choose to do custom/manual partitioning ("I want to review...") and select 'btrfs' for the Partition Scheme, then 'Continue'.

6. Click '+' add '/boot' of '512'

7. Click '+' add 'swap' of '512'

9. Click '+' add '/' of <null>, anaconda will select the maximum size (as intended).

10. Press 'done' to return to the Main Hub.

11. Press 'Accept Changes' in 'Summary Of Changes' dialog. 
    There it can be seen (among other entries):
    * Create Format btrfs           vda3
    * Create Device btrfs volume    fedora
    * Create Format btrfs           fedora
    * Create Device btrfs subvolume root   <<< HERE
    * Create Format ext4            root   <<< HERE

12. In the Main Hub, Start Installing, an 'unknown error' will popup.

Comment 2 David Lehman 2013-12-04 20:47:43 UTC
*** Bug 1036256 has been marked as a duplicate of this bug. ***

Comment 4 Ludek Smid 2014-06-13 13:17:00 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.