Your message dated Sat, 22 Jul 2017 21:33:59 +0200 with message-id <[email protected]> and subject line Bug can be closed has caused the Debian Bug report #735204, regarding cloud-init: boot never finished switch to runlevel 2 with upstart 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.) -- 735204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735204 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: cloud-init Version: 0.7.2-3 Severity: normal Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Install upstart and cloud-init on the same system. * What exactly did you do Boot a fresh instance. * What was the outcome of this action? System boots but rc never returns because startpar is waiting for jobs to be in a start/running state. * What outcome did you expect instead? I expected the system to boot completely. The problem is that upstart booting on Debian is in a transition phase where startpar listens to upstart events to keep track of upstartified scripts that have scripts in /etc/rc#.d. It may miss early started events though, so it will consider a job in 'start/running' as ready. Since cloud-init uses tasks to control early boot, the tasks will have run, but will be 'stop/waiting'. So startpar waits forever for them and never moves to the final phase of the sysvinit boot. As long as we need startpar for sysvinit<->upstart, we will have to use pre-exec instead of 'task' to run one-time tasks. The jobs will also need 'stop on' so the shut down does not block waiting for them.
--- End Message ---
--- Begin Message ---Unfortunately, upstart isn't maintained in Debian anymore, therefore, we should ignore issues with it. Cheers, Thomas Goirand (zigo)
--- End Message ---
