Your message dated Fri, 27 Sep 2019 14:12:50 +0200
with message-id <[email protected]>
and subject line Re: Bug#933640: cloud-init 18.3 failed to run after installed 
in Debian 10
has caused the Debian Bug report #933640,
regarding cloud-init 18.3 failed to run after installed in Debian 10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
933640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933640
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cloud-init
Version: 18.3
X-Debbugs-CC: [email protected], [email protected] , [email protected]  

After "apt-get install cloud-init" and enable cloud-init customize in file of 
"/etc/cloud/cloud.cfg" in Debian 10.0.0 GA, cloud-init doesn’t run even after 
reboot.

# cloud-init -v
/usr/bin/cloud-init 18.3
# ls /var/log/cloud-init.log
ls: cannot access '/var/log/cloud-init.log': No such file or directory
# systemctl status cloud-init.service
● cloud-init.service - Initial cloud-init job (metadata service crawler)
   Loaded: loaded (/lib/systemd/system/cloud-init.service; enabled; vendor prese
   Active: inactive (dead)
# systemctl status cloud-init-local.service
● cloud-init-local.service - Initial cloud-init job (pre-networking)
   Loaded: loaded (/lib/systemd/system/cloud-init-local.service; enabled; vendor
   Active: inactive (dead)

Would you please help us take a look?

If need any other information, please kindly tell me!

--

Best Regards,
Yanhui



--- End Message ---
--- Begin Message ---
On 9/26/19 5:26 AM, Marco Sinhoreli wrote:
> I have the same issue. I don’t know if it helps, but, if I start
> cloud-init systemd daemon manually it works. Maybe the problem is around
> systemd.  

As much as I know, cloud-init isn't a daemon, it just starts at boot
time, does a bunch of things, and that's it. Please re-open the bug if
you think I'm wrong.

Cheers,

Thomas Goirand (zigo)

--- End Message ---

Reply via email to