Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When selecting a disk during installation which does not meet the requirements of the auto partitioning, then the installation can not be started, because the error messgae is: "No disk selected"
This is false, because there was a disk selected, but the disk was to small
Version-Release number of selected component (if applicable):
4.0-snapshot
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Please attach the logs from the failure to this bug as individual, text/plain attachments.
Please also provide the steps you took to reproduce this issue. Is this a kickstart install or interactive? Did you hit done in the installation destination spoke, or did you use the automatic partitioning button in the custom partitioning spoke? Did you see the no space dialog? ("You don't have enough space available to install %(product)s, even if you used all of the free space available on the selected disks.")
(In reply to Fabian Deutsch from comment #4)
> I sadly don't recall the details.
>
> Chen, did you run into this bug and can provide the reproducer steps?
Sure.
Test version:
RHVH-4.0-20160822.8-RHVH-x86_64-dvd1.iso
Test steps:
1. Prepare a small disk(e.g. 5G)
2. Anaconda interactive install RHVH via ISO.
3. Enter disk selection page.
4. Select the small disk and automatically configure partitioning.(see attachment "5G-disk2").
5. Save.
6. Focus on "Installation Summary" page. (see attachment "5G-disk2").
Test result:
There was a disk selected, but the disk was to small, but anaconda report "No disk selected".
(In reply to Sandro Bonazzola from comment #15)
> Ying can you check if this is still happening in latest RHV-H builds?
I will provide test result in here later.
(In reply to cshao from comment #17)
> (In reply to Sandro Bonazzola from comment #15)
> > Ying can you check if this is still happening in latest RHV-H builds?
>
> I will provide test result in here later.
Test version:
RHVH-4.2-20181121.1-RHVH-x86_64-dvd1.iso
Test steps:
1. Prepare a small disk(e.g. 5G)
2. Anaconda interactive install RHVH via ISO.
3. Enter disk selection page.
4. Select the small disk and automatically configure partitioning.
5. Save.
Test result:
There was a disk selected, but an unknown error has occurred after save partition configure.(see attachment: RHVH42-small-disk-error)
It's acceptable from my point of view.
Comment 20Samantha N. Bueno
2019-03-05 12:13:42 UTC
Based on c#18 and after talking with Sandro, I'm going to close this since this seems acceptable now. Please re-open if you feel the issue was not resolved.