Comment 8 for bug 2028284
Revision history for this message
| Björn Tillenius (bjornt) wrote Re: vm compose fails with - This "instances" entry already exists | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
demo site
(Get the code!)
In the long term, we should make the compose form handle conflict errors. One idea is that add a user.* isntance property containing the maas system id, so that we know that MAAS created the instance and can handle deletion of it if necessary.
In the short term, we can make BMC.sync_hints() a bit smarter and not save anything if nothing changed. Currently only virsh is actually returning any hints when composing a machine. And only LXD is sending commissioning results in the post commit hook.