On Feb 28, 2012 6:12 AM, "Juerg Haefliger" <jue...@gmail.com> wrote: > [ 92.376121] systemd[1]: cloud-init-local.service changed start -> failed
Of interest here is the fact that the script that cloud-init-local.service runs currently has a bug that causes it to return the wrong return code. Since cloud-init.target Requires that service (cloud-config.service does not function correctly without it), two of those services should not be running at all, if I understand the systemd documentation correctly. On Feb 28, 2012 6:12 AM, "Juerg Haefliger" <jue...@gmail.com> wrote: > On Tue, Feb 28, 2012 at 12:02 PM, Michal Schmidt <mschm...@redhat.com> > wrote: > > On 02/26/2012 07:37 AM, Garrett Holmstrom wrote: > >> > >> On 2012-02-24 4:22, Juerg Haefliger wrote: > >>> > >>> So I installed the official Fedora version of cloud-init but the > >>> service startup ordering is broken there too: > >>> > >>> [root@342 ~]# dmesg | grep cloud | grep About > >>> [ 91.668396] systemd[1]: About to execute: /usr/bin/cloud-init > >>> start-local > >>> [ 91.993238] systemd[1]: About to execute: /usr/bin/cloud-init-cfg > all > >>> config > >>> [ 92.540255] systemd[1]: About to execute: /usr/bin/cloud-init-cfg > all > >>> final > >>> [ 92.559834] systemd[1]: About to execute: /usr/bin/cloud-init start > > > > > > I can't reproduce the problem. They are started in the expected order > here. > > > > Juerg, > > is this a log of the order during boot? Or did you test the services by > > listing all 4 of them in systemctl start ...? > > The latter would show bug 704214. > > > This is the boot order. Different than the last time: > > [root@fedora ~]# dmesg | grep cloud > [ 1.639947] systemd[1]: Installed new job cloud-config.service/start as > 80 > [ 1.639952] systemd[1]: Installed new job cloud-config.target/start as > 81 > [ 1.639957] systemd[1]: Installed new job > cloud-init-local.service/start as 82 > [ 1.639961] systemd[1]: Installed new job cloud-init.service/start as 83 > [ 1.639966] systemd[1]: Installed new job cloud-final.service/start as > 84 > [ 1.640413] systemd[1]: cloud-config.target changed dead -> active > [ 1.640426] systemd[1]: Job cloud-config.target/start finished, > result=done > [ 91.676503] systemd[1]: About to execute: /usr/bin/cloud-init > start-local > [ 91.686093] systemd[1]: Forked /usr/bin/cloud-init as 489 > [ 91.686227] systemd[1]: cloud-init-local.service changed dead -> start > [ 91.990133] systemd[1]: About to execute: /usr/bin/cloud-init-cfg all > config > [ 91.998048] systemd[1]: Forked /usr/bin/cloud-init-cfg as 549 > [ 91.998213] systemd[1]: cloud-config.service changed dead -> start > [ 92.364807] systemd[1]: Received SIGCHLD from PID 549 (cloud-init-cfg). > [ 92.364835] systemd[1]: Got SIGCHLD for process 549 (cloud-init-cfg) > [ 92.364877] systemd[1]: Child 549 belongs to cloud-config.service > [ 92.364889] systemd[1]: cloud-config.service: main process exited, > code=exited, status=0 > [ 92.375143] systemd[1]: cloud-config.service changed start -> exited > [ 92.375160] systemd[1]: Job cloud-config.service/start finished, > result=done > [ 92.375264] systemd[1]: Got SIGCHLD for process 489 (cloud-init) > [ 92.375302] systemd[1]: Child 489 belongs to cloud-init-local.service > [ 92.375311] systemd[1]: cloud-init-local.service: main process > exited, code=exited, status=1 > [ 92.376121] systemd[1]: cloud-init-local.service changed start -> failed > [ 92.377151] systemd[1]: Job cloud-init-local.service/start > finished, result=failed > [ 92.377175] systemd[1]: Unit cloud-init-local.service entered failed > state. > [ 92.377833] systemd[1]: About to execute: /usr/bin/cloud-init start > [ 92.385184] systemd[1]: Forked /usr/bin/cloud-init as 599 > [ 92.385262] systemd[1]: cloud-init.service changed dead -> start > [ 92.385293] systemd[1]: About to execute: /usr/bin/cloud-init-cfg all > final > [ 92.393218] systemd[1]: Forked /usr/bin/cloud-init-cfg as 600 > [ 92.393358] systemd[1]: cloud-final.service changed dead -> start > [ 92.394075] systemd[1]: cloud-config.service: cgroup is empty > [ 92.394927] systemd[1]: cloud-init-local.service: cgroup is empty > [ 92.550734] systemd[1]: Received SIGCHLD from PID 600 (cloud-init-cfg). > [ 92.550760] systemd[1]: Got SIGCHLD for process 600 (cloud-init-cfg) > [ 92.550803] systemd[1]: Child 600 belongs to cloud-final.service > [ 92.550810] systemd[1]: cloud-final.service: main process exited, > code=exited, status=0 > [ 92.559058] systemd[1]: cloud-final.service changed start -> exited > [ 92.559072] systemd[1]: Job cloud-final.service/start finished, > result=done > [ 92.559522] systemd[1]: cloud-final.service: cgroup is empty > [ 116.415829] systemd[1]: Received SIGCHLD from PID 599 (cloud-init). > [ 116.415854] systemd[1]: Got SIGCHLD for process 599 (cloud-init) > [ 116.415896] systemd[1]: Child 599 belongs to cloud-init.service > [ 116.415908] systemd[1]: cloud-init.service: main process exited, > code=exited, status=0 > [ 116.422236] systemd[1]: cloud-init.service changed start -> exited > [ 116.422252] systemd[1]: Job cloud-init.service/start finished, > result=done > [ 116.422760] systemd[1]: cloud-init.service: cgroup is empty > [root@fedora ~]# dmesg | grep cloud | grep Ab > [ 91.676503] systemd[1]: About to execute: /usr/bin/cloud-init > start-local > [ 91.990133] systemd[1]: About to execute: /usr/bin/cloud-init-cfg all > config > [ 92.377833] systemd[1]: About to execute: /usr/bin/cloud-init start > [ 92.385293] systemd[1]: About to execute: /usr/bin/cloud-init-cfg all > final > > Send me your public key and I'll hook you up with access to the VM if > you want to poke around. > > ...Juerg > > > > Michal > > > > -- > > devel mailing list > > devel@lists.fedoraproject.org > > https://admin.fedoraproject.org/mailman/listinfo/devel > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
