/srv/irclogs.ubuntu.com/2017/04/06/#cloud-init.txt

=== rangerpbzzzz is now known as rangerpb
smoserrharper, fyi, shadowusers really sucks.15:59
smosers/shadowusers/extrausers/15:59
smoser http://pad.lv/167976515:59
smoserbug 167977716:00
smoserbug 167976516:00
smoseri thought i had amup here.16:00
rharperthe first bug is a coreutils issue; I believe the --extrausers was introduced in some of those tools; I guess not all of them16:15
rharperthe second issue is related to cloud-init's concept of 'system-user';   that does need to be addressed;16:15
smosergenerally agree.16:16
smoserthe first bug is just a half-done implementation16:16
smoserbut so is the second.16:16
smoserthere are well defined ways that you can iterate users or get information about users.16:17
smoserpython uses such ways16:17
smoserand they dont work with 'extrausers'16:17
rharperit may end up being the same bug 'incomplete extrausers implementation'16:18
rharperI suspect it's broken without cloud-init; ie, if you snap create-user with an assertion, the same issues remain w.r.t user manipulation/configuration/enumeration16:18
rharperwe should likely sync with foundations16:19
smoserwell, yes. cloud-init *does* have the ability to know that for users it created.16:21
smoserbut "what is the home directory for bob". should not require "is bob an extra user?"16:21
rharpercorrect, which to me is a bug in the getent failure;  I think if --extrausers is available in the tools, the the default search should try both paths (/etc/passwd , /var/lib/extrausers/passwd)16:31
rharperetc16:31
harlowjasmoser hey, for the reporting stuff in cloud-init, what's a common usage of it?17:40
smoserto do the bidding of harlowja17:41
harlowjasome folks at godaddy are trying to gather more insight into how long modules in cloud-init run for and ...17:41
smoserbut it was added for maas17:41
harlowjaand this reporting stuff looks designed for doing that (sort of)17:41
smosermaas wanted status17:41
harlowjaya, makes sense17:41
harlowjasounds similar17:42
smoserbut yeah. the reporting stuff is doing that too17:42
harlowjacool beans17:42
smoserand rharper has stuff that reads a journal17:42
harlowja?17:42
harlowjaout loud?17:42
smoserand timestpams things17:42
harlowjacool cool17:42
smoserit reads harlowja's journal17:42
harlowjamy diaryyyyy17:42
harlowjanoooo17:42
smoser"Dear diary, today I met a new friend"17:42
harlowjahis name was bob17:42
smoser"I think i love cloud-init"17:42
harlowjalol17:42
harlowjathe things i write about smoser ...17:43
harlowjadon't read those17:43
harlowjalol17:43
smoserrharper, where do we see cloud-init annotate ?17:43
rharperhttps://lists.ubuntu.com/archives/ubuntu-server/2016-October/007419.html17:43
rharperhttps://code.launchpad.net/~raharper/+git/cloudinit-analyze17:43
harlowjahmmm17:44
harlowjainteresting17:45
harlowjacool, thx17:45
harlowjaforwarding some of htis17:45
rharperalso, it'd be highly useful if we wrapped each subp with a reporting event17:45
smosernot the journal entries i hope17:45
rharperthat'd give us per exec data17:45
rharpersmoser: lol17:45
harlowjawhats this 'ubuntu-server' ml17:45
harlowja:-P17:45
rharperI also sent it to the cloud-init ML17:48
rharperwhich is hosted on launchpad17:48
harlowjaoh17:48
* harlowja shuts up now17:48
harlowjalol17:48
erick3khi18:07
erick3kcan someone help me debug a timeout18:07
erick3kplease18:07
erick3khttps://paste.fedoraproject.org/paste/VifD~R6n8t78gj-m-Iv4CV5M1UNdIGYhyRLivL9gydE=18:07
smosererick3k, at very least you'll need to paste /var/log/cloud-init.log and also journalctl output18:09
erick3kty18:09
erick3khttps://paste.fedoraproject.org/paste/7rV6y2UBLmcJ77KPWP4PjF5M1UNdIGYhyRLivL9gydE=/raw18:12
erick3kthat is /var/log/cloud-init.log (although there is nothing other than a warning that config drive was unplugged)18:12
erick3kand journalctl output says invalid argument18:13
=== rangerpb is now known as rangerpbzzzz
erick3kcan someone help me when get a change, https://paste.fedoraproject.org/paste/6-WoDBw8~Pw9QtOd2KV~lF5M1UNdIGYhyRLivL9gydE=22:26
erick3kgetting big timeouts22:26
naccerick3k: which line?22:32
erick3knacc i dont really care about the warnings if they are not causing the timeout nor i care it can't print to the console but i am guessing this is the big timeout22:33
erick3kCloud-init v. 0.7.5 finished at Thu, 06 Apr 2017 22:16:28 +0000. Datasource DataSourceConfigDrive [local,ver=2][source=/dev/sr1].  Up 311.33 seconds22:33
erick3kthat is 5 mins22:33
erick3ki guess?22:33
naccare these from multiple installs? why is cloud-init 'finished' more than once22:34
naccalso it's a bit odd that the timezone appears to jump in the logs?22:35
nacc2017-04-06 18:16:28,20822:35
naccThu, 06 Apr 2017 22:16:28 +0000.22:35
nacclines 120 and 12122:35
erick3kummm maybe i didn't clear the log22:35
erick3kyes its weird and i can't find why those huge timeouts22:36
naccstarts at Thu, 06 Apr 2017 22:11:2222:36
erick3klike the vm takes after is up, like 20 mins before it reboots (runcmd)22:36
naccends at Thu, 06 Apr 2017 22:16:28 +000022:36
naccerick3k: which log is this?22:37
nacc2017-04-06 18:11:26,935 - cloud-init[WARNING]: Stdout, stderr changing to (>> /var/log/cloud-init-output.log, >> /var/log/cloud-init-output.log)22:37
erick3kyes22:37
naccCloud-init v. 0.7.5 running 'init' at Thu, 06 Apr 2017 22:16:21 +0000. Up 305.12 seconds.22:37
naccthere is the 5 minute gap22:37
erick3kchanges cloud-init.log to cloud-init-output.log22:37
nacc(i think)22:37
erick3knot sure why, am using centos 7 cloud image22:37
erick3kand why that gap? how can i tune that timeout thingy22:38
erick3kany ideas nacc?22:39
naccerick3k: so that output is from cloud-init.log, erick3k ?22:40
erick3kthere is nothing on cloud-init.log22:40
naccerick3k: i'm not sure why you think it's a timeout?22:40
erick3kwell what could it be doing for 15 minutes?22:41
naccerick3k: there is a delay, but that doesn't necessarily equate to a timeout, unless you have some other data?22:41
nacc5 minutes, i thought?22:41
erick3kna22:41
erick3konce the machine is up and ready for login22:41
erick3klast command in runcmd: -reboot is run like 15 - 20 minutes later22:41
naccerick3k: but i can only go off what's in the logs22:42
naccerick3k: you might need smoser or rharper for this22:43
erick3kyes he tried but busy22:43
erick3kthats all there is on logs, cloud-init.log is changed to cloud-init-output.log22:43
erick3kso is same file22:43
naccerick3k: https://lists.ubuntu.com/archives/ubuntu-server/2016-October/007419.html22:43
naccerick3k: i wonder if that profiler would help22:44
erick3khe saying 13% improvement22:45
naccerick3k: by making changes based upon profiling22:45
naccerick3k: my point was the profiler might tell you where all your time is being spent, if it's cloud-init22:45
erick3ki have the machines in raid 0 with two NVME intel latest pci ssd, so you can imagine how fast things are22:45
erick3kit boots in like 3 seconds so 15 minutes is just beyond ridiculous amount of time to have an instance ready22:46
erick3kyou think it could be a timeout on the os?22:47
erick3k*OS22:47
naccerick3k: i really don't know -- was hoping it'd be something obvious, but i don't know enough about cloud-init or cento22:47
nacc*centos22:47
erick3kkind of same happens in ubuntu 1422:48
erick3ktakes a long time22:48
erick3know that you tell me might be OS timeout for network gonna check that first22:48
erick3kis there a way to have the network not even look for dhcp while turning on until cloudinit injects the network?22:49
naccerick3k: i assumethat would be centos specific22:49
erick3kall22:50
erick3kubuntu / centos22:50
erick3ki seal the vm with this in interfaces22:50
erick3kDEVICE=eth022:51
erick3kTYPE=Ethernet22:51
erick3kBOOTPROTO=dhcp22:51
erick3kONBOOT=yes22:51
erick3kwhat if i delete that?22:51
erick3kcan cloud-init still inject?22:51
erick3kYES SR23:13
erick3kTHAT WAS THE TIMEOUT23:13
erick3kFINALLY23:13
erick3khehe23:13
erick3know instance ready in 6 seconds23:14
erick3kthats how its done :)23:14

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