Qemu binary not/inccorectly set when adding appliance from template (v2.2.31)

[DanielBarie]

While Qemu binary is (correctly) set when adding a template:

It will be overwritten when the appliance has been added:

Thus, the appliance will not work because Qemu fails (with error code 0). Symptom: Appliance will turn green and revert to red shortly thereafter.

Console output:

POST http://172.16.10.249:80/v2/projects/d266bb16-71e6-4e43-a54e-785fc7350e04/nodes/start
Event received: node.updated - command_line: /bin/qemu-system-i386 -name MikroTikCHR6.49.1-1 -m 128M -smp cpus=1,sockets=1 -enable-kvm -boot order=c -drive file=/opt/gns3/projects/d266bb16-71e6-4e43-a54e-785fc7350e04/project-files/qemu/fb537c04-8782-4a21-b685-c73668137642/hda_disk.qcow2,if=virtio,index=0,media=disk,id=drive0 -uuid fb537c04-8782-4a21-b685-c73668137642 -serial telnet:127.0.0.1:5001,server,nowait -monitor tcp:127.0.0.1:40893,server,nowait -net none -device virtio-net-pci,mac=0c:53:7c:04:00:00,netdev=gns3-0 -netdev socket,id=gns3-0,udp=127.0.0.1:20001,localaddr=127.0.0.1:20000 -device virtio-net-pci,mac=0c:53:7c:04:00:01,netdev=gns3-1 -netdev socket,id=gns3-1,udp=127.0.0.1:20003,localaddr=127.0.0.1:20002 -display none, compute_id: local, console: 5000, console_host: 0.0.0.0, console_type: telnet, first_port_name: , height: 45, label: MikroTikCHR6.49.1-1, name: MikroTikCHR6.49.1-1, node_directory: /opt/gns3/projects/d266bb16-71e6-4e43-a54e-785fc7350e04/project-files/qemu/fb537c04-8782-4a21-b685-c73668137642, node_id: fb537c04-8782-4a21-b685-c73668137642, node_type: qemu, port_name_format: ether{port1}, port_segment_size: 0, ports: adapter_number: 0, link_type: ethernet, name: ether1, port_number: 0, short_name: ether1, adapter_number: 1, link_type: ethernet, name: ether2, port_number: 0, short_name: ether2, project_id: d266bb16-71e6-4e43-a54e-785fc7350e04, status: started, symbol: :/symbols/classic/router.svg, symbol_url: undefined, width: 66, x: -481, y: 111, z: 1.
Event received: node.updated - command_line: /bin/qemu-system-i386 -name MikroTikCHR6.49.1-1 -m 128M -smp cpus=1,sockets=1 -enable-kvm -boot order=c -drive file=/opt/gns3/projects/d266bb16-71e6-4e43-a54e-785fc7350e04/project-files/qemu/fb537c04-8782-4a21-b685-c73668137642/hda_disk.qcow2,if=virtio,index=0,media=disk,id=drive0 -uuid fb537c04-8782-4a21-b685-c73668137642 -serial telnet:127.0.0.1:5001,server,nowait -monitor tcp:127.0.0.1:40893,server,nowait -net none -device virtio-net-pci,mac=0c:53:7c:04:00:00,netdev=gns3-0 -netdev socket,id=gns3-0,udp=127.0.0.1:20001,localaddr=127.0.0.1:20000 -device virtio-net-pci,mac=0c:53:7c:04:00:01,netdev=gns3-1 -netdev socket,id=gns3-1,udp=127.0.0.1:20003,localaddr=127.0.0.1:20002 -display none, compute_id: local, console: 5000, console_host: 0.0.0.0, console_type: telnet, first_port_name: , height: 45, label: MikroTikCHR6.49.1-1, name: MikroTikCHR6.49.1-1, node_directory: /opt/gns3/projects/d266bb16-71e6-4e43-a54e-785fc7350e04/project-files/qemu/fb537c04-8782-4a21-b685-c73668137642, node_id: fb537c04-8782-4a21-b685-c73668137642, node_type: qemu, port_name_format: ether{port1}, port_segment_size: 0, ports: adapter_number: 0, link_type: ethernet, name: ether1, port_number: 0, short_name: ether1, adapter_number: 1, link_type: ethernet, name: ether2, port_number: 0, short_name: ether2, project_id: d266bb16-71e6-4e43-a54e-785fc7350e04, status: stopped, symbol: :/symbols/classic/router.svg, symbol_url: undefined, width: 66, x: -481, y: 111, z: 1. 

[piotrpekala7]

user is able to set correct qemu path when adding new template & in configurator

[piotrpekala7]

if binary is visible in results of following query: /computes/local/qemu/binaries then it should also be properly matched when opening configurator

[piotrpekala7]

list of qemu binaries is taken from server endpoint https://github.com/GNS3/gns3-web-ui/blob/master/src/app/components/project-map/node-editors/configurator/qemu/configurator-qemu.component.ts#L66, we don't change anything in received data, you can query server on your own and verify the returned list