------- Comment From [email protected] 2018-07-23 06:03 EDT------- Configuring Bridge with latest version of netplan is failing again, even after reboot of server. I could see the same error messages that are initially reported in the BUG.
I had following entry in netplan yaml and rebooted the server and could not the bridge interface under ifconfig output. root@ltciofvtr-bostonlc1:~# cat /etc/net netconfig netplan/ netscript/ network/ networks root@ltciofvtr-bostonlc1:~# cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: enP2p1s0f2: addresses: [ 9.47.78.174/20 ] gateway4: 9.47.79.254 nameservers: search: [ pok.stglabs.ibm.com ] addresses: - "9.3.1.200" enP48p1s0f0: dhcp4: no addresses: [ 14.14.14.14/24 ] enP48p1s0f1: dhcp4: no addresses: [ 15.15.15.15/24 ] enP51p1s0f0: dhcp4: no optional: true enP51p1s0f1: dhcp4: no optional: true enP52p1s0f1: dhcp4: no optional: true bridges: br0: interfaces: [ enP52p1s0f1 ] addresses: [ 201.1.1.174/24 ] dhcp4: no # bonds: # bond14: # dhcp4: no # interfaces: [ enP51p1s0f0, enP51p1s0f1 ] # parameters: # mode: balance-xor # primary: enP51p1s0f0 # mii-monitor-interval: 100 # addresses: [ 199.1.1.174/24 ] root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# ifconfig br0 br0: error fetching interface information: Device not found root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# ifconfig enP52p1s0f1 enP52p1s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 24:8a:07:b4:e5:03 txqueuelen 1000 (Ethernet) RX packets 3 bytes 420 (420.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@ltciofvtr-bostonlc1:~# dmessages ================= root@ltciofvtr-bostonlc1:~# dmesg | grep br0 [ 12.812776] IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready [ 12.813665] br0: port 1(enP52p1s0f1) entered blocking state [ 12.813666] br0: port 1(enP52p1s0f1) entered disabled state [ 13.835419] br0: port 1(enP52p1s0f1) entered blocking state [ 13.835421] br0: port 1(enP52p1s0f1) entered forwarding state [ 13.835515] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready [ 17.363001] br0: port 1(enP52p1s0f1) entered disabled state [ 17.364000] br0: port 1(enP52p1s0f1) entered disabled state [ 118.588264] virbr0: port 1(virbr0-nic) entered blocking state [ 118.588268] virbr0: port 1(virbr0-nic) entered disabled state [ 118.588340] device virbr0-nic entered promiscuous mode [ 118.840087] device virbr0-nic left promiscuous mode [ 118.840196] virbr0: port 1(virbr0-nic) entered disabled state root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# netplan --debug apply ** (generate:8844): DEBUG: 05:54:28.780: Processing input file //etc/netplan/01-netcfg.yaml.. ** (generate:8844): DEBUG: 05:54:28.780: starting new processing pass ** (generate:8844): DEBUG: 05:54:28.780: enP48p1s0f1: setting default backend to 1 ** (generate:8844): DEBUG: 05:54:28.780: enP2p1s0f2: setting default backend to 1 ** (generate:8844): DEBUG: 05:54:28.780: enP51p1s0f1: setting default backend to 1 ** (generate:8844): DEBUG: 05:54:28.780: enP51p1s0f0: setting default backend to 1 ** (generate:8844): DEBUG: 05:54:28.780: br0: setting default backend to 1 ** (generate:8844): DEBUG: 05:54:28.780: enP52p1s0f1: setting default backend to 1 ** (generate:8844): DEBUG: 05:54:28.780: enP48p1s0f0: setting default backend to 1 ** (generate:8844): DEBUG: 05:54:28.780: Generating output files.. ** (generate:8844): DEBUG: 05:54:28.780: NetworkManager: definition enP48p1s0f1 is not for us (backend 1) ** (generate:8844): DEBUG: 05:54:28.780: NetworkManager: definition enP2p1s0f2 is not for us (backend 1) ** (generate:8844): DEBUG: 05:54:28.780: NetworkManager: definition enP51p1s0f1 is not for us (backend 1) ** (generate:8844): DEBUG: 05:54:28.780: NetworkManager: definition enP51p1s0f0 is not for us (backend 1) ** (generate:8844): DEBUG: 05:54:28.781: NetworkManager: definition br0 is not for us (backend 1) ** (generate:8844): DEBUG: 05:54:28.781: NetworkManager: definition enP52p1s0f1 is not for us (backend 1) ** (generate:8844): DEBUG: 05:54:28.781: NetworkManager: definition enP48p1s0f0 is not for us (backend 1) DEBUG:netplan generated networkd configuration exists, restarting networkd DEBUG:no netplan generated NM configuration exists DEBUG:replug enP2p1s0f3: unbinding 0002:01:00.3 from /sys/bus/pci/drivers/i40e DEBUG:replug enP2p1s0f3: rebinding 0002:01:00.3 to /sys/bus/pci/drivers/i40e DEBUG:replug enP2p1s0f1: unbinding 0002:01:00.1 from /sys/bus/pci/drivers/i40e DEBUG:replug enP2p1s0f1: rebinding 0002:01:00.1 to /sys/bus/pci/drivers/i40e DEBUG:device enP52p1s0f1 operstate is up, not replugging DEBUG:netplan triggering .link rules for enP52p1s0f1 DEBUG:replug enP49p1s0f2: unbinding 0031:01:00.2 from /sys/bus/pci/drivers/i40e DEBUG:replug enP49p1s0f2: rebinding 0031:01:00.2 to /sys/bus/pci/drivers/i40e DEBUG:replug enP49p1s0f0: unbinding 0031:01:00.0 from /sys/bus/pci/drivers/i40e DEBUG:replug enP49p1s0f0: rebinding 0031:01:00.0 to /sys/bus/pci/drivers/i40e DEBUG:replug enP51p1s0f0: unbinding 0033:01:00.0 from /sys/bus/pci/drivers/mlx5_core DEBUG:replug enP51p1s0f0: rebinding 0033:01:00.0 to /sys/bus/pci/drivers/mlx5_core DEBUG:device enP48p1s0f1 operstate is up, not replugging DEBUG:netplan triggering .link rules for enP48p1s0f1 DEBUG:device enP2p1s0f2 operstate is up, not replugging DEBUG:netplan triggering .link rules for enP2p1s0f2 DEBUG:replug enP49p1s0f3: unbinding 0031:01:00.3 from /sys/bus/pci/drivers/i40e DEBUG:replug enP49p1s0f3: rebinding 0031:01:00.3 to /sys/bus/pci/drivers/i40e DEBUG:device lo operstate is unknown, not replugging DEBUG:netplan triggering .link rules for lo DEBUG:replug enP2p1s0f0: unbinding 0002:01:00.0 from /sys/bus/pci/drivers/i40e DEBUG:replug enP2p1s0f0: rebinding 0002:01:00.0 to /sys/bus/pci/drivers/i40e DEBUG:replug enP52p1s0f0: unbinding 0034:01:00.0 from /sys/bus/pci/drivers/mlx5_core DEBUG:replug enP52p1s0f0: rebinding 0034:01:00.0 to /sys/bus/pci/drivers/mlx5_core DEBUG:replug enP49p1s0f1: unbinding 0031:01:00.1 from /sys/bus/pci/drivers/i40e DEBUG:replug enP49p1s0f1: rebinding 0031:01:00.1 to /sys/bus/pci/drivers/i40e DEBUG:replug enP51p1s0f1: unbinding 0033:01:00.1 from /sys/bus/pci/drivers/mlx5_core DEBUG:replug enP51p1s0f1: rebinding 0033:01:00.1 to /sys/bus/pci/drivers/mlx5_core DEBUG:device enP48p1s0f0 operstate is up, not replugging DEBUG:netplan triggering .link rules for enP48p1s0f0 root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# ifconfig br0 br0: error fetching interface information: Device not found root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# dmesg | grep br0 [ 12.812776] IPv6: ADDRCONF(NETDEV_UP): br0: link is not ready [ 12.813665] br0: port 1(enP52p1s0f1) entered blocking state [ 12.813666] br0: port 1(enP52p1s0f1) entered disabled state [ 13.835419] br0: port 1(enP52p1s0f1) entered blocking state [ 13.835421] br0: port 1(enP52p1s0f1) entered forwarding state [ 13.835515] IPv6: ADDRCONF(NETDEV_CHANGE): br0: link becomes ready [ 17.363001] br0: port 1(enP52p1s0f1) entered disabled state [ 17.364000] br0: port 1(enP52p1s0f1) entered disabled state [ 118.588264] virbr0: port 1(virbr0-nic) entered blocking state [ 118.588268] virbr0: port 1(virbr0-nic) entered disabled state [ 118.588340] device virbr0-nic entered promiscuous mode [ 118.840087] device virbr0-nic left promiscuous mode [ 118.840196] virbr0: port 1(virbr0-nic) entered disabled state [ 1221.701366] br0: port 1(enP52p1s0f1) entered blocking state [ 1221.701369] br0: port 1(enP52p1s0f1) entered disabled state [ 1221.728932] br0: port 1(enP52p1s0f1) entered disabled state root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# ------- Comment From [email protected] 2018-07-23 06:05 EDT------- configuration details ================== root@ltciofvtr-bostonlc1:~# uname -a Linux ltciofvtr-bostonlc1 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:43:33 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic root@ltciofvtr-bostonlc1:~# root@ltciofvtr-bostonlc1:~# dpkg -l | grep -i netplan.io ii netplan.io 0.36.3 ppc64el YAML network configuration abstraction for various backends root@ltciofvtr-bostonlc1:~# dpkg -l | grep -i netplan rc netplan 1.10.1-5build1 ppc64el network server for `plan' ii netplan.io 0.36.3 ppc64el YAML network configuration abstraction for various backends root@ltciofvtr-bostonlc1:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759056 Title: [Ubuntu18.04][Witherspoon DD2.2] netplan fails to configure network bridge interface (tg3/BCM5719) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1759056/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
