=== cpaelzer_ is now known as cpaelzer [13:43] agy, no, you cant. :-( [13:43] agy, but patches are definitely welcome for that. === tmclaugh[work]_ is now known as tmclaugh[work] [18:53] hi there. i'm trying to use cloud-init to partition and mount a disk using the latest ubuntu 14.04 official images on aws and i'm getting a stack trace. https://gist.github.com/BarnacleBob/ef00cbed7d49bd97a058 [18:53] anyone see what i might be doing wrong [18:57] BarnacleBob: I think you're hitting https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1311463 [19:00] ah excelent [19:03] does cloud-init rerun everytime the machine boots up or is there some protection against that? [19:05] BarnacleBob: So it does run, but modules specify if they are per-instance or per-boot. [19:05] BarnacleBob: So generally it comes up and finds there isn't anything to do. [19:05] ok great. i'm guessing disk partitioning and filesystem are once per instance but i'll test it [19:05] I believe they are. [19:07] hey guys, I have a little issue.. my code fails to create users and set passwords: http://paste.ubuntu.com/13333626/ [19:08] and here's my script: http://paste.ubuntu.com/13333632/ [19:09] Diplomat: Is that the output in /var/log/cloud-init.log, or is there more info there? [19:09] well, I can't access my vm unfortunately [19:09] oh [19:09] nvm [19:09] no it's from the console [19:10] console log from openstack [19:11] OK, getting cloud-init.log would probably make it much easier to debug. [19:11] Diplomat: Can you mount that disk on another VM and access it that way? [19:11] Not really [19:12] I'm seeing this too [19:12] [WARNING]: Running ssh-authkey-fingerprints () failed [19:12] I'm using CentOS 6.7 cloud image [19:12] from their website [19:13] Diplomat: OK, if you aren't going to get cloud-init.log, then your best bet is probably to strip down to an empty configuration and add a line at a time. [19:13] Diplomat: I'm curious to know why you can't mount the disk though. :) [19:14] Because I'm not using a volume [19:14] If i'd boot using a volume then i could do that [19:15] Diplomat: What are you booting from? [19:15] From that disc it creates into a compute node [19:16] Diplomat: "that disc it creates" <-- what is creating the disk? [19:16] Umm.. nova? [19:16] I'm not sure what you mean [19:16] So my understanding is that nova creates a volume from the image; you should be able to mount that volume on another instance, no? [19:17] (I'm not super au-fait with OpenStack though, so I could be completely wrong :p) [19:17] Well, you can't do that.. if you would use a volume (Cinder) then you can remove it and add to another VM, mount it and then access those files [19:18] Also.. I just commented out "customer" account creation and used a key pair and now it works [19:18] Changing password for user root. [19:18] passwd: all authentication tokens updated successfully. [19:18] Locking password for user root. [19:18] passwd: Success [19:18] Cool. :) [19:19] Yes, but now I have to figure out why it doesn't want to create an account [19:19] Diplomat: Just add in each line of config there one at a time, and you'll discover which one is the problem. [19:21] I think I already found it.. its that account creation thingy [19:21] so you want to log in to an account that is non-root using password after creation? [19:22] Diplomat: Right, I'm saying see if adding "- name: customer" works and iterate just through that section. [19:22] oh [19:22] Diplomat: Having said that, I suspect lock-passwd should be lock_passwd. [19:22] smatzek: yes [19:22] (Not 100% sure) [19:22] I was going exactly where Odd_Bloke went. lock_passwd is wrong in the public cloud-init docs. [19:22] that's burned hours for me in the past. [19:23] Oh, really? [19:23] I removed it.. but it still failed :/ [19:23] http://cloudinit.readthedocs.org/en/latest/topics/examples.html#yaml-examples has lock-passwd which is wrong. [19:24] yea i took it from there lol [19:24] if you want to be able to log in with password it must be lock_passwd: False [19:25] lock-passwd: False doesn't get picked up because of the - _ difference and the default for lock_passwd is True. [19:25] groups: sudo [19:25] maybe that's a problem too ? [19:26] Diplomat: Try a line at a time. :) [19:30] also, it's not covered much in the docs but you could try plain_text_passwd: passw0rd instead of the hashed one to see if its a problem with a SHA / salt difference. [19:31] Good idea [19:38] yea [19:38] groups: sudo was wrong [19:39] it failed then [19:40] but I still can't login with customer:password [19:40] there are no error messages :/ [19:41] also it only says Changing password for user root. [19:41] nothing about customer.. [19:41] oh, because i forgot to add that line :> [19:44] wooo [19:44] works :D [19:45] Now I have to figure out why it doesn't resize the disc [19:48] growpart: [19:48] mode: auto [19:48] devices: ["/"] [19:48] resize_rootfs: True [19:48] resize_rootfs_tmp: /dev [19:48] sorry for spam [19:48] but shouldn't this part do that? [19:49] or i have to do under runcmd growpart /dev/vda 1 [19:49] or whatever it was [19:51] Actually.. I can see that something is running this: fsck.ext4 -a /dev/vda1