/srv/irclogs.ubuntu.com/2013/12/02/#cloud-init.txt

=== worth is now known as mushtar
tmclaugh[work]Hey, we're having an issue where our puppet section is failing to install Puppet from our repo.15:43
tmclaugh[work]One person here feels it's possibly because networking isn't fully up...15:43
tmclaugh[work]Isn't it safe to say that cloud-init will be running after networking is operable?15:44
Chocobodoes anyone see anything wrong with this configuration:  http://pastie.org/852314415:44
ChocoboWhat is the difference between "- UserName" and "- name: UserName16:02
=== ctracey|away is now known as ctracey
smosertmclaugh[work], ubuntu ?17:20
tmclaugh[work]smoser: CentOS17:21
tmclaugh[work]does cloud-init perform any networking service restart?17:21
smoserit really depends on the datasource, but for ubuntu all interfaces defined in /etc/network/interfaces are guaranteed to be up before packages will be installed.17:21
smosertmclaugh[work], why would it do a restart ?17:21
tmclaugh[work]smoser: I don't know.  Just ruling it out.  I'm 99% certain that networking is initialized and fully operational before cloud-init starts and that it's not causing the network connection to blip17:22
tmclaugh[work]to backup a few steps, out puppet package installation periodically fails.17:22
tmclaugh[work]So someone proposed, "let's move the puppet installation to further down in the cloud-init order"17:22
smoserChocobo is gone17:23
smoserbut http://paste.ubuntu.com/6510271/ is the eanswer to his question17:23
smoserbasically, he provided broken yaml.17:23
tmclaugh[work]He wants to move it from cloud_config_modules to cloud_final_modules17:23
smosertmclaugh[work], do you have multiple interfaces ?17:24
tmclaugh[work]he's claiming that maybe by delaying the install Networking will be working.  Which makes no sense to me.17:24
tmclaugh[work]nope, signle interface17:24
smoseri can't speak definitevely on the init scripts for centos17:24
tmclaugh[work]The host should have successfully DHCPed  before cloud-init starts.17:24
smoserbut for ubuntu, yes. your statement above is correct17:24
smoserwhat is the datasource you're using ?17:24
smoser(openstack or ec2 ?)17:24
tmclaugh[work]and I'm 99% sure this is the case with CentOS17:25
tmclaugh[work]ec217:25
smoseri suspect that if it were not the case on ec2, you'd not be the first to report this issue.17:26
tmclaugh[work]Good, time for another argument with this person. :)17:28
ChocoboIs there a way to test cloud configurations?  I am having a real problem with "users:"19:17
smoserChocobo, http://paste.ubuntu.com/6510271/19:19
smoserrunning that will expose your problem19:19
smoseryou had invalid yaml19:19
Chocobosmoser: Thanks...  also if I move "vmuser" to the first entry in users, I should be able to eliminate the "user: vmuser" line correct?19:21
smoser'user' affects the entry in user that is marked 'default: True'.19:23
smoseri think.19:23
smoserwait19:23
smoserignore that last statement19:23
smoserfrom doc/examples/cloud-config-user-groups.txt:19:24
smoser # users[0] (the first user in users) overrides the user directive.19:24
smoserso yeah:19:24
smoserusers:19:24
smoser - name: vmuser19:24
Chocobosmoser: thanks, I will give that a shot.19:25
smoserChocobo, note, unfortutely this bit of code has been error prone :-(19:26
Chocobosmoser: the "user:" creation is error prone?   19:26
smoserwell...w ait.19:26
smoserthe thing that is error prone is the inclusion of 'user:' into 'users'19:27
smoserif you only use 'users'19:27
smoseryou should be ok19:27
Chocobook, that is alright...  and it is ok to list a user that already exists (root for example)19:28
harlowjaerror prone u say smoser, impossible, ha20:01
smoserChocobo, its ok to list a user that exists20:01
smoserbut it wont be modified20:01
smoserie, its gecos wont be changed.20:02
smoser(or groups)20:02
Chocobosmoser: How aout locking an account?20:25
smoseri think that is only applied on creation20:25
Chocobosmoser: ok, thanks.21:04
=== ctracey is now known as ctracey|away

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