Bug 1610202

Summary: [nfp]modify the config about network-scripts , restart network faild sometimes
Product: Red Hat Enterprise Linux 7 Reporter: Fei Liu <feliu>
Component: initscriptsAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: initscripts-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-15 07:41:05 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:

Description Fei Liu 2018-07-31 07:56:33 UTC
Description of problem:
[nfp]modify the config about network-scripts , restart network faild sometime

Version-Release number of selected component (if applicable):
[root@hp-dl380g9-01 network-scripts]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.6 Beta (Maipo)
[root@hp-dl380g9-01 network-scripts]# uname -a
Linux hp-dl380g9-01.rhts.eng.pek2.redhat.com 3.10.0-924.el7.x86_64 #1 SMP Mon Jul 16 13:57:23 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:
some times

Steps to Reproduce:
[root@hp-dl380g9-01 network-scripts]# cat ifcfg-ens2np0
DEVICE=ens2np0
TYPE=Ethernet
ONBOOT=yes
BRIDGE=br0
BOOTPROTO=none
NM_CONTROLLED=no
[root@hp-dl380g9-01 network-scripts]# 
[root@hp-dl380g9-01 network-scripts]# cat ifcfg-br0 
DEVICE=br0
ONBOOT=yes
BOOTPROTO=dhcp
TYPE=Bridge
NM_CONTROLLED=no
[root@hp-dl380g9-01 network-scripts]# service network restart
Restarting network (via systemctl):  
[  OK  ]
[root@hp-dl380g9-01 network-scripts]# service network restart
Restarting network (via systemctl):  
Job for network.service failed because the control process exited with error code. See "systemctl status network.service" and "journalctl -xe" for details.
[root@hp-dl380g9-01 network-scripts]# systemctl status network.service
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2018-07-31 03:40:55 EDT; 17s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 21849 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS)
  Process: 22258 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)

Jul 31 03:40:48 hp-dl380g9-01.rhts.eng.pek2.redhat.com network[22258]: Bringing up interface eno1:  Connection successfully activated (D-B...n/28)
Jul 31 03:40:48 hp-dl380g9-01.rhts.eng.pek2.redhat.com network[22258]: [  OK  ]
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com network[22258]: Bringing up interface ens2np0:  [  OK  ]
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com network[22258]: Bringing up interface br0:
Jul 31 03:40:55 hp-dl380g9-01.rhts.eng.pek2.redhat.com network[22258]: Determining IP information for br0... failed; no link present.  Che...able?
Jul 31 03:40:55 hp-dl380g9-01.rhts.eng.pek2.redhat.com network[22258]: [FAILED]
Jul 31 03:40:55 hp-dl380g9-01.rhts.eng.pek2.redhat.com systemd[1]: network.service: control process exited, code=exited status=1
Jul 31 03:40:55 hp-dl380g9-01.rhts.eng.pek2.redhat.com systemd[1]: Failed to start LSB: Bring up/down networking.
Jul 31 03:40:56 hp-dl380g9-01.rhts.eng.pek2.redhat.com systemd[1]: Unit network.service entered failed state.
Jul 31 03:40:56 hp-dl380g9-01.rhts.eng.pek2.redhat.com systemd[1]: network.service failed.


[root@hp-dl380g9-01 network-scripts]# journalctl -xe
Jul 31 03:40:48 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: nfp 0000:0b:00.0 ens2np0: RV21: irq=170/023
Jul 31 03:40:48 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: nfp 0000:0b:00.0 ens2np0: RV22: irq=171/024
Jul 31 03:40:48 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: nfp 0000:0b:00.0 ens2np0: RV23: irq=172/025
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: IPv6: ADDRCONF(NETDEV_UP): ens2np0: link is not ready
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com nm-dispatcher[21990]: req:4 'connectivity-change': start running ordered scripts...
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: br0: port 1(ens2np0) entered blocking state
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: br0: port 1(ens2np0) entered disabled state
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: device ens2np0 entered promiscuous mode
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com NetworkManager[2192]: <info>  [1533022850.3417] device (ens2np0): released from master devi
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com network[22258]: Bringing up interface ens2np0:  [  OK  ]
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com NetworkManager[2192]: <info>  [1533022850.3528] policy: set 'eno1' (eno1) as default for IP
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com network[22258]: Bringing up interface br0:
Jul 31 03:40:50 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready
Jul 31 03:40:53 hp-dl380g9-01.rhts.eng.pek2.redhat.com chronyd[993]: Selected source 10.5.26.10
Jul 31 03:40:55 hp-dl380g9-01.rhts.eng.pek2.redhat.com network[22258]: Determining IP information for br0... failed; no link present.  Check cable
Jul 31 03:40:55 hp-dl380g9-01.rhts.eng.pek2.redhat.com network[22258]: [FAILED]
Jul 31 03:40:55 hp-dl380g9-01.rhts.eng.pek2.redhat.com systemd[1]: network.service: control process exited, code=exited status=1
Jul 31 03:40:55 hp-dl380g9-01.rhts.eng.pek2.redhat.com systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit network.service has failed.
-- 
-- The result is failed.
Jul 31 03:40:56 hp-dl380g9-01.rhts.eng.pek2.redhat.com systemd[1]: Unit network.service entered failed state.
Jul 31 03:40:56 hp-dl380g9-01.rhts.eng.pek2.redhat.com systemd[1]: network.service failed.
Jul 31 03:40:56 hp-dl380g9-01.rhts.eng.pek2.redhat.com polkitd[1003]: Unregistered Authentication Agent for unix-process:21843:220337 (system bus 
Jul 31 03:40:57 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: nfp 0000:0b:00.0 ens2np0: NIC Link is Up
Jul 31 03:40:57 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: IPv6: ADDRCONF(NETDEV_CHANGE): ens2np0: link becomes ready
Jul 31 03:40:57 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: br0: port 1(ens2np0) entered blocking state
Jul 31 03:40:57 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: br0: port 1(ens2np0) entered forwarding state
Jul 31 03:40:57 hp-dl380g9-01.rhts.eng.pek2.redhat.com kernel: IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready
Jul 31 03:40:57 hp-dl380g9-01.rhts.eng.pek2.redhat.com NetworkManager[2192]: <info>  [1533022857.2345] device (ens2np0): carrier: link connected
Jul 31 03:40:57 hp-dl380g9-01.rhts.eng.pek2.redhat.com NetworkManager[2192]: <info>  [1533022857.2350] device (br0): carrier: link connected

[root@hp-dl380g9-01 network-scripts]# ethtool -i ens2np0
driver: nfp
version: 3.10.0-924.el7.x86_64 SMP mod_u
firmware-version: 0.0.3.5 0.22 nic-2.0.7 nic
expansion-rom-version: 
bus-info: 0000:0b:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
[root@hp-dl380g9-01 network-scripts]# lspci -s 0b:00.0
0b:00.0 Ethernet controller: Netronome Systems, Inc. Device 4000

refer to job/case
https://beaker.engineering.redhat.com/jobs/2626243
/kernel/netwoking/bridge/setup_bridge

Actual results:
sometimes restart network failed

Expected results:
restart network success always

Additional info:

Comment 2 Fei Liu 2018-07-31 08:00:27 UTC
update error


refer to job
https://beaker.engineering.redhat.com/jobs/2626243

refer to case 
/kernel/networking/bridge/setup_bridge

Comment 6 RHEL Program Management 2021-02-15 07:41:05 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.