fixed in 0.7.2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1015223
Title:
cloud-init-nonet main process killed by TERM signal
To manage notifications about this bug go to:
fixed in 0.7.2
** Changed in: cloud-init
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1015223
Title:
cloud-init-nonet main process
** Branch linked: lp:ubuntu/cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1015223
Title:
cloud-init-nonet main process killed by TERM signal
To manage notifications
This bug was fixed in the package cloud-init - 0.7.2~bzr795-0ubuntu1
---
cloud-init (0.7.2~bzr795-0ubuntu1) raring; urgency=low
* New upstream snapshot.
* documentation on write-files module (LP: #205)
* support for specifying package versions in package installs
*
** Branch linked: lp:~smoser/cloud-init/lp-1015223
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1015223
Title:
cloud-init-nonet main process killed by TERM signal
To manage
Sean,
Thanks for the suggestion of handling SIGTERM. I wasn't sure it would work,
but in testing it does seem to.
I've verified that it works by booting a system, and looking in
/var/log/dmesg. You'll see something like:
$ grep init:.*cloud-init.*kill /var/log/dmesg
[ 13.207358] init:
fix-committed in trunk at revno 788.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New = Fix Committed
** Changed in: cloud-init
Importance: Undecided = Low
--
You received this bug notification because you are a member of
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1015223
Title:
cloud-init-nonet main process killed by TERM signal
To manage notifications about
ading normal exit SIGTERM to /etc/init/cloud-init.conf will probably
suppress the appearance of normal termination messages in dmesg. What
would be slightly better, though probably overkill in this case, would
be a signal handler that somehow pacifies upstart by catching SIGTERM
and exiting more
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
I am encountering the same error when I try to add the second node using
physical machines. If I use VMWare Workstation 8.0 I get this error when
trying to add the first node. In both scenarios I am using PXE boot.
Enlisting the nodes works but actualling installing them fails. Before
the process
I forgot to mention that there may be a relation to bug 992075
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1015223
Title:
cloud-init-nonet main process killed by TERM signal
** Changed in: upstart (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1015223
Title:
cloud-init-nonet main process killed by TERM signal
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1015223
Title:
cloud-init-nonet main process killed by TERM signal
To manage notifications about this bug go to:
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Description changed:
it has been reported in maas (and i think i've seen it other places) that the
console may include:
- init: cloud-init-nonet main process (307) killed by TERM signal
+ init: cloud-init-nonet main process (307) killed by TERM signal
This message is scary to
I'm adding an upstart task. I'm wondering if its even valid for upstart
to log these at the default log priority. Perhaps they should be dropped
to 'info' level. Killing a process as part of stopping the job is a
perfectly normal situation and doesn't really seem to warrant logs. The
only time I
17 matches
Mail list logo
