JoaoJandre commented on PR #10140: URL: https://github.com/apache/cloudstack/pull/10140#issuecomment-3132114108
> > * Tried to configure create VM from backup in the GUI, was unable to change template. > > * Tried to configure create VM from backup in the FUI, was unable to change ISO. > > Template/ISO can only be changed if the original template/iso was deleted. It is possible to do it from API though for advanced users. Added a note in the doc [apache/cloudstack-documentation@01c0bc2](https://github.com/apache/cloudstack-documentation/commit/01c0bc287f405b338f8b80c63e7551fc6f0175c1). > Could we add either a warning or not show that part of the form when this is the case? Otherwise this would be a bad UX. > > * The form to configure VM from backup does not allow to create network if an option already exists. > > I didn't see this in my testing. https://github.com/user-attachments/assets/fd97e79a-7b07-4c1a-9f0f-fee6465edff3 Maybe it was only present in the commit I was testing. I tested it again on the latest commit and was able to create a network this time. > > * Tried to create VM from backup and delete the backup before the process ends, the deletion was allowed but the VM was not restored. I think that these processes should be either blocked from executing at the same time, or be queued. > > The processes are queued once they reach the agent. i.e, if the new instance is in Restoring state then backup is deleted, the agent will process the restore first and then backup delete. If the new instance is still being created/starting/stopping before restore, and the backup is deleted, delete is not blocked and restore will throw an error that backup is deleted. IMO this is not a must have, and I'll be happy to fix this as a future improvement. Could we map it as an issue then? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
