juju status hangs

Bug #1413052 reported by Tim Penhey on 2015-01-21
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
juju-core
Medium
Unassigned

Bug Description

If the user has a .jenv file that points to an environment that no longer exists, the status command does not return.

I would expect the command to try for a while and then give up reporting that it was not able to connect.

Curtis Hovey (sinzui) on 2015-01-21
tags: added: status
Changed in juju-core:
milestone: none → 1.23
Wayne Witzel III (wwitzel3) wrote :

AFAICT the is caused by the openAttempt on api/apiclient.go:241

Other commands, not just juju status, also do not return. They end up in a connection retry loop with api/apiclient.go:252 dialing and api/apiclient.go:258 catching the error. And then retrying indefinitely.

I would fix, but I am not sure what we want to be using for sane value here? I noticed in that same file on api/apiclient.go:120 we have DefaultDialOpts() which has a 10 minute Timeout.

Tim Penhey (thumper) wrote :

I think that if a command can't connect in 5 seconds it should error out.

That number may be a bit arbitrary, but better than hanging forever.

Changed in juju-core:
assignee: nobody → Matthew Williams (mattyw)
status: Triaged → In Progress
Matthew Williams (mattyw) wrote :

I've taken my name off it in case someone else has time, otherwise I'll try to get to it next week

Changed in juju-core:
assignee: Matthew Williams (mattyw) → nobody
status: In Progress → Triaged
Curtis Hovey (sinzui) on 2015-04-21
Changed in juju-core:
milestone: 1.23 → none
importance: High → Medium

I can confirm this.

`juju status` and `juju list-models` all hang.
After removing ~/.local/share/juju/, everything goes well.

tags: added: papercut
Changed in juju-core:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers