Activity log for bug #1949104

Date Who What changed Old value New value Message
2021-10-28 16:44:49 Stefan Greiner bug added bug
2021-10-29 08:05:04 Launchpad Janitor netplan.io (Ubuntu): status New Confirmed
2021-11-02 09:45:45 Carlos sola bug added subscriber Carlos sola
2021-11-02 09:47:53 Carlos sola netplan.io (Ubuntu): status Confirmed New
2021-11-02 09:47:56 Carlos sola netplan.io (Ubuntu): status New Confirmed
2021-11-03 15:28:49 Lukas Märdian netplan.io (Ubuntu): status Confirmed Triaged
2021-11-04 08:51:22 Lukas Märdian tags regression-update
2021-11-04 08:51:33 Lukas Märdian nominated for series Ubuntu Impish
2021-11-04 08:51:33 Lukas Märdian bug task added netplan.io (Ubuntu Impish)
2021-11-04 08:51:33 Lukas Märdian nominated for series Ubuntu Focal
2021-11-04 08:51:33 Lukas Märdian bug task added netplan.io (Ubuntu Focal)
2021-11-04 08:51:33 Lukas Märdian nominated for series Ubuntu Jammy
2021-11-04 08:51:33 Lukas Märdian bug task added netplan.io (Ubuntu Jammy)
2021-11-04 08:51:33 Lukas Märdian nominated for series Ubuntu Hirsute
2021-11-04 08:51:33 Lukas Märdian bug task added netplan.io (Ubuntu Hirsute)
2021-11-04 08:52:09 Lukas Märdian tags regression-update regression-update rls-jj-incoming
2021-11-04 15:14:22 Matthieu Clemenceau tags regression-update rls-jj-incoming fr-1833 regression-update rls-jj-incoming
2021-11-04 15:53:41 Brian Murray tags fr-1833 regression-update rls-jj-incoming fr-1833 regression-update
2021-11-05 00:36:24 Launchpad Janitor netplan.io (Ubuntu Focal): status New Confirmed
2021-11-05 00:36:24 Launchpad Janitor netplan.io (Ubuntu Hirsute): status New Confirmed
2021-11-05 00:36:24 Launchpad Janitor netplan.io (Ubuntu Impish): status New Confirmed
2021-11-05 15:06:15 Lukas Märdian description I hava a freshly installed Ubuntu Server 20.04 LTS. I am using a static IP config (100% sure it is correct, also the YAML is correct) If you then enter "netplan try" I get this: -------------------------------------------------------------------------------- Warning: Stopping systemd-networkd.service, but it can still be activated by: systemd-networkd.socket An error occurred: 'NetplanApply' object has no attribute 'state' Reverting. Warning: Stopping systemd-networkd.service, but it can still be activated by: systemd-networkd.socket -------------------------------------------------------------------------------- "netplan generate && netplan apply" does work. I found some other people having these issues too on freshly installed 20.04 and 21.10 and online forums. System Infos: lsb_release -rd: Description: Ubuntu 20.04.3 LTS Release: 20.04 apt-cache policy netplan.io: netplan.io: Installed: 0.103-0ubuntu5~20.04.2 Candidate: 0.103-0ubuntu5~20.04.2 Version table: *** 0.103-0ubuntu5~20.04.2 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.99-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages systemd --version: systemd 245 (245.4-4ubuntu3.13) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Thank you! [Impact] The last netplan SRU (0.103-0ubuntu5~20.04.2) introduced a state tracking feature, that regressed the 'netplan try' CLI command, if no such --state argument is passed, making it fail with a error message like this: An error occurred: 'NetplanApply' object has no attribute 'state' This upload contains a fix to properly initialize the 'self.state' attribute in all cases to avoid this problem. [Test Plan] In addition to runing & passing the full set of unit- and integration-tests (that contains new tests to check for this regression), as described in https://wiki.ubuntu.com/NetplanUpdates we want to run the following commands to make sure the 'netplan try' command is working properly: $ netplan try $ [Ctrl+C] # to abort the waiting => Make sure it does not print a "An error occurred" message $ netplan try $ [Enter] => Make sure it does not print a "An error occurred" message autopkgtest logs TBD: * Impish: amd64, arm64, armhf, ppc64el, s390x * Hirsute: amd64, arm64, armhf, ppc64el, s390x * Focal: amd64, arm64, armhf, ppc64el, s390x [Where problems could occur] This upload contains changes to the CLI of netplan, if anything goes wrong it could impact the interactive usage of 'netplan try'/'netplan apply' by the user. [Other Info] The full set of autopkgtest logs will be attached after the upload is accepted into -proposed and the tests have been run on the official autopkgtest.u.c infrastructure. === Original Description === I hava a freshly installed Ubuntu Server 20.04 LTS. I am using a static IP config (100% sure it is correct, also the YAML is correct) If you then enter "netplan try" I get this: -------------------------------------------------------------------------------- Warning: Stopping systemd-networkd.service, but it can still be activated by:   systemd-networkd.socket An error occurred: 'NetplanApply' object has no attribute 'state' Reverting. Warning: Stopping systemd-networkd.service, but it can still be activated by:   systemd-networkd.socket -------------------------------------------------------------------------------- "netplan generate && netplan apply" does work. I found some other people having these issues too on freshly installed 20.04 and 21.10 and online forums. System Infos: lsb_release -rd: Description: Ubuntu 20.04.3 LTS Release: 20.04 apt-cache policy netplan.io: netplan.io:   Installed: 0.103-0ubuntu5~20.04.2   Candidate: 0.103-0ubuntu5~20.04.2   Version table:  *** 0.103-0ubuntu5~20.04.2 500         500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages         100 /var/lib/dpkg/status      0.99-0ubuntu1 500         500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages systemd --version: systemd 245 (245.4-4ubuntu3.13) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Thank you!
2021-11-05 21:58:52 Steve Langasek netplan.io (Ubuntu Jammy): status Triaged Fix Committed
2021-11-05 22:17:25 Steve Langasek netplan.io (Ubuntu Focal): status Confirmed Fix Committed
2021-11-05 22:17:28 Steve Langasek bug added subscriber Ubuntu Stable Release Updates Team
2021-11-05 22:17:29 Steve Langasek bug added subscriber SRU Verification
2021-11-05 22:17:33 Steve Langasek tags fr-1833 regression-update fr-1833 regression-update verification-needed verification-needed-focal
2021-11-05 22:20:13 Steve Langasek netplan.io (Ubuntu Impish): status Confirmed Fix Committed
2021-11-05 22:20:20 Steve Langasek tags fr-1833 regression-update verification-needed verification-needed-focal fr-1833 regression-update verification-needed verification-needed-focal verification-needed-impish
2021-11-05 22:30:40 Steve Langasek netplan.io (Ubuntu Hirsute): status Confirmed Fix Committed
2021-11-05 22:30:48 Steve Langasek tags fr-1833 regression-update verification-needed verification-needed-focal verification-needed-impish fr-1833 regression-update verification-needed verification-needed-focal verification-needed-hirsute verification-needed-impish
2021-11-10 14:35:28 Lukas Märdian description [Impact] The last netplan SRU (0.103-0ubuntu5~20.04.2) introduced a state tracking feature, that regressed the 'netplan try' CLI command, if no such --state argument is passed, making it fail with a error message like this: An error occurred: 'NetplanApply' object has no attribute 'state' This upload contains a fix to properly initialize the 'self.state' attribute in all cases to avoid this problem. [Test Plan] In addition to runing & passing the full set of unit- and integration-tests (that contains new tests to check for this regression), as described in https://wiki.ubuntu.com/NetplanUpdates we want to run the following commands to make sure the 'netplan try' command is working properly: $ netplan try $ [Ctrl+C] # to abort the waiting => Make sure it does not print a "An error occurred" message $ netplan try $ [Enter] => Make sure it does not print a "An error occurred" message autopkgtest logs TBD: * Impish: amd64, arm64, armhf, ppc64el, s390x * Hirsute: amd64, arm64, armhf, ppc64el, s390x * Focal: amd64, arm64, armhf, ppc64el, s390x [Where problems could occur] This upload contains changes to the CLI of netplan, if anything goes wrong it could impact the interactive usage of 'netplan try'/'netplan apply' by the user. [Other Info] The full set of autopkgtest logs will be attached after the upload is accepted into -proposed and the tests have been run on the official autopkgtest.u.c infrastructure. === Original Description === I hava a freshly installed Ubuntu Server 20.04 LTS. I am using a static IP config (100% sure it is correct, also the YAML is correct) If you then enter "netplan try" I get this: -------------------------------------------------------------------------------- Warning: Stopping systemd-networkd.service, but it can still be activated by:   systemd-networkd.socket An error occurred: 'NetplanApply' object has no attribute 'state' Reverting. Warning: Stopping systemd-networkd.service, but it can still be activated by:   systemd-networkd.socket -------------------------------------------------------------------------------- "netplan generate && netplan apply" does work. I found some other people having these issues too on freshly installed 20.04 and 21.10 and online forums. System Infos: lsb_release -rd: Description: Ubuntu 20.04.3 LTS Release: 20.04 apt-cache policy netplan.io: netplan.io:   Installed: 0.103-0ubuntu5~20.04.2   Candidate: 0.103-0ubuntu5~20.04.2   Version table:  *** 0.103-0ubuntu5~20.04.2 500         500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages         100 /var/lib/dpkg/status      0.99-0ubuntu1 500         500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages systemd --version: systemd 245 (245.4-4ubuntu3.13) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Thank you! [Impact] The last netplan SRU (0.103-0ubuntu5~20.04.2) introduced a state tracking feature, that regressed the 'netplan try' CLI command, if no such --state argument is passed, making it fail with a error message like this: An error occurred: 'NetplanApply' object has no attribute 'state' This upload contains a fix to properly initialize the 'self.state' attribute in all cases to avoid this problem. [Test Plan] In addition to runing & passing the full set of unit- and integration-tests (that contains new tests to check for this regression), as described in https://wiki.ubuntu.com/NetplanUpdates we want to run the following commands to make sure the 'netplan try' command is working properly: $ netplan try $ [Ctrl+C] # to abort the waiting => Make sure it does not print a "An error occurred" message $ netplan try $ [Enter] => Make sure it does not print a "An error occurred" message autopkgtest logs: * Impish: https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/impish_amd64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/impish_arm64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/impish_armhf.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/impish_ppc64el.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/impish_s390x.log * Hirsute: https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/hirsute_amd64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/hirsute_arm64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/hirsute_armhf.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/hirsute_ppc64el.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/hirsute_s390x.log * Focal: https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/focal_amd64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/focal_arm64.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/focal_armhf.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/focal_ppc64el.log https://git.launchpad.net/~slyon/+git/files/tree/LP1949104/focal_s390x.log [Where problems could occur] This upload contains changes to the CLI of netplan, if anything goes wrong it could impact the interactive usage of 'netplan try'/'netplan apply' by the user. [Other Info] The full set of autopkgtest logs will be attached after the upload is accepted into -proposed and the tests have been run on the official autopkgtest.u.c infrastructure. === Original Description === I hava a freshly installed Ubuntu Server 20.04 LTS. I am using a static IP config (100% sure it is correct, also the YAML is correct) If you then enter "netplan try" I get this: -------------------------------------------------------------------------------- Warning: Stopping systemd-networkd.service, but it can still be activated by:   systemd-networkd.socket An error occurred: 'NetplanApply' object has no attribute 'state' Reverting. Warning: Stopping systemd-networkd.service, but it can still be activated by:   systemd-networkd.socket -------------------------------------------------------------------------------- "netplan generate && netplan apply" does work. I found some other people having these issues too on freshly installed 20.04 and 21.10 and online forums. System Infos: lsb_release -rd: Description: Ubuntu 20.04.3 LTS Release: 20.04 apt-cache policy netplan.io: netplan.io:   Installed: 0.103-0ubuntu5~20.04.2   Candidate: 0.103-0ubuntu5~20.04.2   Version table:  *** 0.103-0ubuntu5~20.04.2 500         500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages         100 /var/lib/dpkg/status      0.99-0ubuntu1 500         500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages systemd --version: systemd 245 (245.4-4ubuntu3.13) +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid Thank you!
2021-11-10 14:45:12 Lukas Märdian tags fr-1833 regression-update verification-needed verification-needed-focal verification-needed-hirsute verification-needed-impish fr-1833 regression-update verification-done-impish verification-needed verification-needed-focal verification-needed-hirsute
2021-11-10 14:55:52 Lukas Märdian tags fr-1833 regression-update verification-done-impish verification-needed verification-needed-focal verification-needed-hirsute fr-1833 regression-update verification-done-hirsute verification-done-impish verification-needed verification-needed-focal
2021-11-10 15:03:17 Stefan Greiner tags fr-1833 regression-update verification-done-hirsute verification-done-impish verification-needed verification-needed-focal fr-1833 regression-update verification-done-focal verification-done-impish verification-needed verification-needed-hirsute
2021-11-10 15:05:13 Stefan Greiner tags fr-1833 regression-update verification-done-focal verification-done-impish verification-needed verification-needed-hirsute fr-1833 regression-update verification-done-focal verification-done-hirsute verification-done-impish verification-needed
2021-11-10 15:12:51 Stefan Greiner tags fr-1833 regression-update verification-done-focal verification-done-hirsute verification-done-impish verification-needed fr-1833 regression-update verification-done verification-done-focal verification-done-hirsute verification-done-impish
2021-11-10 15:14:28 Lukas Märdian tags fr-1833 regression-update verification-done verification-done-focal verification-done-hirsute verification-done-impish fr-1833 regression-update verification-done-focal verification-done-hirsute verification-done-impish verification-needed
2021-11-10 15:18:59 Lukas Märdian tags fr-1833 regression-update verification-done-focal verification-done-hirsute verification-done-impish verification-needed fr-1833 regression-update verification-done verification-done-focal verification-done-hirsute verification-done-impish
2021-11-17 00:22:59 Launchpad Janitor netplan.io (Ubuntu Impish): status Fix Committed Fix Released
2021-11-17 00:23:12 Brian Murray removed subscriber Ubuntu Stable Release Updates Team
2021-11-17 00:24:04 Launchpad Janitor netplan.io (Ubuntu Hirsute): status Fix Committed Fix Released
2021-11-17 00:25:22 Launchpad Janitor netplan.io (Ubuntu Focal): status Fix Committed Fix Released
2021-11-24 17:20:33 Launchpad Janitor netplan.io (Ubuntu Jammy): status Fix Committed Fix Released