/srv/irclogs.ubuntu.com/2015/12/16/#cloud-init.txt

smosercornfeedhobo, thanks01:00
cornfeedhobothank you as well :)02:32
=== cpaelzer is now known as cpaelzer_afk
jlebonhi all, hitting a strange issue on f23 with 0.7.617:00
jlebonit seems like commands in the bootcmd section are run twice?17:00
jlebononce during init-local and once more during 'init'17:01
jlebonis this the expected behaviour?17:02
smoserjlebon, they should only run at one of those17:40
jlebonsmoser: hmm strange. i'll check if fedora is holding any patches that might affect this17:42
jlebonwhich of the two should it run at, init-local?17:42
smoserwell, it should run when the datasource is found.17:43
smoseri'm guessing you're config drive ?17:43
jlebonno, i'm using NoCloud17:43
jlebongiving seedfrom on the commandline17:43
smoserhm.17:43
smoserjust thinking, it coudl be a bug.17:44
jlebonhmm, yeah I don't see anything related to this in the fedora patches17:45
smoserjlebon, can you post /var/log/cloud-init* ?17:51
smosersomethign is goign wrong in that if init-local finds a datasource and runs the init modules, then init should not17:51
jlebonsmoser: sure, let me get it from a fresh instance17:51
smoserand generally speaking if you're seeding you want 'dsmode=net' . but it shoudl actually do the right thing if it is seeded from http17:52
jlebonsmoser: ahhh, i'm using dsmode=nocloud;s=/path/to/cloud-init-data17:55
jlebonsmoser: http://ur1.ca/ocj8n17:55
jlebonthe ln msg is how I know it's runnign twice17:55
jleboni didn't use ln -f so it fails on the second time17:56
smoseryeah, so you want:17:58
smoser ds=nocloud,dsmode=nocloud-net17:59
jleboneven though i'm seeding locally?17:59
smoserwell, if you want networking to be guaranteed when the bootcmd commands run18:00
smoserthen you need dsmode=net18:00
smosermaybe you need journalctl or systemctl info18:01
smoserthe pasete there isnt very much other than to show like you said that its probably running twice. although the order there is still odd.18:01
smoser(that they come before the 'running init')18:01
smosermaybe i just misunderstood your problem18:01
smoserbootcmds do run on everyboot18:01
smosernot "per-instance"18:01
jleboni can paste the full journal if needed18:02
jlebonright, it does run which is good18:02
jlebonmy issue is that it runs twice18:02
jlebonit's not a big deal in this case because i can make my bootcmd idempotent18:02
jlebonby using ln -f18:02
smoserit shoudl not run twice per boot though.18:02
smoserit shoudl run once on every boot18:03
jlebonright, so there's a mismatch somewhere -- did you mean earlier that using the ds=nocloud,dsmode=nocloud-net cmdline would work around this issue?18:04
jlebonthe files themselves are located locally, so i don't really need net access for sourcing18:04
smoserwell, it shoudlnt happen. can you get the full log ?18:05
smoseri'm nto sure why you're running twice.18:05
smoserthe order of the log you pasted is really confusing18:05
smosereither the ln ran the second time *before* the 'running "init"' message18:06
smoseror the order is just flipflopped18:06
smoser(stdout/stderr possibly)18:06
jlebonsmoser: journalctl output http://ur1.ca/ocj9o18:06
jlebonnotice the bootcmd module running on line 1143 and on line 142718:07
smoserwell notice line 996 and 125218:09
smoserinit-local is running twice18:09
jlebonhmm, i thought the 1252 line was just to "close off" the logs for that instance18:11
jlebonthey're the same PID18:11
jlebonthe first bootcmd is run by pid 742 and the second by 85618:12
smoserjlebon, so, what is suppose to happen is that cloud-init local should write a file that said that it ran . and the cloud-init-net shoudl basically do nothing18:17
smoseri really can'tdebug this much more right now, i'm sorry.18:18
smoseri do think you're right about the same pid though (i was wrong about local running twice)18:18
jlebonsmoser: no worries, this is not high priority for me as well, just thought i'd investigate on here18:19
jlebonthanks for looking into it18:19
jlebonif it does become a bigger issue for me, i'll see if i can look into it18:20
=== shardy is now known as shardy_afk
=== cpaelzer_afk is now known as cpaelzer
=== cpaelzer is now known as cpaelzer_afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!