[15:39] <larsks> smoser: harlowja: any thoughts on a 0.7.7 release date?
[15:41] <smoser> not really. it'd be good to releas one soon.
[15:42] <larsks> I ask for selfish reasons: I would like to not be carrying the rh_subscription plugin as a patch in our packages :)
[15:50] <larsks> My life would be so much easier if it were possible to disable individual plugins without having to replace the entire cloud_*_modules key.
[16:26] <larsks> smoser: I am making some changes to the rh_subscription module.  Should I be working with launchpad bzr repo, or github repo, and if the latter, master or 0.7.x branch?
[16:26] <larsks> It looks like 0.7.x branch at least as a .gitreview, which the launchpas bzr does not...
[16:28] <larsks> smoser: but oh, there are more recent changes in launchpad bzr. Halp!
[16:29] <larsks> harlowja: ^^^ >
[16:29] <larsks> ?
[16:31] <smoser> larsks, harlowja  made me promise to not push trunk change to bzr
[16:31] <smoser> the goal to get to git.
[16:32] <larsks> Okay...but 0.7.x seems more recent in bzr.
[16:32] <larsks> Hence my confusion :)
[16:33] <larsks> If I want to ultimately get a change into 0.7.7, where should I put that?
[18:44] <larsks> Uuuuuugh, rh_subscription exists in lp, but not on github.
[19:01] <harlowja> larsks yes its confusing :-P
[19:01] <harlowja> larsks i will try to get the github repo in sync with bzr (then i guess no more changes ever on bzr, lol)
[19:02] <harlowja> if smoser presses the big red button
[19:02] <larsks> I have a patch I want to submit; should I wait for you to finish syncing things?
[19:03] <harlowja> smoser smoser smoser  come in over
[19:03] <harlowja> ;)
[19:08] <harlowja> larsks sooo once i get smoser to press the big button, i will commence the request to git sync again
[19:09] <larsks> Okay. I gueass I will wait a bit and watch.
[19:09] <harlowja> :)
[21:51] <j12t> Getting exit 1 with minimal cloud.cfg file on EC2. No error message I can find. How can I debug this?
[22:20] <j12t> Seem the main cloud-init script returns an error code if there were errors, but it does not actually print the errors.
[22:20] <j12t> "print v1" at the end of status_wrapper in cloud-init script did wonders to explain my configuration error to me
[22:51] <larsks> j12t: if you're booting a rhel/fedora/centos image, then "journalctl | grep -i cloud" often yields lots of good information.
[23:00] <j12t> larsks: this is a custom version of Arch, but should be no different re what's in the journal. the trouble is, not all error messages are in the journal or anywhere else it seems ...