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 822449 - Anaconda exits abnormally while installing RHEL6.3 Snapshot4 as 32bit Xen PV guest
Summary: Anaconda exits abnormally while installing RHEL6.3 Snapshot4 as 32bit Xen PV ...
Keywords:
Status: CLOSED DUPLICATE of bug 822697
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-17 11:35 UTC by Yuyu Zhou
Modified: 2012-05-18 14:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-18 14:24:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screen shot (27.28 KB, image/png)
2012-05-17 11:35 UTC, Yuyu Zhou
no flags Details
anaconda log (3.35 KB, text/plain)
2012-05-17 11:36 UTC, Yuyu Zhou
no flags Details

Description Yuyu Zhou 2012-05-17 11:35:05 UTC
Description of problem:
RHEL6.3 Snapshot4 -- RHEL6.3-20120516.0(as 32bit Xen PV guest in RHEL5.9) fails to install after running anaconda .

Version-Release number of selected component (if applicable):
guest:
RHEL6.0-20120516.0
anaconda-13.21.173-1.el6
host:
xen-3.0.3-139.el5
kernel-xen-2.6.18-318.el5

How reproducible:
Every time

Steps to Reproduce:
1. Install RHEL6.2 snapshot4 as 32bit Xen Paravirtualized guest via virt-manager, using network install tree:
http://download.devel.redhat.com/rel-eng/RHEL-6.3-Snapshot-4/6.3/Server/i386/os/

Actual results: (screenshot attached)
SELinux: Could not load policy file /etc/selinux/targeted/policy/policy.24: Invalid argument
/sbin/load_policy: Can't load policy: Invalid argument

Running anaconda 13.21.173, the Red Hat Enterprise Linux system installer - please wait.
Anaconda died after receiving signal 6.
Install exited abnormally [1/1]

Expected results:
Install should go ahead smoothly.

Additional info:
1. Rhel 6.3 Snapshot3(anaconda-13.21.171-1.el6) can be installed as 32bit Xen PV guest successfully.
2. Rhel 6.3 Snapshot4 can be installed as 64bit Xen PV guest, 32bit Xen HVM guest, 64bit Xen HVM guest successfully.
3. anaconda log attached.
4. The anaconda fail still be reproduce with "selinux=0" kernel parameter

Comment 1 Yuyu Zhou 2012-05-17 11:35:44 UTC
Created attachment 585193 [details]
screen shot

Comment 2 Yuyu Zhou 2012-05-17 11:36:10 UTC
Created attachment 585194 [details]
anaconda log

Comment 5 Lei Wang 2012-05-18 02:23:26 UTC
typo in description: s/RHEL6.0-20120516.0/RHEL6.3-20120516.0

Comment 6 Andrew Jones 2012-05-18 08:36:54 UTC
The selinux logs are probably unrelated. This is likely a dup of bug 822697

Comment 7 Chris Lumens 2012-05-18 14:24:01 UTC

*** This bug has been marked as a duplicate of bug 822697 ***


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