juju debug-log returns not logged-in error

[Scott Croft]

Juju: 2.0-beta11-xenial-amd64
MAAS: 2.0RC2
Ubuntu: 16.04

When executing "juju debug-log" the following error is reported:

ERROR login expired

Executing a juju login:

ubuntu@OrangeBox56:~/sademos/openstack$ juju login
username: admin
password:
You are now logged in to "maas-controller" as "admin@local".

ubuntu@OrangeBox56:~/sademos/openstack$ juju debug-log
ERROR login expired

[Cheryl Jennings (cherylj)]

Scott - would you be able to grab machine-0.log from the controller model and attach it to the bug?

[Scott Croft (secroft)]

Let me see if it still has the information. I've upgraded to beta12 since
that happened, but I will if it's there

On Tue, Jul 19, 2016 at 2:51 PM, Cheryl Jennings <
<email address hidden>> wrote:

> Scott - would you be able to grab machine-0.log from the controller
> model and attach it to the bug?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1603176
>
> Title:
> juju debug-log returns not logged-error
>
> Status in juju-core:
> Triaged
>
> Bug description:
> Juju: 2.0-beta11-xenial-amd64
> MAAS: 2.0RC2
> Ubuntu: 16.04
>
> When executing "juju debug-log" the following error is reported:
>
> ERROR login expired
>
> Executing a juju login:
>
> ubuntu@OrangeBox56:~/sademos/openstack$ juju login
> username: admin
> password:
> You are now logged in to "maas-controller" as "admin@local".
>
> ubuntu@OrangeBox56:~/sademos/openstack$ juju debug-log
> ERROR login expired
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1603176/+subscriptions
>

--
Scott Croft
Solutions Architect
Canonical
469-664-9453
GPG: 43E9 E8E0 F187 A685 74F7 0CA2 5960 5767 7B53 E16F

[Sandor Zeestraten (szeestraten)]

I am hitting the same issue in Juju 2.0-beta13-xenial-amd64.

If I login as another user (not default admin user) and try to run "juju debug-log" I get "ERROR login expired".

I assume that regular users (at least those granted with read permissions) should be able to access debug logs, though that is not clear in the docs.