Bug 1391568

Summary: blivet.errors.DeviceFormatError: device path does not exist or is not writable
Product: [Fedora] Fedora Reporter: Jiri Konecny <jkonecny>
Component: python-blivetAssignee: Vratislav Podzimek <vpodzime>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: anaconda-maint-list, blivet-maint-list, g.kaviyarasu, jkonecny, jonathan, mkolman, vanmeeuwen+fedora, vpodzime, vponcova
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:46a2117db2160d5d9d5253f052c8807032df142068a51b36ba60fb5f051da1ce;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 11:28:09 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:    
Bug Blocks: 1277290    
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: dnf.librepo.log
none
File: environ
none
File: hawkey.log
none
File: lsblk_output
none
File: lvm.log
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: syslog
none
File: ifcfg.log
none
File: packaging.log none

Description Jiri Konecny 2016-11-03 14:56:44 UTC
Description of problem:
When I have precreated partitioning with RAID1 thinPool and thinLV for root on it, the installation will fail with this exception.

How reproducible:
Always

Steps to reproduce:
1) Create partitioning before installation
	a) RAID1 thinPool with thinLV on it
2) Start the installation
3) Go to Manual partitioning
4) Use precreated partition thinLV for / (root mountpoint)
5) Start the installation

Actual result:
Exception will raise

Expected result:
Installation should be successful

Version-Release number of selected component:
anaconda-25.20.5-1

The following was filed automatically by anaconda:
anaconda 25.20.5-1 exception report
Traceback (most recent call first):
  File "/usr/lib/python3.5/site-packages/blivet/formats/__init__.py", line 558, in _pre_destroy
    raise DeviceFormatError("device path does not exist or is not writable")
  File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.5/site-packages/blivet/formats/__init__.py", line 545, in destroy
    self._pre_destroy(**kwargs)
  File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.5/site-packages/blivet/deviceaction.py", line 696, in execute
    self.format.destroy()
  File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.5/site-packages/blivet/actionlist.py", line 325, in process
    action.execute(callbacks)
  File "/usr/lib/python3.5/site-packages/blivet/actionlist.py", line 48, in wrapped_func
    return func(obj, *args, **kwargs)
  File "/usr/lib/python3.5/site-packages/blivet/blivet.py", line 163, in do_it
    self.devicetree.actions.process(callbacks=callbacks, devices=self.devices)
  File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.5/site-packages/blivet/osinstall.py", line 1112, in turn_on_filesystems
    storage.do_it(callbacks)
  File "/usr/lib64/python3.5/site-packages/pyanaconda/install.py", line 204, in doInstall
    turn_on_filesystems(storage, mount_only=flags.flags.dirInstall, callbacks=callbacks_reg)
  File "/usr/lib64/python3.5/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.5/site-packages/pyanaconda/threads.py", line 251, in run
    threading.Thread.run(self, *args, **kwargs)
blivet.errors.DeviceFormatError: device path does not exist or is not writable

Additional info:
addons:         com_redhat_kdump, com_redhat_docker
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   initrd=/test/fedora_devel/initrd.img inst.stage2=ftp://cobra02/fedora_devel/ BOOT_IMAGE=/test/fedora_devel/vmlinuz 
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.8.4-301.fc25.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        25

Potential duplicate: bug 1379084

Comment 1 Jiri Konecny 2016-11-03 14:56:53 UTC
Created attachment 1217019 [details]
File: anaconda-tb

Comment 2 Jiri Konecny 2016-11-03 14:56:55 UTC
Created attachment 1217020 [details]
File: anaconda.log

Comment 3 Jiri Konecny 2016-11-03 14:56:58 UTC
Created attachment 1217021 [details]
File: dnf.librepo.log

Comment 4 Jiri Konecny 2016-11-03 14:56:59 UTC
Created attachment 1217022 [details]
File: environ

Comment 5 Jiri Konecny 2016-11-03 14:57:01 UTC
Created attachment 1217023 [details]
File: hawkey.log

Comment 6 Jiri Konecny 2016-11-03 14:57:03 UTC
Created attachment 1217024 [details]
File: lsblk_output

Comment 7 Jiri Konecny 2016-11-03 14:57:06 UTC
Created attachment 1217025 [details]
File: lvm.log

Comment 8 Jiri Konecny 2016-11-03 14:57:07 UTC
Created attachment 1217026 [details]
File: nmcli_dev_list

Comment 9 Jiri Konecny 2016-11-03 14:57:09 UTC
Created attachment 1217027 [details]
File: os_info

Comment 10 Jiri Konecny 2016-11-03 14:57:11 UTC
Created attachment 1217028 [details]
File: program.log

Comment 11 Jiri Konecny 2016-11-03 14:57:14 UTC
Created attachment 1217029 [details]
File: storage.log

Comment 12 Jiri Konecny 2016-11-03 14:57:17 UTC
Created attachment 1217030 [details]
File: syslog

Comment 13 Jiri Konecny 2016-11-03 14:57:18 UTC
Created attachment 1217031 [details]
File: ifcfg.log

Comment 14 Jiri Konecny 2016-11-03 14:57:20 UTC
Created attachment 1217032 [details]
File: packaging.log

Comment 15 Fedora Blocker Bugs Application 2016-11-03 15:07:47 UTC
Proposed as a Freeze Exception for 25-final by Fedora user jkonecny using the blocker tracking app because:

 You can't successful finish installation with RAID1 LVM thinPool pre-created partitioning.

Comment 16 Vratislav Podzimek 2016-11-04 11:28:09 UTC
I'm not able to reproduce this issue with an existing RAID1 thin pool setup. And from the attached output of 'lsblk' it looks like the system was in a very bad shape when this traceback appeared. Thus I'm closing this as WORKSFORME. If anybody hits the issue, feel free to reopen it and provide extra information.