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.
After completing an install using the latest ISO (7.2-2), whereby most defaults were selected, the host is left without an IP address.
During the install, I had used the network spoke to enable networking and the host was assigned an IP address as expected.
After rebooting into the system, the host is left without an IP address.
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 52:54:00:4d:df:30 brd ff:ff:ff:ff:ff:ff
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN
link/ether 02:42:f8:60:9f:3a brd ff:ff:ff:ff:ff:ff
inet 172.17.42.1/16 scope global docker0
valid_lft forever preferred_lft forever
I looked through the contents of 'journalctl' and found these messages related to the 'ens3' interface:
# journalctl | grep ens3
Oct 06 15:53:24 localhost.localdomain NetworkManager[724]: <info> ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-ens3 (6150e941-4d03-42da-88a9-fb2a725b63b1,"ens3")
Oct 06 15:53:24 localhost.localdomain NetworkManager[724]: <info> (ens3): new Ethernet device (carrier: OFF, driver: 'virtio_net', ifindex: 2)
Oct 06 15:53:24 localhost.localdomain NetworkManager[724]: <info> (ens3): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Oct 06 15:53:24 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): ens3: link is not ready
Oct 06 15:53:24 localhost.localdomain NetworkManager[724]: <info> (ens3): link connected
Oct 06 15:53:24 localhost.localdomain NetworkManager[724]: <info> (ens3): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
Note, similar behavior was observed when using a KVM environment or bare-metal.
Additionally, when I repeated the install using the 7.2-1 ISO, this problem did not occur.
It appears that /etc/sysconfig/networking-scripts/ifcfg-ens3 had ONBOOT=no
# cat /etc/sysconfig/network-scripts/ifcfg-ens3
TYPE=Ethernet
BOOTPROTO=dhcp
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=ens3
UUID=6150e941-4d03-42da-88a9-fb2a725b63b1
DEVICE=ens3
ONBOOT=no
Changing ONBOOT=yes and then 'systemctl restart network' resolved the issue.
However, I don't know why ONBOOT=no was configured that way in the first place.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-2284.html
After completing an install using the latest ISO (7.2-2), whereby most defaults were selected, the host is left without an IP address. During the install, I had used the network spoke to enable networking and the host was assigned an IP address as expected. After rebooting into the system, the host is left without an IP address. # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:4d:df:30 brd ff:ff:ff:ff:ff:ff 3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN link/ether 02:42:f8:60:9f:3a brd ff:ff:ff:ff:ff:ff inet 172.17.42.1/16 scope global docker0 valid_lft forever preferred_lft forever I looked through the contents of 'journalctl' and found these messages related to the 'ens3' interface: # journalctl | grep ens3 Oct 06 15:53:24 localhost.localdomain NetworkManager[724]: <info> ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-ens3 (6150e941-4d03-42da-88a9-fb2a725b63b1,"ens3") Oct 06 15:53:24 localhost.localdomain NetworkManager[724]: <info> (ens3): new Ethernet device (carrier: OFF, driver: 'virtio_net', ifindex: 2) Oct 06 15:53:24 localhost.localdomain NetworkManager[724]: <info> (ens3): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Oct 06 15:53:24 localhost.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP): ens3: link is not ready Oct 06 15:53:24 localhost.localdomain NetworkManager[724]: <info> (ens3): link connected Oct 06 15:53:24 localhost.localdomain NetworkManager[724]: <info> (ens3): device state change: unavailable -> disconnected (reason 'none') [20 30 0] Note, similar behavior was observed when using a KVM environment or bare-metal. Additionally, when I repeated the install using the 7.2-1 ISO, this problem did not occur.