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 1042722 - in rescue mode, when exiting rescue shell, get "Pane is dead"
Summary: in rescue mode, when exiting rescue shell, get "Pane is dead"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Vratislav Podzimek
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 08:26 UTC by Adam Williamson
Modified: 2014-06-18 01:46 UTC (History)
4 users (show)

Fixed In Version: anaconda-19.31.40-1
Doc Type: Bug Fix
Doc Text:
Clone Of: 1038855
Environment:
Last Closed: 2014-06-13 09:54:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2013-12-13 08:26:22 UTC
+++ This bug was initially created as a clone of Bug #1038855 +++

Description of problem:
With 20 Final TC4 and TC5, when using rescue mode and exiting rescue shell, instead of the menu, you get "Pane is dead". Other than that, rescue mode still works. This worked normally prior to TC4.

Version-Release number of selected component (if applicable):
anaconda-20.25.13-1 and anaconda-20.25.14-1

How reproducible:
always

Comment 1 Adam Williamson 2013-12-13 08:28:01 UTC
This is reproducible in RHEL 7 public beta just as described. Bit odd since it only showed up recently in F20 testing and RHEL 7 anaconda is a 19 branch, but hey. Definitely happens, reproduced twice.

Comment 5 Ľuboš Kardoš 2014-02-04 10:48:58 UTC
I tested on anaconda-19.31.51-1 (RHEL-7.0-20140127.0). After exiting from rescue shell the message "Pane is dead" is not showed but system is rebooted instead of showing rescue menu. After exiting rescue shell it is expected that anaconda will show rescue menu. This is written in description of this bug so I move this bug back to assigned.

Comment 6 Vratislav Podzimek 2014-02-04 11:26:01 UTC
No matter what the description of this bug says the screen right before the shell starts says following:
"The system will reboot automatically when you exit from the shell."

Which is what happens. Please file another bug if you think this behaviour should be changed. But the behaviour is the same as was in the RHEL 6. Changing summary and moving back to ON_QA.

Comment 7 Ľuboš Kardoš 2014-02-04 11:32:43 UTC
In that case I move this bug to verified. Verified on anaconda-19.31.51-1 (RHEL-7.0-20140127.0).

Comment 8 Ludek Smid 2014-06-13 09:54:10 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


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