=== shardy_afk is now known as shardy [22:37] hey guys, ltns [22:37] i think i will have 2 small changes to push shortly [22:38] before i push the bigger of the 2, just curious if folks ever have issues with package_command from within cloud-init [22:38] from time to time on RHEL we had issues with yum just failing...no clear reason why [22:53] hmmmm, yum is just problematic in general [22:53] *imho its a pile of crap, ha [22:55] what errors do u see ctracey [22:55] hey, i wouldnt disagree [22:55] well, we dont see errors only bc capture=False [22:55] hmmm [22:56] so, my change is simply to allow for debugging package_command [22:56] just wondering if anyone else had encountered it [22:56] i haven't [22:57] but i haven't used that feature to much [22:57] basically I would propose system_info: debug_package_command: true [22:57] seems to make sense [22:57] to you can at least grab the output as necessary [22:57] yahoo has a whole other way to install stuff (like juju in a way) [22:57] ah, interesting [22:57] but ya, i think debug package command makes sense [22:57] the other issue we ran into was a 2.7 vs 2.6 thing [22:58] buried in the AzureDataSource [22:58] ah, blame smoser for that one, ha [22:58] :-P [22:58] (yes, we are on an ancient python release) [22:58] :) [22:58] its a simple fix [22:58] ill get them in tonight most likely [22:58] cool [22:58] sounds great [22:59] harlowja: you going to HK? [22:59] sure am [22:59] niiiice [22:59] i'll see ya there then :) [23:00] cool [23:59] ctracey, yeah. i'm sorry about that. [23:59] but wrt debug_package_command [23:59] that output shoudl be caught by [23:59] output: {all: '| tee -a /var/log/cloud-init-output.log'} [23:59] is it not?