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 buliding a server with a Kickstart file and the RPMs on a different server, the boot.iso only allows NetworkManager to try DHCP to configure the interface. There's no option to manually configure the interface.
Version-Release number of selected component (if applicable):
6.1 Beta
How reproducible:
Try to boot and point to an external Kickstart file source
Actual results:
NetworkManager tries to configure the interface via DHCP.
Expected results:
Option to manually configure interface with IP and Network information.
Additional info:
This is kind of a show stopper for installing 6.1.
Comment 2RHEL Program Management
2011-04-06 16:44:26 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
(In reply to comment #3)
> Description of problem:
>
> When buliding a server with a Kickstart file and the RPMs on a different
> server, the boot.iso only allows NetworkManager to try DHCP to configure the
> interface. There's no option to manually configure the interface.
Hi Leam,
To make sure I am understanding the problem properly, are you only seeing the bad behavior when using distinct servers for the kickstart file versus the product repos? (ie kernel parameters something like this:
linux ks=http://serverA/ks.cfg repo=http://serverB/path/to/repos
Or does your kernel command line/ks.cfg data look differently ...?
Best Regards,
Brock
Interesting...so far that works. However, it also seems to cause an issue if the Kickstart file as a network configuration line. For example,
network --device eth0 --bootproto static --ip 192.168.1.250 --netmask 255.255.255.0 --hostname mynewserver
Even taking out the --device, --ip, and --netmask stuff it fails. Which means we'll have to manually set the hostname configuration info once the server is built.