[14:24] Hi [14:25] Any one online [14:25] Need a help [14:27] faizal: Just ask. You'll get the answer (sooner or later) if someone knows it :) [14:27] Ok [14:31] We are using cloud init to create users in all our servers. .I have written the cloud config script and uploaded it to s3. ..then I wrote a wrapper shell script which will download the cloud config script from the s3 and will run the command "cloudinit init " [14:32] Our plan is to put this wrapper script in cron job and run every 30 min [14:32] So if we want to add a user we will just edit the cloud config script and upload to s3 [14:33] The problem I am facing is [14:33] When I run the script manually it is working fine [14:34] But from cron job it is showing some error [14:34] faizal: Can you pastebin the error somewhere? [14:36] Where can I paste [14:36] faizal: http://paste.ubuntu.com/ [14:36] faizal: (It's worth noting that cloud-init is designed to run when initialising a server, it's not really intended for this use case.) [14:36] But I'm happy to see if I can unblock you. [14:38] Pasted [14:38] faizal: You need to give us the link. :) [14:38] 10449492 [14:39] Can you see [14:40] faizal: I can; in future just put the whole URL in the channel. :) [14:40] faizal: And could you also paste your configuration? [14:40] Ok [14:44] http://paste.ubuntu.com/10449576/ [14:45] faizal: Which user was failing to create? [14:46] When i run the command manually the user is getting created [14:47] But from crontab it Is showing error [14:49] It is not creating any user when running from cronjob [14:50] faizal: Sorry, let me rephrase: all of the users in that configuration have already been created, so I'm not sure what in the configuration is causing failure. [14:52] I added a new user named "newuser" in the cloud config and ran the script from cronjob [14:53] That newuser is not getting created when running from cronjob but is getting created when running manually [14:53] faizal: Oh, you know what, this is probably a PATH issue. [14:54] faizal: You'll have useradd in your PATH when you run it manually, but PATH won't be set in cron. [14:54] ohh [14:55] So how to fix [14:55] Any clue [14:56] faizal: Set PATH in your crontab. [14:57] Can you tell me how. ..I am just a beginner in Linux [15:02] Got it [15:02] Thanks odd_bloke [15:02] Its working fine now [15:03] faizal: :) [15:03] You saved my weekend [15:03] faizal: You might want to look at configuration management software rather than cloud-init for this sort of ongoing usecase. [15:03] faizal: But I'm glad I could help. :) [15:03] Yeah [15:03] Odd_Bloke++ :) [15:04] This was a task from my manger and I am a new joinee [15:04] You saved me [15:05] :-) [15:24] well, as faizal has quit, it doens't help so much, but with cloud-init 2.0 we do want to have some mechanism for accomplishing what he wants. [15:25] smoser: Presumably we'd want to be able to do it against a cloud's metadata source. [15:26] (Rather than an arbitrary source, like faizal was using) [15:31] one way or another, information in some format would get to cloud-init and it would act on it. [15:31] i odnt think s3 is terrible, its a datastore, and can be addressed over https also. [15:32] so : cloud-init set-config https://foo.bar/wark [15:32] doesn't seem so bad. [15:32] but it is treating cloud-init like puppet in a lot of ways. [15:32] and i'm not so sure how far down this hole we'll go [15:43] Yeah, that would be my concern. [19:54] my god, the Horizon spice console is looking horrible [19:54] :p [20:45] smoser: was cirros building on 14.04, or still at 12? [20:45] i think 0.3 builds on 12.04 [20:45] hm hm [20:45] ok [20:45] but i think i mvoed it to 14.04 in a 0.4 branch [20:46] I want to setup a new builvm, to get back to playing with it a littl [20:46] and as much as I'd like to play in docker, I'm going the qemu-way first :p [20:48] i think i'd go from lp:~smoser/cirros/buildroot-upgrade [20:48] ah yeas, I was looking for that [20:48] and that builds on 14? [21:13] smoser: wasn't there some magic just-build-the-damn-thing script? [21:13] (or did I create that myself, once) [21:17] looking [21:17] http://bazaar.launchpad.net/~smoser/cirros/buildroot-upgrade/view/head:/doc/create-release.txt [21:18] looking that,didn't you make build-release or something? [21:18] oh [21:19] stupid [21:19] thats actually being refrenced from inside that .txt [21:23] VER=0.3.3 && ./bin/build-release $VER 2>&1 | tee build-$VER.log [21:24] ok [21:24] right. [21:24] hm, what's this... the vm is suffering from bitrot, so it seems [21:25] the vm ? [21:25] instance [21:25] you just launch new ones all the time :) [21:26] no no, I have one ubuntu 1404 instance :) [21:26] and it's corrupting my downloads [21:28] hm, mtu 1450 seems to go better (instead of 1400) [21:33] smoser: you have access to some PPC64 hardware right? [21:33] thats IBM PowerPC, right? [21:33] i do, yeah. [21:34] https://code.launchpad.net/~smoser/cirros/powerpc at one point was close. [21:34] we have Power6 and 7 at work [21:35] would it be conventient to have access to either one of those archs to build, say, cirros? [21:40] well, cirros is cross-building. [21:40] so it would build on x86_64 is fine. [21:40] i think that both of those arches should support 'ppc64 kernel' [21:41] at somepoint i'd like to have a ppc64el one also, and that would only run on power8 [21:41] ok [21:42] but those are all crosscompiled [21:56] right. buildroot is always crosscompile [21:57] so from a build perspective, powerX are not terribly useful [21:57] but for testing they are [21:57] yup [22:01] i got to run. later man. have fun. [22:01] :)