Bug 2087642

Summary: [abrt] blivet-gui-runtime: commit(): blivetgui.py:243:_reraise_exception:_ped.IOException: Échec de l’exécution des actions :
Product: [Fedora] Fedora Reporter: Nicolas Sapa <redhat>
Component: blivet-guiAssignee: Vojtech Trefny <vtrefny>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: mkolman, vtrefny
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9920ddc7487a1fb77d70ddb6b68301ebd9a3a047
Whiteboard: abrt_hash:f4804459e1eb6209898724ef9b60b66749ae6d7b;VARIANT_ID=matecompiz;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 18:00:50 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:
Attachments:
Description Flags
File: backtrace
none
File: blivet-gui-utils.log
none
File: blivet.log
none
File: cpuinfo
none
File: environ
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: program.log none

Description Nicolas Sapa 2022-05-18 06:48:59 UTC 
Description of problem:
I had an USB Key that contained System Rescue CD.
I've set the following actions:
- delete the system rescue cd partition
- create a new MBR
- create a new NTFS partition with label Data

Blivert crashed after deleted the system rescue partition.

Version-Release number of selected component:
blivet-gui-runtime-2.3.0-3.fc35

Additional info:
reporter:       libreport-2.15.2
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-glib-blivet\x2dgui-174195.scope
cmdline:        /usr/bin/python3 /usr/bin/blivet-gui
crash_function: commit
exception_type: _ped.IOException
executable:     /usr/bin/blivet-gui
interpreter:    python3-3.10.4-1.fc35.i686
kernel:         5.17.6-200.fc35.x86_64
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
#1 [/usr/lib64/python3.10/site-packages/parted/disk.py:212] commit
#2 [/usr/lib64/python3.10/site-packages/parted/decorators.py:42] new
#3 [/usr/lib/python3.10/site-packages/blivet/formats/disklabel.py:367] commit
#4 [/usr/lib/python3.10/site-packages/blivet/threads.py:53] run_with_lock
#5 [/usr/lib/python3.10/site-packages/blivet/formats/disklabel.py:360] _create
#6 [/usr/lib/python3.10/site-packages/blivet/threads.py:53] run_with_lock
#7 [/usr/lib/python3.10/site-packages/blivet/formats/__init__.py:517] create
#8 [/usr/lib/python3.10/site-packages/blivet/threads.py:53] run_with_lock
#9 [/usr/lib/python3.10/site-packages/blivet/deviceaction.py:662] execute
#10 [/usr/lib/python3.10/site-packages/blivet/threads.py:53] run_with_lock
Comment 1 Nicolas Sapa 2022-05-18 06:49:01 UTC 
Created attachment 1880700 [details]
File: backtrace
Comment 2 Nicolas Sapa 2022-05-18 06:49:02 UTC 
Created attachment 1880701 [details]
File: blivet-gui-utils.log
Comment 3 Nicolas Sapa 2022-05-18 06:49:03 UTC 
Created attachment 1880702 [details]
File: blivet.log
Comment 4 Nicolas Sapa 2022-05-18 06:49:04 UTC 
Created attachment 1880703 [details]
File: cpuinfo
Comment 5 Nicolas Sapa 2022-05-18 06:49:05 UTC 
Created attachment 1880704 [details]
File: environ
Comment 6 Nicolas Sapa 2022-05-18 06:49:06 UTC 
Created attachment 1880705 [details]
File: mountinfo
Comment 7 Nicolas Sapa 2022-05-18 06:49:07 UTC 
Created attachment 1880706 [details]
File: namespaces
Comment 8 Nicolas Sapa 2022-05-18 06:49:08 UTC 
Created attachment 1880707 [details]
File: open_fds
Comment 9 Nicolas Sapa 2022-05-18 06:49:09 UTC 
Created attachment 1880708 [details]
File: program.log
Comment 10 Nicolas Sapa 2022-05-18 06:54:12 UTC 
I've found the issue: one partition was still mounted
│ ├─/run/media/nico/RESCUE902  /dev/sdb1   iso9660      ro,nosuid,nodev,relatime,nojoliet,check=s,map=n,blocksize=2048,uid=1000,gid=

Blivet should probably check if a volume is mounted before doing anything on a disk.
Comment 11 Ben Cotton 2022-11-29 18:55:09 UTC 
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 12 Ben Cotton 2022-12-13 18:00:50 UTC 
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.