juju status <service-name> stuck

[Junaid Ali]

Hi,

I'm having an issue on juju status command. It stucks when I run the command for a service e.g

juju status nova-cloud-controller

although
$ juju status
 and
$ juju status --format tabular
works fine.

Version of juju that I'm using is 1.25.6. Let me know please if any workaround available for this issue or what logs to share if this is a bug.

[Alexis Bruemmer (alexis-bruemmer)]

can you please post the machine-0.log ($ juju ssh 0 ls -al /var/log/juju) for further debugging.

[Tim Penhey (thumper)]

@Junaid, if you are able to set the environment logging to trace, and then attempt the 'juju status <service>', and attach the logs. Setting the logging to trace will mean that if something asks for cloud credentials, that will be shown in the clear, so please don't send everything indiscriminately. The trace level will show both the request from the cli and the server response (assuming there is one).

You can change the logging config of a running server by doing this:

juju set-env logging-config="juju=trace"

and set it back to normal with

juju set-env logging-config="juju=warn"

or debug with

juju set-env logging-config="juju=debug"

[Junaid Ali (junaidali)]

Hi Alexis, I'll get the setup access again today, will post the logs soon.

[Julian Neytchev (juliann)]

Clarification:
juju status <charm> works as expected.
juju stat <charm> hangs.
Attaching logs from bootstrap, did not see the message about verbose logging on time, can ask the affected party to reproduce them with trace on if needed.

[Tim Penhey (thumper)]

It seems like you have an alias or plugin for 'stat'

Go `juju help stat`, or see if you `which juju-stat` will let you know if there is a plugin being called.

[Julian Neytchev (juliann)]

Sorry about the confusion. Final clarification:

juju stat or juju status is working as expected.
juju status <service-name> or juju stat <service-name> is taking nearly an hour to respond.

The only thing different in the environment is the fact that we are using an upstream DNS server. So on the MAAS node, we have configured bind9 to forward non local queries to another DNS server.

[Alexis Bruemmer (alexis-bruemmer)]

juju status <app>

and

juju status nova-cloud-controller

are working fine in our testing w/ juju 2.0 and maas 2.0. Please re-open the bug if you are still seeing this issue on juju 2.0

[Junaid Ali (junaidali)]

Hi Alexis, juju version being used is 1.25.6
As mentioned by Julian in comment#6, juju status <service-name> takes around an hour to respond. He has shared the bootstrap node logs too. Could you please help us to identify from the logs, what might be the cause if its not a bug?

Thanks.