[08:13] <mup> Bug #1599402 opened: read-only users: unauthorized access to read-only functionalities <juju-core:New> <https://launchpad.net/bugs/1599402>
[12:58] <mup> Bug #1599503 opened: Cannot upgrade charm if storage is modified, even if the service doesn't use said storage <juju-core:New> <https://launchpad.net/bugs/1599503>
[13:04] <mup> Bug #1599507 opened: juju status show blank for public name for one machine. <juju-core:New> <https://launchpad.net/bugs/1599507>
[13:40] <mgz> dooferlad: bug 1450729
[13:40] <mup> Bug #1450729: juju should be able to use nodes acquired by the same user in MAAS <cloud-installer> <deploy> <landscape> <maas-provider> <juju-core:Triaged> <MAAS:Opinion> <https://launchpad.net/bugs/1450729>
[14:32] <mup> Bug #1599507 changed: juju status show blank for public name for one machine. <juju-core:New> <OPNFV:New> <https://launchpad.net/bugs/1599507>
[14:55] <aisrael> cherylj: Could you take a new look at https://bugs.launchpad.net/juju-core/+bug/1287665? We ran into this issue during customer meetings last week in Madrid.
[14:55] <mup> Bug #1287665: Export bundle without juju GUI <canonical-is> <deployer> <sts-support> <juju-core:Triaged> <juju-deployer:New> <https://launchpad.net/bugs/1287665>
[14:56] <cherylj> aisrael: sure
[14:58] <cherylj> aisrael: we are already fully booked for 2.1 and the remaining 2.0 work.  We can put this on a wish list, but I wouldn't be optimistic about getting it any time soon :(
[14:59] <aisrael> cherylj: ack, thanks for looking
[15:02] <cherylj> aisrael: just fyi - it's already on the "feature request" list:  https://github.com/juju/juju/wiki/Feature-Requests
[15:02] <aisrael> cherylj: excellent, thanks!
[15:03] <cherylj> aisrael: the idea is that we would look there for features when we make our plans, but we were already overcommitted for 2.1
[15:04] <aisrael> cherylj: Understood. I'll check juju-bundlizer to see if that can be updated to work with the new API in the meantime
[15:06] <aisrael> deployerizer, rather
[15:50] <mup> Bug #1599315 changed: LXD no longer gets correct network in JUJU beta11 and MAAS2rc1 <network> <juju-core:Invalid> <https://launchpad.net/bugs/1599315>
[16:17] <marcoceppi> aisrael: it might be worth renaming deployerizer to something like `juju get-bundle` to make it clearer what it's doing?
[16:18] <marcoceppi> cherylj: I also noticed that the hook-tool descriptions are out of date as of beta11, they still reference "service"
[16:18] <rick_h_> but 'deployerizer' is so cool! It seems like a james bond weapon.
[16:19] <aisrael> marcoceppi: ack, I agree. I kept typing it as bundlizer because name =/= functionality
[16:19] <cherylj> marcoceppi: oh, thanks for finding that.  Want to open a bug, or should I?
[16:19] <marcoceppi> cherylj: https://bugs.launchpad.net/juju-core/+bug/1599570
[16:19] <mup> Bug #1599570: hook-tool help messages still reference service <juju-core:New> <https://launchpad.net/bugs/1599570>
[16:19] <cherylj> there ya go
[16:19] <cherylj> thanks :)
[16:20] <mup> Bug #1599570 opened: hook-tool help messages still reference service <juju-core:New> <https://launchpad.net/bugs/1599570>
[18:56] <mup> Bug #1599612 opened: remove-application has unexpected output with subordinate units <juju-core:New> <https://launchpad.net/bugs/1599612>
[22:15] <mup> Bug #1573020 changed: upgrade-charm --path does not recognize dot <juju-release-support> <upgrade-charm> <juju-core:Triaged> <https://launchpad.net/bugs/1573020>
[22:15] <mup> Bug #1576346 changed: upgrade-charm with a local charm fails with trailing slash <juju-release-support> <papercut> <upgrade-charm> <juju-core:Triaged> <https://launchpad.net/bugs/1576346>