Deleting a machine from a KVM pod doesn't delete its disk image
Bug #1741165 reported by
Michael Iatrou
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Newell Jensen | ||
| 2.3 |
Fix Released
|
High
|
Newell Jensen | ||
Bug Description
Repro steps:
1. On a KVM pod, compose a new machine.
2. Deploy an OS on the composed machine.
3. Release the machine.
4. Delete the composed machine.
5. Observe that:
a. The machine is no longer listed in the pod
b. The disk image of the machine still exists under /var/lib/
Related branches
~mpontillo/maas:preseed-per-interface-routes--bug-1758919--2.3
- MAAS Maintainers: Pending requested
-
Diff: 1785 lines (+1501/-2) (has conflicts)17 files modifieddebian/changelog (+10/-0)
snap/snapcraft.yaml (+9/-0)
src/maasserver/bootsources.py (+3/-0)
src/maasserver/models/tests/test_userprofile.py (+3/-0)
src/maasserver/rpc/boot.py (+5/-0)
src/maasserver/static/js/angular/controllers/tests/test_nodes_list.js (+17/-0)
src/maasserver/static/partials/ipranges.html (+17/-0)
src/maasserver/static/partials/node-details.html (+134/-0)
src/maasserver/static/partials/nodes-list.html (+1017/-0)
src/maasserver/static/partials/script-results-list.html (+76/-0)
src/maasserver/tests/test_bootsources.py (+3/-0)
src/maasserver/triggers/tests/test_websocket_listener.py (+5/-0)
src/provisioningserver/import_images/boot_resources.py (+61/-0)
src/provisioningserver/import_images/tests/test_boot_resources.py (+92/-0)
src/provisioningserver/import_images/tests/test_download_resources.py (+35/-0)
src/provisioningserver/utils/tests/test_network.py (+3/-0)
utilities/release-build (+11/-2)
~newell-jensen/maas:2.3-lp1741165
- Newell Jensen (community): Approve
-
Diff: 42 lines (+6/-5)2 files modifiedsrc/provisioningserver/drivers/pod/tests/test_virsh.py (+1/-2)
src/provisioningserver/drivers/pod/virsh.py (+5/-3)
~newell-jensen/maas:lp1741165
- Alberto Donato (community): Approve
- MAAS Lander: Approve
-
Diff: 42 lines (+6/-5)2 files modifiedsrc/provisioningserver/drivers/pod/tests/test_virsh.py (+1/-2)
src/provisioningserver/drivers/pod/virsh.py (+5/-3)
Revision history for this message
| Michael Iatrou (michael.iatrou) wrote | #1 |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #2 |
| Changed in maas: | |
| status: | New → Incomplete |
Revision history for this message
| Michael Iatrou (michael.iatrou) wrote | #3 |
| Changed in maas: | |
| status: | Incomplete → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.4.0alpha1 |
| Changed in maas: | |
| milestone: | 2.4.0alpha1 → 2.4.0alpha2 |
Revision history for this message
| Newell Jensen (newell-jensen) wrote | #4 |
Revision history for this message
| Newell Jensen (newell-jensen) wrote | #5 |
Revision history for this message
| Newell Jensen (newell-jensen) wrote | #6 |
| Changed in maas: | |
| assignee: | nobody → Newell Jensen (newell-jensen) |
| status: | Triaged → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
dpkg -l | grep maas
ii maas 2.3.0-6434-g all "Metal as a Service" is a physica
ii maas-cli 2.3.0-6434-g all MAAS client and command-line inte
ii maas-common 2.3.0-6434-g all MAAS server common files
ii maas-dhcp 2.3.0-6434-g all MAAS DHCP server
ii maas-dns 2.3.0-6434-g all MAAS DNS server
ii maas-proxy 2.3.0-6434-g all MAAS Caching Proxy
ii maas-rack-cont 2.3.0-6434-g all Rack Controller for MAAS
ii maas-region-ap 2.3.0-6434-g all Region controller API service for
ii maas-region-co 2.3.0-6434-g all Region Controller for MAAS
ii python3-maas-c 2.3.0-6434-g all MAAS python API client (Python 3)
ii python3-maas-p 2.3.0-6434-g all MAAS server provisioning librarie