Public bug reported: cloud-init status --wait blocks indefinitely after running 'sudo cloud- init init --local' on the commandline. This path is sometimes used after a user upgrades cloud-init and then executes a 'systemctl restart cloud- init-local.service' to avoid rebooting.
This is an uncommon/unsupported path generally, and generally in most cases we'd recommend that "systemctl restart cloud-init.service" is also run afterward, but it does represent as window during which cloud-init status --loing (or --wait) is lying and says that cloud-init is still running. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cloud-init 18.3-9-g2e62cb8a-0ubuntu1~18.04.2 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CloudName: LXD Date: Fri Aug 17 21:02:23 2018 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) user_data.txt: #cloud-config {} ** Affects: cloud-init (Ubuntu) Importance: Low Status: Triaged ** Tags: amd64 apport-bug bionic uec-images ** Changed in: cloud-init (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787657 Title: cloud-init status reports 'running' after 'cloud-init init --local' run on commandline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1787657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs