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.
RHEL7's anaconda boot parameter "asknetwork" is deprecated. Due to this, those people who have experience using virt-install to create RHEL5 or RHEL6 guests on a DHCP-less network are bewildered why a RHEL7 guest fails to install. (See <https://access.redhat.com/solutions/511263> for the answer.)
A user that has experienced this problem would like to see Chapter 3.2 of the _Virtualization Deployment And Administration Guide_ changed to include a 3.2.z section centered around RHEL7 guests under different network configurations. This section would include 3 examples of installing RHEL7 guests using virt-install when:
1. using libvirtd's NAT virtual network switch. The virt-install command would specify either "--network=default" or leave the "--network" option off since it defaults to the default virbr0 network. The command would also possibly include '--extra-args="ip=dhcp"', though that is the default if not explicitly set.
2. using an external DHCP server if by specifying the host's bridge interface. This example would have to inform the reader about the need to setup a br0 interface with the host's eth0 interface as a slave. The virt-install command would specify "--network=br0" and possibly '--extra-args="ip=dhcp"'. (The user also suggested linking to RHEL7's DHCP networking guide -- specifically <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-dhcp-configuring-server.html> -- for readers who want to know how to setup an external DHCP server. That may be extraneous, but will let the documentation folks decide.)
3. using an external static IPv4 address. This example would have to inform the reader about the need to setup a br0 interface with the host's eth0 interface as a slave. The virt-install command would specify "--network=br0" and '--extra-args="ip=<ip>::<gateway>:<netmask>:<hostname>:<interface>:<autoconf>"'. It would probably be good to give an real-value example like "ip=192.168.1.2::192.168.1.1:255.255.255.0:test.example.com:eth0:none" so the reader knows for sure what kind of values to put in.