local provider stops bootstrapping: "Job is already running"

Bug #1403151 reported by Nick Moffitt
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Low
Unassigned

Bug Description

While doing a lot of destroy-environment/bootstrap/mojo run in a fairly tight loop, I somehow got my local environment in a state where it will no longer bootstrap. I probably ^C'd it at some inopportune time.

output of juju bootstrap attached.

Revision history for this message
Nick Moffitt (nick-moffitt) wrote :
Revision history for this message
Nick Moffitt (nick-moffitt) wrote :

$ sudo stop juju-agent-nick-mojo
stop: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist

That error message aside, this seems to have fixed it.

Revision history for this message
Tim Penhey (thumper) wrote :

I think if you had done 'juju destroy-environment --force' after that error happened it "should" have fixed it. If this happens again, can you try that?

Changed in juju-core:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Nick Moffitt (nick-moffitt) wrote : Re: [Bug 1403151] Re: local provider stops bootstrapping: "Job is already running"

Tim Penhey:
> I think if you had done 'juju destroy-environment --force' after that
> error happened it "should" have fixed it. If this happens again, can
> you try that?

I tried that several times before happening upon the workaround
described above. It did not fix this!

--
Nick Moffitt

Curtis Hovey (sinzui)
tags: added: bootstrap local-provider
Revision history for this message
Kit Randel (blr) wrote :

I'm able to reproduce this fairly regularly on 1.20.14-utopic-amd64.

Revision history for this message
Nick Moffitt (nick-moffitt) wrote :

Could someone please take this bug out of incomplete? The advice given was tried long before the bug was filed, and others have confirmed the behaviour.

blr: Can you work around it by running `sudo stop juju-agent-<username>-<env>` after you `juju destroy-environment --force`? You should be able to tab-complete the full name of that.

Revision history for this message
Kit Randel (blr) wrote :

Yep, that workaround does the trick Nick.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju-core because there has been no activity for 60 days.]

Changed in juju-core:
status: Incomplete → Expired
Revision history for this message
Nick Moffitt (nick-moffitt) wrote :

The fact that there was no activity on this bug was not my fault. Could someone please now take it out of expired?

Changed in juju-core:
status: Expired → Confirmed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.