[08:11] <mup> Bug #1671733 opened: harvest mode setting not honoured by destroy-model <juju:New> <juju-core:New> <https://launchpad.net/bugs/1671733>
[08:17] <mup> Bug #1671733 changed: harvest mode setting not honoured by destroy-model <juju:New> <juju-core:New> <https://launchpad.net/bugs/1671733>
[08:26] <mup> Bug #1671733 opened: harvest mode setting not honoured by destroy-model <juju:New> <juju-core:New> <https://launchpad.net/bugs/1671733>
[15:56] <mup> Bug #1670499 opened: maas 2.1.3 kvm nodes do not deploy, Juju reports 'started but not deployed'  <cdo-qa-blocker> <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1670499>
[16:05] <mup> Bug #1670499 changed: maas 2.1.3 kvm nodes do not deploy, Juju reports 'started but not deployed'  <cdo-qa-blocker> <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1670499>
[16:09] <rogpeppe1> if anyone is around, I'd appreciate a review of this PR (targetting a feature branch): https://github.com/juju/juju/pull/7087/files
[16:09] <perrito666> jam: ship it
[16:10] <perrito666> rogpeppe1: ill review
[16:10] <rogpeppe1> perrito666: ta
[16:10] <perrito666> rogpeppe1: tx for the idea yesterday btw, I wrote a dirty version for what I was doing and fixed most of the tests
[16:10] <rogpeppe1> perrito666: cool, np
[16:16] <perrito666> rogpeppe1: shipit
[16:16] <rogpeppe1> perrito666: ta!
[16:17] <mup> Bug #1670499 opened: maas 2.1.3 kvm nodes do not deploy, Juju reports 'started but not deployed'  <cdo-qa-blocker> <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1670499>
[16:21] <jam> hml: I think your fix for https://bugs.launchpad.net/juju/+bug/1671265 should go into the 2.1 series, given the regression of support for Openstack I think it is a proper Critical blocker bug
[16:21] <mup> Bug #1671265: Allowing duplicate secgroups via neutron breaks 2.0.3 models with 2.1 controllers <juju:In Progress by hmlanigan> <juju 2.1:In Progress by hmlanigan> <https://launchpad.net/bugs/1671265>
[16:23] <hml> jam: there was a question of whether 2.1.2 would release before i could get the fix out
[16:23] <jam> hml: sure. Mostly a 2.1.x
[16:23] <jam> vs just 2.2
[16:23] <jam> they won't move to an alpha to get openstack fixed
[17:14] <elmo> hey - Juju folks, does Juju need the 'ubuntu' user once the agent is up and running?
[17:15] <elmo> jam: ^- if you know
[17:17] <perrito666> elmo: afaik at least juju ssh will depend on the ubuntu user being there, I cant tell you out of the top of my head but I am pretty sure more things deppend on it (backup and restore come to mind)
[17:17] <perrito666> elmo: we are on a sprint right now so jam might not be near his computer, ill ping him as soon as I find him to see if he has more input
[17:17] <elmo> ah, maybe actions and/or juju-run?
[17:18] <perrito666> debug hooks seems to deppend on it too
[17:19] <perrito666> elmo:  I believe actions might be free of that dependency but not in every version of juju, only after we changed the way they are executed, cant say which version that happened  though
[18:01] <jam> wpk: https://github.com/juju/juju/wiki/Code-Review-Checklists
[18:02] <jam> elmo: actions are likely to run as root, and juju-run should be moving over to triggering via the actions stuff, but "juju ssh/scp" need a user and we don't want to give root an ssh key
[18:02] <jam> perrito666: elmo: 'run' is supposed to not use ssh for 2.0 (and possibly not even 1.25)
[18:03] <elmo> jam: there's no ssh key as root though; do they login as ubuntu  and su to ubuntu?
[18:04] <jam> elmo: so "juju ssh" doesn't su unless you ask it to. "juju-run" was supposed to be fixed to just run as root without ssh first
[18:04] <jam> (as in we have something watching for run requests that spawns the request directly)
[18:07] <elmo> ah, interesting
[18:08] <elmo> jam: so the unit agent kicks off both run requests and actions?
[18:08] <jam> elmo: as I understand it, yes.
[18:08] <elmo> jam: OK, thanks
[18:16] <jam> elmo: I just confirmed. I blocked port 22 and "juju ssh" doesn't work but "juju run 'echo hello'" works
[18:33] <abentley> jam, elmo: In fact, I filed a bug about this, as the behaviour changed in 2.x and no longer matches the docs: https://bugs.launchpad.net/juju/+bug/1628593
[18:33] <mup> Bug #1628593: Juju run runs as root, not 'ubuntu' <jujuqa> <run> <juju:Triaged> <juju 2.0:Won't Fix> <https://launchpad.net/bugs/1628593>
[19:39] <elmo> https://pastebin.canonical.com/182159/
[19:39] <elmo> so, yeah - debug hooks and restore
[19:39] <elmo> it looks l;ike
[19:39] <elmo> actions are definitely api/agent driven