[06:56] morning all o/ [06:59] I'm having an issue when using the cloud-init chef functionality on a box that already has chef installed on it. Cloud init appears to be doing nothing, doesnt change the client.rb or the firstboot.json :S Is there an issue using it on a box with chef already installed? (cloud-init 0.7.5) [07:02] actually it appears that the force_install isn't taking hold either. Testing this on a Centos7 machine. === rangerpbzzzz is now known as rangerpb === rangerpb is now known as rangerpbzzzz [14:04] NerdyBiker: not that I know of, can you file a bug in launchpad and provide some user-data and possibly the cloud-init.log from a failed run ? [14:56] NerdyBiker, there were recent-ish fixes in that area === rangerpbzzzz is now known as rangerpb [16:00] so we’ve been testing with the following patches the last couple days (under RHEL7) and they’re working well, and are interested in getting these merged soonish so we can get off our fork. what can we do to help move these forward and make that happen? [16:00] https://code.launchpad.net/~harlowja/cloud-init/+git/cloud-init/+merge/305882 [16:00] https://code.launchpad.net/~nrezinorn/cloud-init/+git/cloud-init/+merge/306562 [16:06] mdorman_: thanks for the feedback and testing on those [16:06] smoser: is on a merge mission today [16:06] so hopefully soon [16:19] powersj, magicalChicken [16:19] while ! lxc exec "$name" -- [ -f /run/cloud-init/result.json ]; do sleep 1; done === rangerpb is now known as rangerpbzzzz [16:27] rharper: cool thanks. please ping me or nrezinorn if we can do anything to help [16:28] nrezinorn, ok. i'll take alook [16:28] i have one of nrezinorn's others. [16:28] sorry mdorman_ [16:35] cool [16:39] smoser: I did have another question, do you use root to run bddeb? [16:39] bddeb shoudl run as non-root [16:39] i think === mdorman_ is now known as mdorman [16:40] powersj: smoser: right; you don't need root [16:40] without it I got permission errors on some files in /etc/cloud/* [16:40] after installing ? [16:40] not following [16:41] while building, let me pastebin [16:41] k [16:41] it's basically doing a debuild -us -uc (after creating tarball of the git repo in a tempdir) [16:43] https://paste.ubuntu.com/23354559/ [16:43] (although it is apparently all on one line lol) [16:44] powersj: what does git status show ? [16:44] clean [16:44] On branch master [16:45] somethings not right, the maas-99 is only present on images that have been deployed via maas [16:45] Your branch is up-to-date with 'origin/master'. [16:45] nothing to commit, working directory clean [16:45] maybe something in ENV [16:45] for example, you'll not find the maas.cfg file in cloud-init/config/ [16:45] rharper: ah so this is on torkoal our baremetal slave, where we want to run ci integration [16:45] but it's mentioned in the output [16:45] I wonder if we have a leak in importing config [16:51] nTraceback (most recent call last):\n File "/tmp/tmpvkejmell/cloud-init-0.7.8-19-g7ae2011/tests/unittests/test_data.py", line 375, in test_unhandl [16:51] powersj: looks like unittest isn't mocking path [16:51] when it attempts to read config [16:51] powersj: can you file a bug ? [16:52] rharper: sure! [16:58] LP# 1635350 [17:09] harlowja, ping [17:10] http://paste.ubuntu.com/23354699 [17:10] those are on top of your sys-io-errors ... thoughts ? [17:14] smoser seems ok with me [17:16] i commented on the merge [17:16] just hit submit [17:16] are you able to test those easiliy-ish ? [17:18] mdorman and nrezinorn are in a better place to test it in a fully image [17:18] but i can do basic stuff [17:18] (they are in part the image builders/owners) [17:18] @godaddy [17:23] so what exactly is the question? [17:25] mdorman nothing yet, will get back to u :) [17:26] kk [18:28] mdorman, ok. so for the first one, i put a comment ther... it'd be nice to test my changes. [18:28] and commented on the second one also. [18:28] i could put toether a suggested diff if you want. [18:32] yeah that would be helpful. i’m hoping to work on these this afternoon