Bug 1855371
| Summary: | Unable to reclaim disk space if package selection is bigger than disk space | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Jan Stodola <jstodola> | ||||||
| Component: | anaconda | Assignee: | Jan Stodola <jstodola> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 8.3 | CC: | dmarek, jikortus, jkonecny | ||||||
| Target Milestone: | rc | Keywords: | Patch, Reopened, Triaged | ||||||
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
||||||
| Hardware: | Unspecified | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | anaconda-33.16.9.3-1.el8 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 2187371 (view as bug list) | Environment: | |||||||
| Last Closed: | 2023-11-14 15:32:04 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1812825 | ||||||||
| Attachments: |
|
||||||||
|
Description
Jan Stodola
2020-07-09 17:03:31 UTC
Created attachment 1700470 [details]
lvm.log
Created attachment 1700474 [details]
screnshot
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 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) Workaround is to go to the Custom partitioning screen, remove existing mount points and let anaconda create the partitions. 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. 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. I'm re-opening the bug. BTW, the same problem exists on RHEL-9 as well. 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. 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. Upstream PR: https://github.com/rhinstaller/anaconda/pull/4546 Cloned as a RHEL-9 bug 2187371. Bug fix had successful pre-verification, setting Verified: Tested. 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 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 |