[07:58] <nk121> write-files occasionally fails for me, the only i can find is
[07:58] <nk121> 2015-03-20 07:35:14,540 - util.py[WARNING]: Running write-files (<module 'cloudinit.config.cc_write_files' from '/usr/lib/python2.7/dist-packages/cloudinit/config/cc_write_files.pyc'>) failed
[07:58] <nk121> any ideas on how to debug?
[11:28] <ndonegan> Hi, currently have cloud-init setup so it will ONLY try EC2. Unfortunately as we have found out, EC2 when using a certain provider's net product is not as reliable as we'd like, so we've been seeing the "likely bad things to come!" message a bit too often :(
[11:29] <ndonegan> At the moment, I've made a copy of the FallBack/None data source which can take in a "user_data" from the config and do things like stop the service that's supposed to start from starting etc.
[11:30] <ndonegan> Is there any neater way of doing this?
[11:41] <ndonegan> And now I spot that Fallback can use data from the config!
[16:01] <zilberstein> good day #cloud-init
[16:01] <zilberstein> I have a problem setting timezone on virtual machine with cloud-init
[16:02] <zilberstein> I pass `timezone` key in meta-data
[16:02] <zilberstein> but cloud-init reports in log the following
[16:02] <zilberstein> Mar 20 11:53:57 localhost [CLOUDINIT] cc_timezone.py[DEBUG]: Skipping module named timezone, no 'timezone' specified
[16:03] <zilberstein> it is specified in /etc/cloud/cloud.cfg
[16:04] <zilberstein> - timezone
[16:12] <smoser> zilberstein, the '-' ?
[16:12] <smoser> oh. i see.
[16:12] <zilberstein> smoser, what - stands for ?
[16:13] <smoser> what metadata did you send ?
[16:13] <smoser> it really should work:
[16:13] <smoser> #cloud-config
[16:13] <smoser> timezone: foo
[20:14] <nk121> hi smoser, any ideas on how to debug write-files? sometimes my files write, and sometimes they don't. the yaml appears valid (it loads in python yaml parser at least). the only error message i could find: 	2015-03-20 07:35:14,540 - util.py[WARNING]: Running write-files (<module 'cloudinit.config.cc_write_files' from '/usr/lib/python2.7/dist-packages/cloudinit/config/cc_write_files.pyc'>) failed
[20:15] <smoser> nk121, probably /var/log/cloud-init.log has something
[20:15] <smoser> a stack trace probably
[20:16] <smoser> if not, you can alway srun that module by hand:
[20:16] <smoser>  sudo cloud-init --debug single --frequency=always --name=write_files
[21:16] <stresler> I want to start work on a new datasource that I'll eventually want to submit to here http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/files/1084/cloudinit/sources 
[21:17] <stresler> My question is, what is the best way to test this? Can I drop it into the directory layout somewhere while I'm working on it, or do I need to roll a build to test it ? 
[21:19] <nk121> smoser: cool, i think i found the isssue. i'm creating an acount via system_info.default_user.name (basically to change it from "ubuntu"), and the file i'm writing has owner NEWUSER:NEWUSER, which when I log into the system that user/group exists. the error from write_files is OSError: Unknown user or group: 'getpwnam(): name not found:   so perhaps that user isn't created yet?
[21:25] <harlowja_> smoser seems like we are good to go
[21:25] <harlowja_> [self._process.terminate,
[21:25] <harlowja_>                           self._process.terminate,
[21:25] <harlowja_>                           self._process.kill]
[21:25] <harlowja_> oops
[21:25] <harlowja_> https://openstacksummitmay2015vancouver.sched.org/event/b52d0c99f65d7713c61524b5a380812b?iframe=no&w=&sidebar=yes&bg=no#.VQyQD2avL-9
[21:25] <harlowja_> that one ^
[21:25] <harlowja_> lol