[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade
*** This bug is a duplicate of bug 1756846 *** https://bugs.launchpad.net/bugs/1756846 Thanks to the investigation from Steve, it seems that during the dist- upgrade process ifupdown was removed due a transient conflict during the devel cycle. This caused it to be removed. It being removed didn't provide network. So this bug is basically a duplicate of #1756846. 17:21 < slangasek> roaksoax: according to your logs, during that upgrade the ifupdown package was removed (because of a transient conflict during the devel cycle). you do not have the ifupdown package installed. 17:22 < slangasek> roaksoax: reinstalling ifupdown will fix this, and this is basically a duplicate of LP: #1756846 ** This bug has been marked a duplicate of bug 1756846 bridge-utils incompatible with ifupdown on bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1761294 Title: Network configuration doesn't survive reboots after bionic dist- upgrade Status in cloud-init package in Ubuntu: Invalid Status in ifupdown package in Ubuntu: New Status in netplan.io package in Ubuntu: Invalid Bug description: I deployed Xenial in this machine with MAAS. After deployment i had re-configured interfaces manually (on /etc/network/interfaces), and removed /etc/network/interfaces.d. At some point, I upgraded the machine from Xenial to Bionic, and everything was working just fine with /e/n/i. About 2/3 weeks ago, I dist-upgraded bionic for the latest packages, and after reboot, networking didn't come up. To recover the machine, what i did is: 1. From the console, brought up the interfaces manually (eno1) 2. added an IP address manually (ip addr add) 3. Configured netplan and applied the config: network: version: 2 renderer: networkd ethernets: eno1: dhcp4: no dhcp6: no addresses: [192.168.1.13/24] gateway4: 192.168.1.1 nameservers: addresses: [8.8.8.8, 8.8.4.4] usb0: dhcp4: no bridges: br0: interfaces: [usb0] dhcp4: no addresses: [10.90.90.1/24] parameters: stp: false forward-delay: 0 max-age: 0 5. Interfaces dont get configured correctly: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 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 17: eno1: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff inet 192.168.1.13/24 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::eea8:6bff:fefd:ac70/64 scope link valid_lft forever preferred_lft forever 19: usb0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff inet6 fe80::20e:c6ff:fe88:b79f/64 scope link valid_lft forever preferred_lft forever 22: wlp2s0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff 6. on reboot, the machine goes back to have no networking again, at all. Note that I also have /e/n/i configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1761294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade
As per cloud-init networking disabled. Please reopen task if you find cloud-init is in the picture here. ** Changed in: cloud-init (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1761294 Title: Network configuration doesn't survive reboots after bionic dist- upgrade Status in cloud-init package in Ubuntu: Invalid Status in ifupdown package in Ubuntu: New Status in netplan.io package in Ubuntu: Invalid Bug description: I deployed Xenial in this machine with MAAS. After deployment i had re-configured interfaces manually (on /etc/network/interfaces), and removed /etc/network/interfaces.d. At some point, I upgraded the machine from Xenial to Bionic, and everything was working just fine with /e/n/i. About 2/3 weeks ago, I dist-upgraded bionic for the latest packages, and after reboot, networking didn't come up. To recover the machine, what i did is: 1. From the console, brought up the interfaces manually (eno1) 2. added an IP address manually (ip addr add) 3. Configured netplan and applied the config: network: version: 2 renderer: networkd ethernets: eno1: dhcp4: no dhcp6: no addresses: [192.168.1.13/24] gateway4: 192.168.1.1 nameservers: addresses: [8.8.8.8, 8.8.4.4] usb0: dhcp4: no bridges: br0: interfaces: [usb0] dhcp4: no addresses: [10.90.90.1/24] parameters: stp: false forward-delay: 0 max-age: 0 5. Interfaces dont get configured correctly: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 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 17: eno1: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff inet 192.168.1.13/24 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::eea8:6bff:fefd:ac70/64 scope link valid_lft forever preferred_lft forever 19: usb0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff inet6 fe80::20e:c6ff:fe88:b79f/64 scope link valid_lft forever preferred_lft forever 22: wlp2s0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff 6. on reboot, the machine goes back to have no networking again, at all. Note that I also have /e/n/i configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1761294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade
Your config file is apparently named /etc/netplan/netplan.conf, which does not match the required "*.yaml" pattern (which is documented in the netplan(5) manpage and elsewhere). ** Changed in: netplan.io (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1761294 Title: Network configuration doesn't survive reboots after bionic dist- upgrade Status in cloud-init package in Ubuntu: New Status in ifupdown package in Ubuntu: New Status in netplan.io package in Ubuntu: Invalid Bug description: I deployed Xenial in this machine with MAAS. After deployment i had re-configured interfaces manually (on /etc/network/interfaces), and removed /etc/network/interfaces.d. At some point, I upgraded the machine from Xenial to Bionic, and everything was working just fine with /e/n/i. About 2/3 weeks ago, I dist-upgraded bionic for the latest packages, and after reboot, networking didn't come up. To recover the machine, what i did is: 1. From the console, brought up the interfaces manually (eno1) 2. added an IP address manually (ip addr add) 3. Configured netplan and applied the config: network: version: 2 renderer: networkd ethernets: eno1: dhcp4: no dhcp6: no addresses: [192.168.1.13/24] gateway4: 192.168.1.1 nameservers: addresses: [8.8.8.8, 8.8.4.4] usb0: dhcp4: no bridges: br0: interfaces: [usb0] dhcp4: no addresses: [10.90.90.1/24] parameters: stp: false forward-delay: 0 max-age: 0 5. Interfaces dont get configured correctly: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 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 17: eno1: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff inet 192.168.1.13/24 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::eea8:6bff:fefd:ac70/64 scope link valid_lft forever preferred_lft forever 19: usb0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff inet6 fe80::20e:c6ff:fe88:b79f/64 scope link valid_lft forever preferred_lft forever 22: wlp2s0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff 6. on reboot, the machine goes back to have no networking again, at all. Note that I also have /e/n/i configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1761294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade
https://pastebin.ubuntu.com/p/YPRxSrjHZ9/ ** Changed in: netplan.io (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1761294 Title: Network configuration doesn't survive reboots after bionic dist- upgrade Status in cloud-init package in Ubuntu: New Status in ifupdown package in Ubuntu: New Status in netplan.io package in Ubuntu: Invalid Bug description: I deployed Xenial in this machine with MAAS. After deployment i had re-configured interfaces manually (on /etc/network/interfaces), and removed /etc/network/interfaces.d. At some point, I upgraded the machine from Xenial to Bionic, and everything was working just fine with /e/n/i. About 2/3 weeks ago, I dist-upgraded bionic for the latest packages, and after reboot, networking didn't come up. To recover the machine, what i did is: 1. From the console, brought up the interfaces manually (eno1) 2. added an IP address manually (ip addr add) 3. Configured netplan and applied the config: network: version: 2 renderer: networkd ethernets: eno1: dhcp4: no dhcp6: no addresses: [192.168.1.13/24] gateway4: 192.168.1.1 nameservers: addresses: [8.8.8.8, 8.8.4.4] usb0: dhcp4: no bridges: br0: interfaces: [usb0] dhcp4: no addresses: [10.90.90.1/24] parameters: stp: false forward-delay: 0 max-age: 0 5. Interfaces dont get configured correctly: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 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 17: eno1: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff inet 192.168.1.13/24 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::eea8:6bff:fefd:ac70/64 scope link valid_lft forever preferred_lft forever 19: usb0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff inet6 fe80::20e:c6ff:fe88:b79f/64 scope link valid_lft forever preferred_lft forever 22: wlp2s0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff 6. on reboot, the machine goes back to have no networking again, at all. Note that I also have /e/n/i configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1761294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761294] Re: Network configuration doesn't survive reboots after bionic dist-upgrade
> 3. Configured netplan and applied the config: > 5. Interfaces dont get configured correctly: Not sure what happened to 4 ;) But in any case, can you please confirm: - what is the full set of config files under /etc/netplan after boot? - what commands did you run to apply the config, and what was the output? - what are the contents of eni (and /etc/network/interfaces.d) at this point? ** Changed in: netplan.io (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1761294 Title: Network configuration doesn't survive reboots after bionic dist- upgrade Status in cloud-init package in Ubuntu: New Status in ifupdown package in Ubuntu: New Status in netplan.io package in Ubuntu: New Bug description: I deployed Xenial in this machine with MAAS. After deployment i had re-configured interfaces manually (on /etc/network/interfaces), and removed /etc/network/interfaces.d. At some point, I upgraded the machine from Xenial to Bionic, and everything was working just fine with /e/n/i. About 2/3 weeks ago, I dist-upgraded bionic for the latest packages, and after reboot, networking didn't come up. To recover the machine, what i did is: 1. From the console, brought up the interfaces manually (eno1) 2. added an IP address manually (ip addr add) 3. Configured netplan and applied the config: network: version: 2 renderer: networkd ethernets: eno1: dhcp4: no dhcp6: no addresses: [192.168.1.13/24] gateway4: 192.168.1.1 nameservers: addresses: [8.8.8.8, 8.8.4.4] usb0: dhcp4: no bridges: br0: interfaces: [usb0] dhcp4: no addresses: [10.90.90.1/24] parameters: stp: false forward-delay: 0 max-age: 0 5. Interfaces dont get configured correctly: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 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 17: eno1: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether ec:a8:6b:fd:ac:70 brd ff:ff:ff:ff:ff:ff inet 192.168.1.13/24 scope global eno1 valid_lft forever preferred_lft forever inet6 fe80::eea8:6bff:fefd:ac70/64 scope link valid_lft forever preferred_lft forever 19: usb0: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:0e:c6:88:b7:9f brd ff:ff:ff:ff:ff:ff inet6 fe80::20e:c6ff:fe88:b79f/64 scope link valid_lft forever preferred_lft forever 22: wlp2s0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether c4:d9:87:5b:42:62 brd ff:ff:ff:ff:ff:ff 6. on reboot, the machine goes back to have no networking again, at all. Note that I also have /e/n/i configured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1761294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
