=== Guest20946 is now known as mgagne
[12:43] <do3meli> anyone able to tell me how to activate debug logging for a specific module?
[16:56] <smoser1> do3meli: you can't turn it on per module like that.
[16:56] <smoser1> generally at this point DEBUG gets written to /var/log/cloud-init.log
[16:57] <smoser1> youc an run individual modules: cloud-init single --name=apt_configure --frequency=always
[16:57] <do3meli> thanks smoser1, i realized that and found the correct log file later on ;-)
[17:00] <smoser1> do3meli: your mp at https://code.launchpad.net/~d-info-e/cloud-init/+git/cloud-init/+merge/340112 needs to be rebased to master
[17:00] <smoser1> git fetch origin
[17:00] <smoser1> (or git fetch upstream)
[17:00] <smoser1> dependening on what is the name of the upstream one
[17:00] <smoser1> then
[17:00] <smoser1> git checkout master
[17:00] <smoser1> git merge --ff-only
[17:00] <smoser1> git checkout salt-freebsd-patch
[17:00] <smoser1> git rebase -i master
[17:02] <do3meli> hmm de rebase would just pick 2 commits:
[17:03] <do3meli> pick dbc395c salt-minion module now works on FreeBSD
[17:03] <do3meli> pick bee5b16 adjust formatting
[17:03] <do3meli> would that be correct?
[17:05] <smoser1> correct
[17:05] <smoser1> those are the 2 commits that you have made
[17:05] <smoser1> right ?
[17:05] <smoser1> and you just want those moved on top of master
[17:05] <smoser1> we *had* fixed the deb install issue you saw in trunk
[17:05] <smoser1> but you are off an older version of trunk, so you dont have that fix.
=== smoser1 is now known as smoser
[17:19] <smoser> do3meli: that make sene ?
[17:19] <smoser> sense
[17:23] <do3meli> hmmm...really. i am confused. because created a brand new branch from upstream/master (in my case origin. but its the upstream)
[17:24] <do3meli> i followed the steps in HACKING.rst as you mentioned to me yesterday.
[17:25] <do3meli> well. anyway. let me try again ;-)
[18:11] <smoser> powersj, rharper, blackboxsw, dpb1 . i think i had written this somewhere before. but... lost it.
[18:11] <smoser> https://hackmd.io/KwUwDAnAxgJgbARgLQA4DsAzCSAsBDHFVCBDJKNPAIzmDQgGY0pgg===
[18:12] <smoser> that is just a copy-and-paste if a user contributes that has not signed CLA.
=== r-daneel_ is now known as r-daneel
=== r-daneel_ is now known as r-daneel
[20:50] <Odd_Bloke> It looks like the most recent cloud-init in artful doesn't handle GCE user data any longer.
[20:50] <Odd_Bloke> I'm filing a bug now (unless someone points me at an existing one).
[20:51] <blackboxsw> ok odd_bloke, ssh handling is a bit different in gce now. certain expired keys removed etc.
[20:51] <blackboxsw> please file away, will check details. 'ubuntu-bug cloud-init'
[20:53] <Odd_Bloke> blackboxsw: https://bugs.launchpad.net/cloud-init/+bug/1752711
[20:53] <ubot5`> Ubuntu bug 1752711 in cloud-init "cloud-init no longer processes user data on GCE in artful" [Undecided,New]
[20:53] <Odd_Bloke> Yeah, this seems more fundamental than that.
[20:54] <blackboxsw> thanks looking now
[20:54] <Odd_Bloke> Hopefully I'm just doing something wrong.
[20:54] <Odd_Bloke> That wasn't filed with ubuntu-bug; is there a way I can add the ubuntu-bug information after the fact?
[20:56] <blackboxsw> cloud-init collect-logs
[20:56] <rharper>  #/bin/sh
[20:56] <rharper> that's missing the the bang, no ?
[20:57] <smoser> Odd_Bloke: apport_collect
[20:57] <blackboxsw> Odd_Bloke: ^ cloud-init collect-logs:   that'll grab a tarfile of all data/logs to attach to bugs when filed after the fact
[20:57] <smoser> err... apport-collect
[20:57] <Odd_Bloke> rharper: Ah, yeah, so it is.
[20:57] <Odd_Bloke> rharper: We are seeing this in automated testing as well, which doesn't have that typo.
[20:57] <Odd_Bloke> (Also, would that cause cloud-init to not even store it in /var/lib/cloud?)
[20:57] <rharper> huh, the % cat thingy made me thing it was a real cat
[20:58] <rharper> nothing in /var/lib/cloud at all ?
[20:58] <rharper> did cloud-init run ? cloud-init status says ?
[20:58] <Odd_Bloke> rharper: That was a real cat from the actual file I manually ran this with.
[20:59] <rharper> ok, then the file is broken, it's not going to execute, right ?
[20:59] <Odd_Bloke> I've just reproduced with the bang.
[21:02] <rharper> ok, did you use something else besides /tmp ?
[21:02] <rharper> systemd likes to clean /tmp and /var/tmp for you
[21:03] <rharper> touch /ubuntu-is-awesome
[21:08] <Odd_Bloke> Trying now.
[21:09] <Odd_Bloke> Yeah, still not working.
[21:10] <rharper> ok; and any way to get the logs of those and attached ?
[21:12] <Odd_Bloke> Yeah, will do so after this meeting.
[21:28] <smoser> blackboxsw: http://paste.ubuntu.com/p/s7DQJrvTKn/
[21:29] <blackboxsw> smoser there's aslo a 2nd part that handled encoded user-data
[21:29] <smoser> its there still
[21:30] <blackboxsw> ahh right you're paste manipulates that content
[21:37] <rharper> smoser: blackboxsw: Odd_Bloke: It looks like the recent change to GCE source dropped setting md['user-data'] since the introduction of recursive query of instance/attributes URL;
[21:38] <rharper> blackboxsw is confirming
[21:38] <Odd_Bloke> Ack.
[21:38] <Odd_Bloke> Thanks for the speedy response. :)
[21:39] <blackboxsw> smoser your fix is good.
[21:40] <smoser> the main is useful :)
[21:40] <rharper> yes
[21:40] <smoser> https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/340248
[21:40] <smoser> i'll add a unit test
[21:43] <blackboxsw> smoser: when's EOD for you ? I will shepherd that in once I re-test on gce with changes. Also time to  expand our manual tests to include  user-data on all clouds
[21:43] <smoser> ok. i have 20 minutes.
[21:43]  * blackboxsw will flag regression to stop xenial from getting an update
[21:43] <blackboxsw> (given that it's blocked
[21:44] <blackboxsw> good pt. will deploy and check
[21:49] <smoser> blackboxsw: good. thanks.
[21:49] <blackboxsw> yeah bionic is good, I see things working there in bionic.
[21:49] <blackboxsw> checking the changeset
[21:49] <smoser> why would it work in bionic?
[22:03] <blackboxsw> strike that on bionic, I provided the same #cloud-config\n hostname: <myname>  as when I used gcloud to create the instance. so I mistakenly thought user-data was observed.   It is not: bionic fail too
[22:20] <blackboxsw> Odd_Bloke: thanks for the bug, I just refiled one with the regression tags etc https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1752729 and dup'd yours
[22:20] <ubot5`> Ubuntu bug 1752711 in cloud-init (Ubuntu Artful) "duplicate for #1752729 cloud-init no longer processes user data on GCE in artful" [Critical,Confirmed]
[22:21] <blackboxsw> landing the fix today. bionic should be fixed by tomorrow and we'll SRU a cherry pick to artful
[22:21] <blackboxsw> landing the fix today. bionic should be fixed by tomorrow and we'll SRU a cherry pick to artful/xenial
[22:22] <Odd_Bloke> Ack, thanks!
[22:23] <blackboxsw> Odd_Bloke: do your automated tests run against bionic?
[22:24] <Odd_Bloke> blackboxsw: They do, but we've been having problems in the pipeline before we get to GCE image publication/test.
[22:24] <blackboxsw> ahh gotcha.
[22:49] <blackboxsw> smoser: bionic merge is up https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/340252
[22:49] <blackboxsw> and your fix has landed in tip
[23:09] <blackboxsw> xenial cherry pick https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/340256
[23:10] <blackboxsw> artful cherry pick https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/340255