Project

General

Profile

Bug #46964

Fix sending multiple vm.clone calls when cloning a VM

Added by William Grzybowski about 2 years ago. Updated about 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
Damian Szidiropulosz
Category:
GUI (new)
Target version:
11.2-RC1
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

It seems cloning a single VM will send a websocket call to clone "N" VMs. N being the number of existing VMs.

vmclone.png (58.9 KB) vmclone.png William Grzybowski, 09/18/2018 06:59 AM
Screenshot-2018-9-26 FreeNAS - 10 231 4 231(6).png (232 KB) Screenshot-2018-9-26 FreeNAS - 10 231 4 231(6).png Jeff Ervin, 09/26/2018 12:31 PM
30640
32045

Related issues

Related to FreeNAS - Bug #43866: Use unique name for cloned zvolDone
Has duplicate FreeNAS - Bug #46986: UI does not unsubscribe vm.status callsClosed

History

#1 Updated by William Grzybowski about 2 years ago

  • Related to Bug #43866: Use unique name for cloned zvol added

#2 Updated by Dru Lavigne about 2 years ago

  • Target version changed from Backlog to 11.2-RC1

#3 Updated by Vaibhav Chauhan about 2 years ago

  • Assignee changed from Vaibhav Chauhan to Damian Szidiropulosz

I have tried to fix this issue but I am not able to point why there are multiple vm.clone calls however I can point out that when it happens.

the number of times vm.clone call on a single click is dependent on how many vm were tried to be cloned on a single vm, without navigating away from the page. seems like VmClone event is fired due to the fact that dispatch table grows.

#4 Updated by Vaibhav Chauhan about 2 years ago

  • Related to Bug #46986: UI does not unsubscribe vm.status calls added

#5 Updated by Damian Szidiropulosz about 2 years ago

  • Status changed from Unscreened to Ready for Testing

PR 1253 fixes this

#6 Updated by Dru Lavigne about 2 years ago

  • Related to deleted (Bug #46986: UI does not unsubscribe vm.status calls)

#7 Updated by Dru Lavigne about 2 years ago

  • Has duplicate Bug #46986: UI does not unsubscribe vm.status calls added

#8 Updated by Dru Lavigne about 2 years ago

  • Status changed from Ready for Testing to In Progress

#9 Updated by Damian Szidiropulosz about 2 years ago

  • Status changed from In Progress to Ready for Testing

#10 Updated by Dru Lavigne about 2 years ago

  • Subject changed from Cloning a single VM may send multiple vm.clone calls to Fix sending multiple vm.clone calls when cloning a VM
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#12 Updated by Jeff Ervin about 2 years ago

32045

Test Passed FreeNAS-11.2-MASTER-201809260853

Each time I cloned a VM, only one clone was created at a time.

#13 Updated by Dru Lavigne about 2 years ago

  • Status changed from Passed Testing to Done

Also available in: Atom PDF