** Description changed: [Impact] This release contains a regression bug-fix for un-breaking the ABI compatibility between libnetplan 0.102 and netplan.io 0.101, which was taken from a pending upstream pull request: https://github.com/canonical/netplan/pull/206 (d/patches/fix-lp1922898) [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each release. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan.io package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. Additionally, we want to manually verify the ABI compatibility (i.e. not SEGFAULT) between the new libnetplan and the old netplan.io "generate" binary, with the steps described below: * Have netplan 0.101 installed * Upgrade ONLY libnetplan0 to 0.102 $ cat /etc/netplan/00-config.yaml network: - ethernets: - ens5: - dhcp4: true - dhcp6: false - match: - macaddress: 06:f8:32:e5:34:28 - set-name: ens5 - version: 2 + ethernets: + ens5: + dhcp4: true + dhcp6: false + match: + macaddress: 06:f8:32:e5:34:28 + set-name: ens5 + version: 2 $ /usr/lib/netplan/generate * Make sure the "generate" binary did not crash. [Where problems could occur] Netplan being a core package it could impact the whole networking stack of the operating system up to the point where servers would not be reachable anymore after a reboot, due to broken network config being generated by netplan at bootup. In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. Additionally, this SRU needs to drop the "Added ttl option for tunnels (LP: #1846783)" feature, added during the 0.102/Hirsute development cycle. So users of the -devel series using the new "tunnels.ttl" setting are going to miss this until it is re-implemented in an ABI preserving way. Hirsute (Bileto pre-test): https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/amd64/n/netplan.io/20210416_204928_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/arm64/n/netplan.io/20210416_213837_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/armhf/n/netplan.io/20210416_201636_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/ppc64el/n/netplan.io/20210416_210302_fec70@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute-ci-train-ppa-service-4530/hirsute/s390x/n/netplan.io/20210416_204523_fec70@/log.gz Groovy: TBD groovy_amd64.log TBD groovy_arm64.log TBD groovy_armhf.log TBD groovy_ppc64el.log TBD groovy_s390x.log Focal: - TBD focal_amd64.log - TBD focal_arm64.log - TBD focal_armhf.log - TBD focal_ppc64el.log - TBD focal_s390x.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_amd64.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_arm64.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_armhf.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_ppc64el.log + https://git.launchpad.net/~slyon/+git/files/tree/LP1922898/focal_s390x.log [Other Info] The integration test logs are attached to this bug, once the package has been accepted into -proposed and the tests have been executed on the real infrastructure. == Original description == Today a bunch of our ubuntu 20.04 servers on AWS EC2 (both amd64 and arm) upgraded to netplan 0.102-0ubuntu1~20.04.1, which resulted in a segfault when netplan ran generate, and then took the whole network down with it, the servers had to be force rebooted. kernel: [1938106.074273] netplan[2874371]: segfault at 100000000 ip 00007f72cb991675 sp 00007ffe8be03158 error 4 in libc-2.31.so[7f72cb82b000+178000] kernel: [1938106.074282] Code: 00 00 0f 1f 00 31 c0 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 89 f9 48 89 fa c5 f9 ef c0 83 e1 3f 83 f9 20 77 2b <c5> fd 74 0f c5 fd d7 c1 85 c0 0f 85 eb 00 00 00 48 83 c7 20 83 e1 systemd[2874368]: /usr/lib/systemd/system-generators/netplan terminated by signal SEGV. /etc/netplan/ is the default from aws ubuntu 20.04 image.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922898 Title: [SRU] SEGFAULT on upgrade to 0.102-0ubuntu1~20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1922898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
