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.

Created attachment 492829 [details]
backtrace on i686

Description of problem:

Kickstart network --device command causes sigsegv crash if it is specified with MAC address (contains ':' character) which is not found (e.g. has a typo).

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

RHEL 6.1 0414 nightly
anaconda 13.21-112

How reproducible:

always

Steps to Reproduce:
1. use network --device with valid but not present MAC address
  
Actual results:

crash, backtrace, see the attachment

Additional info:

[rvykydal@dhcp-lab-144 ~/work/tmp]$ eu-addr2line -e usr/lib/debug/usr/lib/anaconda-runtime/loader/loader.debug 
0x805155b
/usr/src/debug/anaconda-13.21.112/loader/loader.c:2246
0x8059e7a
/usr/src/debug/anaconda-13.21.112/loader/kickstart.c:564
0x8068cb2
/usr/src/debug/anaconda-13.21.112/loader/net.c:1749
0x80602c7
/usr/include/bits/stdio2.h:158
0x8063b20
/usr/src/debug/anaconda-13.21.112/loader/net.c:1856

Proposed patch:
http://www.redhat.com/archives/anaconda-devel-list/2011-April/msg00171.html

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

This should be fixed in anaconda-13.21.114-1.

Tested with anaconda-13.21.114-1/0420.n.0 tree. 

There was no crash and after stage2 started anaconda reported a kickstart error:
The provided network interface 00:1C:C4:10:F7:D6 does not exist.

Moving to VERIFIED.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0530.html