Bug #43855
Display error message if VM clone creation fails in new UI
Description
Create a bhyve or docker VM (using QA-Test in this example)
Create a clone of the VM QA-Test
VM Options (3 vertical dots) -> Edit -> CLONE
The clone is created (QA-Test_clone0)
Delete the clone
VM Options (3 vertical dots) -> Delete
Try to clone the same VM again
VM Options (3 vertical dots) -> Edit -> CLONE
Creating the clone silently fails.
Checked the middlewared.log
[2018/08/30 20:55:03] (ERROR) ZFSSnapshot.do_create():388 - dataset already exists
There should be an error or warning about why the clone operation failed.
Related issues
History
#2 Updated by Anonymous over 2 years ago
- Assignee changed from Anonymous to Vaibhav Chauhan
- Target version changed from Backlog to 11.2-RC1
#3
Updated by Dru Lavigne over 2 years ago
- Blocked by Bug #43866: Use unique name for cloned zvol added
#4
Updated by Dru Lavigne over 2 years ago
- Status changed from Unscreened to Blocked
- Reason for Blocked set to Dependent on a related task to be completed
#5
Updated by Dru Lavigne over 2 years ago
- Status changed from Blocked to Not Started
- Reason for Blocked deleted (
Dependent on a related task to be completed)
#6
Updated by Vaibhav Chauhan over 2 years ago
- Status changed from Not Started to In Progress
in review: https://github.com/freenas/webui/pull/1265
#7
Updated by Dru Lavigne over 2 years ago
- Subject changed from Creating a VM clone can silently fail in the new UI to Diisplay error message if VM clone creation fails in new UI
#8
Updated by Vaibhav Chauhan over 2 years ago
- Subject changed from Diisplay error message if VM clone creation fails in new UI to Display error message if VM clone creation fails in new UI
- Status changed from In Progress to Ready for Testing
#9
Updated by Timothy Moore II over 2 years ago
- File vm-clone-error.png vm-clone-error.png added
- Status changed from Ready for Testing to Passed Testing
- Needs QA changed from Yes to No
- Needs Merging changed from Yes to No
Testing with a FreeNAS Mini updated to FreeNAS-11.2-MASTER-201810020854:
Go to VMs and create Bhyve VM clonetesting. Confirm VM starts and functions, then stop VM, Edit VM, and click CLONE. VM clonetesting_clone0 is created. Start clonetesting_clone0 and confirm it functions. Stop the VM and delete it. Edit original VM clonetesting and click CLONE again. New VM clonetesting_clone0 is created and functional.
Switch to a different FreeNAS system that has an existing VM with an invalid name. Update system to FreeNAS-11.2-MASTER-201810020854 and attempt to clone VM with invalid name. Error appears:
VM clone failed. [EINVAL] vm_create.name: Only alphanumeric characters are allowed. [EINVAL] vm_create.devices.1.attributes.zvol_type: Field was not expected + More info...
This appears to match the change to VM cloning error behavior.
#10
Updated by Timothy Moore II over 2 years ago
- Needs Doc changed from Yes to No
Docs PR: [angulargui] https://github.com/freenas/freenas-docs/pull/383. No [master] PR needed.
#11
Updated by Dru Lavigne over 2 years ago
- Status changed from Passed Testing to Done