UbuntuIRC / 2015 /08 /03 /#cloud-init.txt
niansa
Initial commit
4aa5fce
raw
history blame
4.21 kB
=== zz_natorious is now known as natorious
=== natorious is now known as zz_natorious
[10:28] <minfrin> Quick question - I'm trying to debug the following crash inside cloud-init when it tries to partition disks:
[10:28] <minfrin> [CLOUDINIT] util.py[DEBUG]: Failed partitioning operation#012'list' object has no attribute 'splitlines'#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/dist-packages/cloudinit/config/cc_disk_setup.py", line 57, in handle#012 func=mkpart, args=(disk, definition))#012 File "/usr/lib/python2.7/dist-packages/cloudinit/util.py", line 1875, in log_time#012 ret =...
[10:28] <minfrin> ...func(*args, **kwargs)#012 File "/usr/lib/python2.7/dist-packages/cloudinit/config/cc_disk_setup.py", line 682, in mkpart#012 if not overwrite and (is_disk_used(device) or is_filesystem(device)):#012 File "/usr/lib/python2.7/dist-packages/cloudinit/config/cc_disk_setup.py", line 308, in is_disk_used#012 if len(use_count.splitlines()) > 1:#012AttributeError: 'list' object has no...
[10:28] <minfrin> ...attribute 'splitlines'
[10:28] <minfrin> Does this look familiar?
[11:31] <Odd_Bloke> smoser: If someone wanted to reset passwords on their (OpenStack) instances, could vendor-data specify a module to re-run at each boot to do it?
=== rangerpbzzzz is now known as rangerpb
=== zz_natorious is now known as natorious
=== natorious is now known as zz_natorious
=== zz_natorious is now known as natorious
[15:25] <clouduser> Hi everyone. Is there a way to configure cloud-config to not use an sshkey for login.
[15:25] <clouduser> I only wish to provide a password for the user.
[15:27] <tpeoples> root user or some other user?
[15:28] <clouduser> some other user. 'ubuntu'
[15:32] <tpeoples> clouduser: can try something like http://paste.openstack.org/show/406770/
[15:35] <tpeoples> can also do something like http://paste.openstack.org/show/406772/
[15:41] <clouduser> Thanks.
[15:42] <clouduser> I tried the first method. I still get "Permission denied (publickey)".
[15:47] <Odd_Bloke> clouduser: Instances, by default, only allow you to use SSH keys (because they are substantially more secure than passwords); I think the second should allow password auth, so it's worth trying that.
[15:50] <tpeoples> yeah, i think the lock_passwd set to false is the key to get password login working
[16:10] <smoser> tpeoples, ssh_pwauth: True
[16:10] <smoser> thats what you need to allow password loging
[16:10] <smoser> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config.txt#L562
=== natorious is now known as zz_natorious
=== zz_natorious is now known as natorious
=== minfrin_ is now known as minfrin
=== natorious is now known as zz_natorious
=== zz_natorious is now known as natorious
[20:09] <number1> Hello, I've been reading through the docs and I'm just trying to figure some things out. I get that there are 3 for cloud-init; init, config, and final. What I don't understand is where user-data files fit in. Do those get executed in the config stage, or after the final stage?
[20:10] <number1> I get that there are 3 stages for cloud-init*
=== number1 is now known as doesntunderstand
[20:19] <doesntunderstand> Hello, I've been reading through the docs and I'm just trying to figure some things out. I get that there are 3 for cloud-init; init, config, and final. What I don't understand is where user-data files fit in. Do those get executed in the config stage, or after the final stage?
[20:19] <doesntunderstand> I get that there are 3 stages for cloud-init*
[20:20] <smatzek> doesntunderstand: while there are probably more technical answers, you can think of user_data as providing input to the modules that run at those 3 stages.
[20:21] <smatzek> run cat /etc/cloud/cloud.cfg You can see the modules listed in each stage. The userdata can provide input to any/all of them depending the module.
[20:27] <doesntunderstand> Ah, so user_data applies to all stages?
[20:32] <smatzek> doesntunderstand: yes, depending on the content of your userdata
[20:32] <doesntunderstand> Cool. Thanks, I appreciate it!
=== rangerpb is now known as rangerpbzzzz
=== natorious is now known as zz_natorious