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 installing to a boot from SAN target, anaconda faults while examining storage devices. I've also seen this is then 20120508 build.


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


How reproducible: Almost every time. Out of 7 attempts, only one got past this point.


Steps to Reproduce:
1.Install 20120514 on a system that is configured as boot from SAN.

logs attached.

Created attachment 584777 [details]
beaker anaconda log

Created attachment 584778 [details]
beaker console log

Created attachment 584779 [details]
beaker storage log

Created attachment 584780 [details]
beaker sys log

Are you still seeing this with a tree that's using an anaconda-18.X series?

I just tried that latest build (20121022.1.n). We fail much earier in dracut. See attached dracut_console.log

Created attachment 632897 [details]
console log from install of 20121022.1.n tree

I ran this against Snap Shot 2 and I still run into this problem. I have to remove the FC cables to do an install.

So is the problem "anaconda throws an exception and crashes" or "anaconda doesn't start"? Both symptoms have been reported here.

Assuming it's "anaconda doesn't start", as in the log from comment #7: 

For anaconda to start, it needs a "inst.stage2" or "inst.repo" boot argument *or* a kickstart that contains a valid cdrom/nfs/url/harddrive command. 

The console log shows no such boot arguments, but the kickstart URL isn't valid anymore. So I can't really tell what's going on.

Can you please attach the console log and the kickstart from the last failure?

The real problem has been determined to be in LVM. https://bugzilla.redhat.com/show_bug.cgi?id=1042857

We can kill this BZ and use that one.

nobody's seen the original problem in over a year, so...

closed