cloud-init status reports 'running' after 'cloud-init init --local' run on commandline

Bug #1787657 reported by Chad Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Triaged
Low
Unassigned

Bug Description

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
 {}

Revision history for this message
Chad Smith (chad.smith) wrote :
Changed in cloud-init (Ubuntu):
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.