New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot restore backed up TemplateVMs #2353

Closed
desmond-decker opened this Issue Oct 1, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@desmond-decker

When restoring a backed up TemplateVM, the backup manager will not allow restoring VMs that have the same name as an existing VM. For encrypted backups of standard TemplateVMs (eg Fedora-23) this means restoring the backup is impossible, as there is no way to rename existing TemplateVMs that are installed from RPM.

QVVM displays this message when attempting to rename Fedora-23: "Cannot rename VM installed by RPM -- first clone VM and then use yum to remove package". Cloning the VM and then removing Fedora-23 with yum still doesn't allow restoring of the backed up Fedora-23 VM, and breaks all associated App and System VMs. Renaming the backed-up TemplateVMs in the backup manager is not possible either.

A mechanism for restoring TemplateVMs with a new name from within the backup manager would fix the issue. Either that or inform users that they need to clone and rename RPM-installed TemplateVMs before backing them up.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Oct 1, 2016

Member

Have you tried the --rename-conflicting option?

Member

andrewdavidwong commented Oct 1, 2016

Have you tried the --rename-conflicting option?

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Oct 20, 2016

Member

Closing due to lack of response. Please comment or re-open if this is still an issue.

Member

andrewdavidwong commented Oct 20, 2016

Closing due to lack of response. Please comment or re-open if this is still an issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment