OpenStack Compute (nova)

libvirt deletes VM configuration file after editing uuid

Bug #940539 reported by Shevek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned
libvirt
Expired
High
libvirt (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

https://bugzilla.redhat.com/show_bug.cgi?id=797281

Description of problem:

libvirt deleted the XML configuration file for a VM after an edit.

Version-Release number of selected component (if applicable):

ii libvirt-bin 0.9.2-4ubuntu15
ii libvirt0 0.9.2-4ubuntu15

How reproducible: 100%

Steps to Reproduce:
1. Create and define a VM, but do not start it.
2. virsh edit the VM.
3. Change the UUID
4. Save and exit the editor.
5. Error message appears:
error: operation failed: domain 'orchestra' already exists with uuid
4dd4e4bc-ec46-d7b8-5935-cbd727dd89c0
6. Observe XML file in /etc/libvirt/qemu now gone, and never called me mother.

Actual results:
XML file vanished, and VM config lost to posterity.

Expected results:
VM config should still exist, with an updated UUID.
libvirt should honour the updated UUID.

Revision history for this message
In , Shevek (shevek-redhat-bugs) wrote :

Description of problem:

libvirt deleted the XML configuration file for a VM after an edit.

Version-Release number of selected component (if applicable):

ii libvirt-bin 0.9.2-4ubuntu15 ii libvirt0 0.9.2-4ubuntu15

How reproducible: 100%

Steps to Reproduce:
1. Create and define a VM, but do not start it.
2. virsh edit the VM.
3. Change the UUID
4. Save and exit the editor.
5. Error message appears:
error: operation failed: domain 'orchestra' already exists with uuid 4dd4e4bc-ec46-d7b8-5935-cbd727dd89c0
6. Observe XML file in /etc/libvirt/qemu now gone, and never called me mother.

Actual results:
XML file vanished, and VM config lost to posterity.

Expected results:
VM config should still exist, with an updated UUID.
libvirt should honour the updated UUID.

Revision history for this message
Shevek (r-launchpad-anarres-org) wrote :

I was asked to duplicate this here as pertinent to Nova.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

@Shevek,

thanks for taking the time to report this bug.

In your report, you say that the original xml file disappeared. For me, the original xml file did not disappear. Can you try again and confirm that that happens for you? It makes a significant difference in the importance of this bug if that can happen.

summary: - libvirt deletes VM configuration file after edit
+ libvirt deletes VM configuration file after editing uuid
Changed in libvirt (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
importance: Medium → High
importance: High → Medium
Revision history for this message
In , Dave (dave-redhat-bugs) wrote :

Hmm, I tried your steps to reproduce, but I am unable to reproduce this behavior on libvirt 0.9.6. I see the message about domain already exists with uuid..., but the VM is unaffected following the attempt to edit it. What version of libvirt are you using?

Tom Fifield (fifieldt)
Changed in nova:
status: New → Incomplete
Revision history for this message
Thierry Carrez (ttx) wrote :

We cannot solve the issue you reported without more information. Could you please provide the requested information ?

Revision history for this message
Thierry Carrez (ttx) wrote :

This bug lacks the necessary information to effectively reproduce and fix it, therefore it has been closed. Feel free to reopen the bug by providing the requested information and set the bug status back to ''New''.

Changed in nova:
status: Incomplete → Invalid
Revision history for this message
Chris J Arges (arges) wrote :

I was unable to reproduce this on Xenial/Wily. I edited the UUID and had to also edit the name. This creates an additional domain with the new name and UUID. If this bug still affects you please re-open with the affected version. Thanks

Changed in libvirt (Ubuntu):
status: Confirmed → Incomplete
Shevek (r-launchpad-anarres-org)
Changed in libvirt (Ubuntu):
status: Incomplete → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in libvirt:
importance: Unknown → High
status: Unknown → Expired
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.