Package: cloud-init
Version: 0.7.7~bzr1156-2
Severity: wishlist
Tags: upstream
Dear Maintainer,
I am provisioning an image using
debian-jessie-amd64-hvm-2016-02-17-ebs-39d3917e-ff4e-4597-848e-4d0fdf8529e6-ami-f0e7d19a.3
(ami-3a13ac4) and after ssh becomes available I need to wait for cloud-init to
finish before I can continue (otherwise things like sources.list are not yet
ready).
Currently I need to write a loop to poll /run/cloud-init/result.json and check
for errors, which is a bit fiddly and error prone using ssh, bash and jq etc.
It would be very convenient if one could simply do something like:
if ssh-to-instance cloud-init-wait --timeout 120 ; then
# timedout, assume cloud-init-wait printed any v1.errors from
# result.json.
fi
This would save everyone from reinventing similar code.
Upstream has moved from bzr to git so I'm not 100% sure but it doesn't look
like there is any functionality like this in newer upstream versions.
Thanks,
Ian.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf, armel, arm64
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
