Bug 1881932

Summary: AttributeError: 'BlivetStorageHandler' object has no attribute '_resizable_filesystems'
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: anaconda-maint-list, jkonecny, jonathan, kellin, vanmeeuwen+fedora, vponcova, vtrefny, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:92835d5a5da0f9fd88f55c051f0d790f960df7552b3ba1e0e38e89c8555f9a82;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-23 12:35:59 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: anaconda-tb
none
File: anaconda.log
none
File: dbus.log
none
File: dnf.librepo.log
none
File: environ
none
program.log
none
storage.log
none
syslog none

Description Kamil Páral 2020-09-23 12:21:43 UTC 
Description of problem:
Blivet partitioning crashed on Fedora-Everything-netinst-x86_64-33_Beta-1.3.iso. I created a BIOS boot partition smaller than I wanted, so I tried to resize it. I was testing bug 1881472 and I had the updates.img from bug 1881472 comment 20 applied.

Reproducer:
1. enter Blivet part with a clean disk
2. click Add partition
3. select BIOS boot, make it 1024kB
4. confirm
5. decide you want to make it 2MB
6. right click on the pending biosboot partition (vda1 in my case)
7. select Edit->Resize
8. crash

Version-Release number of selected component:
anaconda-33.25.2

The following was filed automatically by anaconda:
anaconda 33.25.2 exception report
Traceback (most recent call first):
  File "/usr/lib/python3.9/site-packages/blivetgui/communication/client.py", line 176, in remote_call
    raise type(ret.exception)(str(ret.exception) + "\n" + ret.traceback)  # pylint: disable=maybe-no-member
  File "/usr/lib/python3.9/site-packages/blivetgui/blivetgui.py", line 282, in resize_device
    self.client.remote_call("device_resizable", device))
AttributeError: 'BlivetStorageHandler' object has no attribute '_resizable_filesystems'
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/blivetgui/communication/server.py", line 317, in _call_utils_method
    ret = utils_method(*args)
  File "/usr/lib/python3.9/site-packages/blivetgui/blivet_utils.py", line 636, in device_resizable
    elif blivet_device.format.type not in self.resizable_filesystems:
  File "/usr/lib/python3.9/site-packages/blivetgui/blivet_utils.py", line 169, in resizable_filesystems
    if self._resizable_filesystems is None:
AttributeError: 'BlivetStorageHandler' object has no attribute '_resizable_filesystems'


Additional info:
addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-33 quiet inst.updates=https://vtrefny.fedorapeople.org/img/rhbz1881472.img
executable:     /sbin/anaconda
hashmarkername: anaconda
hawkey.log:     INFO Sep-23 12:17:12 === Started libdnf-0.48.0 ===
kernel:         5.8.6-301.fc33.x86_64
product:        Fedora
release:        Fedora release 33 (Thirty Three)
release_type:   pre-release
type:           anaconda
version:        33
Comment 1 Kamil Páral 2020-09-23 12:21:48 UTC 
Created attachment 1716020 [details]
File: anaconda-tb
Comment 2 Kamil Páral 2020-09-23 12:21:51 UTC 
Created attachment 1716021 [details]
File: anaconda.log
Comment 3 Kamil Páral 2020-09-23 12:21:55 UTC 
Created attachment 1716022 [details]
File: dbus.log
Comment 4 Kamil Páral 2020-09-23 12:21:57 UTC 
Created attachment 1716023 [details]
File: dnf.librepo.log
Comment 5 Kamil Páral 2020-09-23 12:22:00 UTC 
Created attachment 1716024 [details]
File: environ
Comment 6 Kamil Páral 2020-09-23 12:23:11 UTC 
Similar problem has been detected:

Blivet partitioning crashed on Fedora-Everything-netinst-x86_64-33_Beta-1.3.iso. I created a BIOS boot partition smaller than I wanted, so I tried to resize it. I was testing bug 1881472 and I had the updates.img from bug 1881472 comment 20 applied.

Reproducer:
1. enter Blivet part with a clean disk
2. click Add partition
3. select BIOS boot, make it 1024kB
4. confirm
5. decide you want to make it 2MB
6. right click on the pending biosboot partition (vda1 in my case)
7. select Edit->Resize
8. crash

addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-E-dvd-x86_64-33 quiet inst.updates=https://vtrefny.fedorapeople.org/img/rhbz1881472.img
hashmarkername: anaconda
hawkey.log:     INFO Sep-23 12:17:12 === Started libdnf-0.48.0 ===
kernel:         5.8.6-301.fc33.x86_64
package:        anaconda-33.25.2
product:        Fedora
reason:         AttributeError: 'BlivetStorageHandler' object has no attribute '_resizable_filesystems'
release:        Fedora release 33 (Thirty Three)
release_type:   pre-release
version:        33
Comment 7 Kamil Páral 2020-09-23 12:24:22 UTC 
Libreport failed during uploading attachments to this report, so I'll upload the rest manually.
Comment 8 Kamil Páral 2020-09-23 12:24:54 UTC 
Created attachment 1716026 [details]
program.log
Comment 9 Kamil Páral 2020-09-23 12:25:00 UTC 
Created attachment 1716027 [details]
storage.log
Comment 10 Kamil Páral 2020-09-23 12:25:08 UTC 
Created attachment 1716028 [details]
syslog
Comment 11 Kamil Páral 2020-09-23 12:32:50 UTC 
I reproduced this bug even with other filesystems, like ext4. You just need to create a new partition and then want to resize it later. However, it only happens to me when I apply updates.img from bug 1881472 comment 20, otherwise it says "pending partitions can't be resized" or something similar.
Comment 12 Vojtech Trefny 2020-09-23 12:35:59 UTC 

*** This bug has been marked as a duplicate of bug 1881234 ***