Proxmox 4.1 Cluster error to restore VM in ZFS over ISCSI

Hello, first excuse me but I have a low level of English.
I have a problem with Proxmox Cluster 4.1 and ZFS over ISCSI storage with Nexenta.
First, I put Proxmox version:

# pveversion -v
proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4)
pve-kernel-4.2.6-1-pve: 4.2.6-26
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-29
qemu-server: 4.0-41
pve-firmware: 1.1-7
libpve-common-perl: 4.0-41
libpve-access-control: 4.0-10
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-17
pve-container: 1.0-32
pve-firewall: 2.0-14
pve-ha-manager: 1.0-14
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6~jessie

The case is as follows:
With Proxmox node and storage with ZFS over ISCSI, when configuring functioning properly.
I follow the procedure of creating the SSH key as described in the documentation: https://pve.proxmox.com/wiki/Storage:_ZFS_over_iSCSI

The problem comes when I perform the same operation on a cluster of Proxmox because the /etc/pve directory is shared between nodes, and to create the SSH key one is replicated immediately in the other.
I think this makes the problem of when to restore the virtual machine. The error message is as follows:

restore vma archive: lzop -d -c /var/lib/vz/dump/vzdump-qemu-101-2016_02_25-13_45_22.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp27290.fifo - /var/tmp/vzdumptmp27290
CFG: size: 370 name: qemu-server.conf
DEV: dev_id=1 size: 5368709120 devname: drive-virtio0
CTIME: Thu Feb 25 13:45:26 2016
new volume ID is 'nex01a11:vm-104-disk-1'
map 'drive-virtio0' to 'iscsi://200.200.20.11/iqn.2010-08.org.illumos:02:754c24cc-735a-4a20-f97b-9b32235b5016/5' (write zeros = 1)

** (process:27293): ERROR **: can't open file iscsi://200.200.20.11/iqn.2010-08.org.illumos:02:754c24cc-735a-4a20-f97b-9b32235b5016/5 - Unknown driver 'illumos:02:754c24cc-735a-4a20-f97b-9b32235b5016/5'
/bin/bash: line 1: 27292 Broken pipe lzop -d -c /var/lib/vz/dump/vzdump-qemu-101-2016_02_25-13_45_22.vma.lzo
27293 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp27290.fifo - /var/tmp/vzdumptmp27290
temporary volume 'nex01a11:vm-104-disk-1' sucessfuly removed
TASK ERROR: command 'lzop -d -c /var/lib/vz/dump/vzdump-qemu-101-2016_02_25-13_45_22.vma.lzo|vma extract -v -r /var/tmp/vzdumptmp27290.fifo - /var/tmp/vzdumptmp27290' failed: exit code 133

Any ideas??

Thank you so much
 
** (process:27293): ERROR **: can't open file iscsi://200.200.20.11/iqn.2010-08.org.illumos:02:754c24cc-735a-4a20-f97b-9b32235b5016/5 - Unknown driver 'illumos:02:754c24cc-735a-4a20-f97b-9b32235b5016/5'
Looks like a regration in Proxmox 4.1. Given target is 'iqn.2010-08.org.illumos:02:754c24cc-735a-4a20-f97b-9b32235b5016' I am a bit confused about this error message "Unknown driver 'illumos:02:754c24cc-735a-4a20-f97b-9b32235b5016/5'"
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!