Bug 1269264
| Summary: | Ethernet device changed to 'disconnected' during boot; no network access | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Micah Abbott <miabbott> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | atodorov, lmiksik, mjenner, pholica, rvykydal, sgraf, walters |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | anaconda-21.48.22.55-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 10:14:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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. 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. I reproduce this too. 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. I'll look into it. (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 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.