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 1027188 - anaconda crash while going through partitioning
Summary: anaconda crash while going through partitioning
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-06 10:56 UTC by Karel Volný
Modified: 2013-12-16 20:24 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-16 20:24:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
anaconda crash log 1 (223.96 KB, application/tar)
2013-11-06 10:56 UTC, Karel Volný
no flags Details
anaconda crash log 2 (224.31 KB, application/tar)
2013-11-06 10:58 UTC, Karel Volný
no flags Details

Description Karel Volný 2013-11-06 10:56:50 UTC
Created attachment 820288 [details]
anaconda crash log 1

Description of problem:
I've set up the installation as desired. Then I've accidentally clicked on the disk selection. I wanted to get back by hitting the Done button, but it didn't let me. So I've chosen the disk to install to and tried to get Done again. Now I don't exactly remember if I got the error right after that or after closing the popup window, I got distracted by the reporting procedure :-/

Version-Release number of selected component (if applicable):
19.31.32-1

How reproducible:
totally random

Steps to Reproduce:
1. mess around with disk settings (and possibly other)

Actual results:
crash, see the attachmets

Expected results:
no problems

Additional info:
if that matters, I've installed over previous install - completely removing partitioning, then autocreating disk layout, then removing /home and enlarging / to the rest of the disk

Comment 1 Karel Volný 2013-11-06 10:58:26 UTC
Created attachment 820289 [details]
anaconda crash log 2

I saved two reports from anaconda - after saving the first, I got the crash report again, these seem to differ a bit ... then I got crash report again, but I have chosen not to store anything else

Comment 3 David Cantrell 2013-12-16 20:24:44 UTC
Please retry using RHEL 7.0 Beta at least.  I have tried to recreate what you described, but there are too many questions.  If you can provide an exact reproducer and a specific error, feel free to reopen the bug.


Note You need to log in before you can comment on or make changes to this bug.