2017-10-10 21:55:47 |
Andres Rodriguez |
bug |
|
|
added bug |
2017-10-10 21:55:53 |
Andres Rodriguez |
maas: milestone |
|
2.3.0beta3 |
|
2017-10-11 13:50:27 |
Michael Iatrou |
bug |
|
|
added subscriber Michael Iatrou |
2017-10-12 15:24:48 |
Andres Rodriguez |
maas: importance |
Undecided |
High |
|
2017-10-12 15:24:50 |
Andres Rodriguez |
maas: status |
New |
Triaged |
|
2017-10-13 13:57:33 |
Andres Rodriguez |
description |
Trying to delete a pod that's gone, I'm unable to provided that the pod is gone:
Unable to decompose machine because: Failed talking to pod: Failed to login to virsh console. |
I deleted a machine that was running a POD, however, I'm unable to delete the machines from that pod or the pod itself.
Unable to decompose machine because: Failed talking to pod: Failed to login to virsh console. |
|
2017-10-13 13:57:48 |
Andres Rodriguez |
description |
I deleted a machine that was running a POD, however, I'm unable to delete the machines from that pod or the pod itself.
Unable to decompose machine because: Failed talking to pod: Failed to login to virsh console. |
I deleted a machine that was running a POD, however, I'm unable to delete the machines from that pod or the pod itself. This is obviously a problem because the pod really no longer exists.
Unable to decompose machine because: Failed talking to pod: Failed to login to virsh console. |
|
2017-10-13 14:03:27 |
Andres Rodriguez |
description |
I deleted a machine that was running a POD, however, I'm unable to delete the machines from that pod or the pod itself. This is obviously a problem because the pod really no longer exists.
Unable to decompose machine because: Failed talking to pod: Failed to login to virsh console. |
I deleted a machine that was running a POD, however, I'm unable to delete the machines from that pod or the pod itself. This is obviously a problem because the pod really no longer exists.
"Unable to decompose machine because: Failed talking to pod: Failed to login to virsh console."
I would imagine that we need to be smart about this and do:
- if we are releasing a machine, or decomposing the machine, then it should definitely fail to decompose.
- if we are deleting the machine or the pod, since we are confirming the deletion via the UI, then we should definitely force the deletion. |
|
2017-10-13 14:04:06 |
Andres Rodriguez |
description |
I deleted a machine that was running a POD, however, I'm unable to delete the machines from that pod or the pod itself. This is obviously a problem because the pod really no longer exists.
"Unable to decompose machine because: Failed talking to pod: Failed to login to virsh console."
I would imagine that we need to be smart about this and do:
- if we are releasing a machine, or decomposing the machine, then it should definitely fail to decompose.
- if we are deleting the machine or the pod, since we are confirming the deletion via the UI, then we should definitely force the deletion. |
I deleted a machine that was running a POD, however, I'm unable to delete the machines from that pod or the pod itself. This is obviously a problem because the pod really no longer exists.
"Unable to decompose machine because: Failed talking to pod: Failed to login to virsh console."
I would imagine that we need to be smart about this and do:
- if we are releasing a machine, or decomposing the machine, then it should definitely fail to decompose.
- if we are deleting the machine or the pod, since we are confirming the deletion via the UI, then we should definitely force the deletion.
It seems that the function decompose_machines where this error is surfaced, should actually be receiving the action being told to differentiate whether this comes from a delete or from a simple release/decompose. |
|
2017-10-13 14:04:25 |
Andres Rodriguez |
maas: assignee |
|
Newell Jensen (newell-jensen) |
|
2017-10-17 12:43:48 |
Andres Rodriguez |
maas: status |
Triaged |
In Progress |
|
2017-10-17 21:13:06 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~newell-jensen/maas/+git/maas/+merge/332387 |
|
2017-10-18 05:34:17 |
MAAS Lander |
maas: status |
In Progress |
Fix Committed |
|
2017-10-30 13:53:32 |
Andres Rodriguez |
maas: status |
Fix Committed |
Fix Released |
|