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 1855371 - Unable to reclaim disk space if package selection is bigger than disk space
Summary: Unable to reclaim disk space if package selection is bigger than disk space
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.3
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: Jan Stodola
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1812825
TreeView+ depends on / blocked
 
Reported: 2020-07-09 17:03 UTC by Jan Stodola
Modified: 2023-11-14 16:47 UTC (History)
3 users (show)

Fixed In Version: anaconda-33.16.9.3-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2187371 (view as bug list)
Environment:
Last Closed: 2023-11-14 15:32:04 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)
lvm.log (270.94 KB, text/plain)
2020-07-09 17:04 UTC, Jan Stodola 		no flags Details
screnshot (60.95 KB, image/png)
2020-07-09 17:07 UTC, Jan Stodola 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github rhinstaller anaconda pull 4826 0 None open Be more indulgent when reclaiming disk space (#1855371) 2023-06-09 11:47:54 UTC
Red Hat Issue Tracker RTT-5244 0 None None None 2023-05-02 10:42:29 UTC
Red Hat Issue Tracker RTT-5245 0 None None None 2023-05-02 10:42:34 UTC
Red Hat Product Errata RHBA-2023:6957 0 None None None 2023-11-14 15:32:22 UTC

Description Jan Stodola 2020-07-09 17:03:31 UTC 
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).
Comment 2 Jan Stodola 2020-07-09 17:04:37 UTC 
Created attachment 1700470 [details]
lvm.log
Comment 6 Jan Stodola 2020-07-09 17:07:20 UTC 
Created attachment 1700474 [details]
screnshot
Comment 7 Jan Stodola 2020-07-09 17:16:14 UTC 
The same result when using the same disk in a z/VM guest, so this problem is not LPAR specific.
I'm not able to reproduce it with RHEL-8.2 GA.

QE note: This was reproduced on RTT LPAR/z/VM guests with DASD 4009
Comment 8 Jan Stodola 2020-07-09 17:50:08 UTC 
More notes:
1) After re-installing the disk with RHEL-8.2 GA (default partitioning), next installation of RHEL-8.3 successfully reclaimed disk space.
2) After re-installing another z/VM guest with RHEL-7.8 (default partitioning), also using one DASD disk, but with a different size, this problem was also reproducible there (RTT z/VM guest a7, DASD: 3027)
Comment 9 Jan Stodola 2020-07-09 17:53:06 UTC 
Workaround is to go to the Custom partitioning screen, remove existing mount points and let anaconda create the partitions.
Comment 10 Jiri Kortus 2020-08-18 10:17:00 UTC 
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.
Comment 14 RHEL Program Management 2022-01-09 07:26:57 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 15 Jan Stodola 2022-08-08 13:02:20 UTC 
I'm re-opening the bug. BTW, the same problem exists on RHEL-9 as well.
Comment 19 RHEL Program Management 2023-02-08 07:27:45 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 20 Jiri Kortus 2023-02-08 07:56:59 UTC 
I'm reopening the bug as it's still present (RHEL-8.8) and I've been hitting it every now and then during Anaconda testing.
Comment 22 Jan Stodola 2023-02-08 10:17:50 UTC 
Upstream PR: https://github.com/rhinstaller/anaconda/pull/4546
Comment 23 Jan Stodola 2023-04-17 14:04:46 UTC 
Cloned as a RHEL-9 bug 2187371.
Comment 24 Jan Stodola 2023-06-09 11:47:55 UTC 
PR: https://github.com/rhinstaller/anaconda/pull/4826
Comment 26 Daniel Marek 2023-07-12 15:38:24 UTC 
Bug fix had successful pre-verification, setting Verified: Tested.
Comment 29 Daniel Marek 2023-07-17 14:42:20 UTC 
Checked that anaconda-33.16.9.3-1.el8 is in nightly compose RHEL-8.9.0-20230716.29
There's no documentation needed for this bug - not checking
Necessary tests were successful as stated in Comment 26

Moving to VERIFIED
Comment 31 errata-xmlrpc 2023-11-14 15:32:04 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:6957
Note You need to log in before you can comment on or make changes to this bug.