Bug 2187371

Summary: [RHEL-9] Unable to reclaim disk space if package selection is bigger than disk space
Product: Red Hat Enterprise Linux 9 Reporter: Jan Stodola <jstodola>
Component: anacondaAssignee: Jan Stodola <jstodola>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.2CC: dmarek, jkonecny
Target Milestone: rcKeywords: Patch, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-34.25.3.7-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1855371 Environment:
Last Closed: 2023-11-07 08:32:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Stodola 2023-04-17 14:03:12 UTC
+++ This bug was initially created as a clone of Bug #1855371 +++

Description of problem:
Anaconda doesn't allow to reclaim disk space after marking all existing partitions/disks to delete in the "Reclaim disk space" dialog. The "Reclaim space" button stays inactive. See attached screenshot.
It happens if I use the "Delete all" button as well as when deleting all partitions/disks one by one.

Version-Release number of selected component (if applicable):
RHEL-8.3.0-20200701.2
anaconda-33.16.3.10-1.el8
python3-blivet-3.2.2-3.el8

How reproducible:
Always? 2 out of 2 attempts

Steps to Reproduce:
1. Start vnc installation on a system where RHEL-7 was pre-installed.
The default partitioning layout was created in RHEL-7.
2. Go to the Installation destination spoke - the disk is already selected, so tick reclaiming disk space
3. In the "Reclaim disk space" dialog window click the "Delete all" button
4. Try yo click the "Reclaim space" button

Actual results:
The "Reclaim space" button is inactive

Expected results:
It's possible to click the "Reclaim space" button and reclaim disk space.

Additional info:
So far only reproduced on s390x when installing in LPAR mode. Reproduced with one DASD disk (more DASD disks have not been tested).


--- Additional comment from Jan Stodola on 2020-07-09 19:53:06 CEST ---

Workaround is to go to the Custom partitioning screen, remove existing mount points and let anaconda create the partitions.

--- Additional comment from Jiri Kortus on 2020-08-18 12:17:00 CEST ---

I was just about to file a similar (or actually the same) bug and found this one in a preliminary search. I bumped into the same problem with anabot not being able to reclaim disk space and finish installation, and I wasn't able to complete the task either. On top of that, it also looked like I was trapped in the disk partitioning spoke, the only way to exit to the main hub was to deselect the disk and click on Done (I'm mentioning this for the sake of completeness, as I'm not sure at all if this is a correct behaviour).

I think that this only happens when you first select a package set that requires more space than what can be made available even after removing all of the existing partitions (in my case the selected space to reclaim was 8 GiB, whereas the selected package set required 8.06 GiB). After having a look at the screenshot from Honza, it looks like the same happened in his case. This assumption also proved correct when I switched to a package set with a smaller footprint - in such a case I was able to reclaim the disk space as expected.

I'd say the logical outcome of the aforementioned situation would be to just let the user reclaim the space and after exiting the partitioning spoke display a warning on the bottom of the screen, telling the user that more space is needed for the selected package set.

--- Additional comment from Jan Stodola on 2023-02-08 11:17:50 CET ---

Upstream PR: https://github.com/rhinstaller/anaconda/pull/4546

Comment 2 Jan Stodola 2023-06-09 11:48:23 UTC
PR: https://github.com/rhinstaller/anaconda/pull/4825

Comment 4 Daniel Marek 2023-07-12 14:53:58 UTC
Bug fix had successful pre-verification, setting Verified: Tested.

Comment 7 Daniel Marek 2023-07-17 14:34:09 UTC
Checked that anaconda-34.25.3.7-1.el9 is in nightly compose RHEL-9.3.0-20230715.0
There's no documentation needed for this bug - not checking
Necessary tests were successful as stated in Comment 4.

Moving to VERIFIED

Comment 9 errata-xmlrpc 2023-11-07 08:32:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (anaconda bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6414