Canonical Juju

[2.8-rc1][lxd] lxd provider failing to perform destructive operations

Bug #1879571 reported by james beedy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

Using 2.8-rc1 with the localhost/lxd provider, I cannot perform any operations that deal with removing units; kill a controller, remove-machine, remove-application, remove-unit, etc etc - the instances never die.

I have been able to reproduce this multiple times now by bootstrapping lxd and then trying to preform a destructive operation.

https://paste.ubuntu.com/p/TSD5hKPZvt/

I can use `lxc delete` to remove the instances, following the manual removal of the lxc instances, juju destructive commands will succeed https://paste.ubuntu.com/p/9wXm7D6wvv/.

See original description
james beedy (jamesbeedy)
summary: - [2.8-rc1][lxd] lxd provider failing to preform any destructive
- operations on machine resources
+ [2.8-rc1][lxd] lxd provider failing to preform destructive operations
summary: - [2.8-rc1][lxd] lxd provider failing to preform destructive operations
+ [2.8-rc1][lxd] lxd provider failing to perform destructive operations
description: updated
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

I'm hitting this as well. I've worked around it with:

for each model including controller:
      * juju destroy-model --force -y <model-name>
then:
* juju kill-controller -y -t 0 <controller-name>

Changed in juju:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Tim Penhey (thumper) wrote : Re: [Bug 1879571] Re: [2.8-rc1][lxd] lxd provider failing to perform destructive operations

I struggled to reproduce this today. Removing units worked fine, and it
removed the machine that the unit was on. Removing the model with an active
unit and machine worked fine as well.

There does seem to be a problem with a stale CMR offer causing issues
removing applications / destroying the model.

Do you have more details about what you were doing?

On Thu, May 21, 2020 at 2:21 AM Heather Lanigan <email address hidden>
wrote:

> I'm hitting this as well. I've worked around it with:
>
> for each model including controller:
> * juju destroy-model --force -y <model-name>
> then:
> * juju kill-controller -y -t 0 <controller-name>
>
>
> ** Changed in: juju
> Importance: Undecided => High
>
> ** Changed in: juju
> Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: Juju bugs
> https://bugs.launchpad.net/bugs/1879571
>
> Title:
> [2.8-rc1][lxd] lxd provider failing to perform destructive operations
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1879571/+subscriptions
>

Revision history for this message
Heather Lanigan (hmlanigan) wrote :

@jamesbeedy, can you reproduce this if the unit/machine etc are not in an error state?

Typically tear down when in an error state requires --force.

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: High → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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