** Summary changed:
- cloud-init parses yaml incorrectly
+ reload-configuration can confuse upstart
--
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/1124384
Title:
reload-configur
** Description changed:
- Example from failure: https://jenkins.qa.ubuntu.com/job/raring-server-
- ec2/ARCH=amd64,REGION=eu-west-1,STORAGE=ebs,TEST=multi-part-ud,label
- =ubuntu-server-ec2-testing/17/console
+ Under bug 1080841 we made cloud-init invoke 'initctl reload-
+ configuration' after it w
** Attachment added: "dmesg when 'initctl reload-configuration' is *not* used"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1124384/+attachment/3528559/+files/dmesg.no-reload.txt
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: upstart (Ubuntu)
** Attachment added: "dmesg when 'initctl reload-configuration' is used"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1124384/+attachment/3528558/+files/dmesg.reload.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clou
** Attachment added: "dmesg with --debug when 'initctl reload-configuration' is
used"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3528635/+files/dmesg-debug-reload.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
** Attachment added: "dmesg with --debug when 'initctl reload-configuration' is
*not* used"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3528636/+files/dmesg-debug-no-reload.txt
--
You received this bug notification because you are a member of Ubuntu
Server T
just a bit more info, the cloud-config content above results in writing
/etc/init/part-002.conf a an upstart job.
The debug logs shown here had that file in place (from a previous boot), and
cloud-init overwriting it, then calling (or not calling) reload-configuration.
--
You received this bug
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1124384
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Server Team, whi
I mistakingly posted recreate instructions at
https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1103881/comments/6 . they're not comletely irrelevant there,
but I did intend for that to go here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
** Description changed:
Under bug 1080841 we made cloud-init invoke 'initctl reload-
configuration' after it wrote a upstart job. This was necessary because
inotify is not supported on all filesystems (overlayfs being the one of
most current interst).
This seems to be causing upstart
I've verified this is still an issue with the following user-data on upstart at
'1.8-0ubuntu1'.
This is re-creatable via the most recent daily image
(ubuntu-raring-daily-amd64-server-20130403). I used ami-88a4c1e1.
But you can download and recreate as above. The user-data provided to
recreate
Ok, another recreate that is possibly simpler to debug. Below, we
create 2 jobs, one invokes reload-configuration, the other just writes
something to /run. We add those jobs to a pristine raring container,
start it, and expect them to run. Only the first will run. I've
explicitly ran 'start cons
16:54 jodh: I *think* I may see the general structure of what's
going on here
16:54 jodh: This debugging should make it about as clear to you as
it is to me so far, I think
16:54 <7>init: conf_load_path_with_override: Loading configuration
file /etc/init/rc-sysinit.conf
16:54 ...
16:54 <7>i
I believe the problem here is that -- in the case where a JobClass has
no running instances -- a reload is causing the original JobClass to be
destroyed. That eventually leads to Event->blockers to reach zero (as a
result of the JobClasses EventOperators being freed) causing the event
to be destroy
14 matches
Mail list logo