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.
Bug 1269264 - Ethernet device changed to 'disconnected' during boot; no network access
Summary: Ethernet device changed to 'disconnected' during boot; no network access
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-06 20:10 UTC by Micah Abbott
Modified: 2015-11-19 10:14 UTC (History)
7 users (show)

Fixed In Version: anaconda-21.48.22.55-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 10:14:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2284 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2015-11-19 09:44:49 UTC

Description Micah Abbott 2015-10-06 20:10:23 UTC 
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.
Comment 2 Micah Abbott 2015-10-06 20:31:30 UTC 
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.
Comment 3 Micah Abbott 2015-10-06 20:35:13 UTC 
The contents of /etc/sysconfig/networking-scripts/ifcfg-ens3 are the same in the 7.2-1 ISO, so I'm not sure what to make of all of this.
Comment 4 Colin Walters 2015-10-06 20:53:58 UTC 
I reproduce this too.
Comment 5 Colin Walters 2015-10-07 13:11:54 UTC 
I downloaded https://download.eng.rdu2.redhat.com/rel-eng/latest-RHEL-7/compose/Server/x86_64/iso/ and got the same symptom.  I'm assuming this is fallout from the 7.2 installer rebase.
Comment 6 Radek Vykydal 2015-10-07 13:29:36 UTC 
I'll look into it.
Comment 7 Radek Vykydal 2015-10-08 11:09:15 UTC 
(In reply to Colin Walters from comment #5)
> I downloaded
> https://download.eng.rdu2.redhat.com/rel-eng/latest-RHEL-7/compose/Server/
> x86_64/iso/ and got the same symptom.  I'm assuming this is fallout from the
> 7.2 installer rebase.

Yeah, seems so, in RHEL 7.1 the NIC activated in GUI would have ONBOOT=yes.

https://github.com/rvykydal/anaconda/commit/117c4c17fffdf10fe5a0781d04f633deaab5d611
Comment 8 Radek Vykydal 2015-10-08 11:19:53 UTC 
https://github.com/rhinstaller/anaconda/pull/395
Comment 12 errata-xmlrpc 2015-11-19 10:14:58 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.