Storage replication constantly failing

timota

Renowned Member
Oct 14, 2011
9
2
68
Hi,

after upgrade all nodes to the latest
pve-manager/5.1-51/96be5354 (running kernel: 4.13.16-2-pve)

Storage replication constantly failing. HA disabled. It sometimes works, sometimes not.
Logs below:
()
2018-04-30 12:50:00 102-0: start replication job
2018-04-30 12:50:00 102-0: guest => VM 102, running => 16077
2018-04-30 12:50:00 102-0: volumes => zfs.vm-disks:vm-102-disk-1
2018-04-30 12:50:02 102-0: create snapshot '__replicate_102-0_1525081800__' on zfs.vm-disks:vm-102-disk-1
2018-04-30 12:50:02 102-0: incremental sync 'zfs.vm-disks:vm-102-disk-1' (__replicate_102-0_1525081200__ => __replicate_102-0_1525081800__)
2018-04-30 12:50:03 102-0: delete previous replication snapshot '__replicate_102-0_1525081800__' on zfs.vm-disks:vm-102-disk-1
2018-04-30 12:50:03 102-0: end replication job with error: import failed: exit code 29

()
2018-04-30 13:13:00 102-0: start replication job
2018-04-30 13:13:00 102-0: guest => VM 102, running => 16077
2018-04-30 13:13:00 102-0: volumes => zfs.vm-disks:vm-102-disk-1
2018-04-30 13:13:01 102-0: create snapshot '__replicate_102-0_1525083180__' on zfs.vm-disks:vm-102-disk-1
2018-04-30 13:13:01 102-0: incremental sync 'zfs.vm-disks:vm-102-disk-1' (__replicate_102-0_1525082700__ => __replicate_102-0_1525083180__)
2018-04-30 13:13:03 102-0: delete previous replication snapshot '__replicate_102-0_1525083180__' on zfs.vm-disks:vm-102-disk-1
2018-04-30 13:13:03 102-0: end replication job with error: import failed: exit code 29

can someone advise what the issue can be.
 
Fixes for this are already on pvetest repository, and we will move them to stable repositories this week.
 
Is this fix already in stable because I'm still having this issue?
Since we would like to go into production with our cluster soon, it would be very helpful to know what is going on with this issue.
Could any proxmox staff member please confirm?
 
Fixes for this are already on pvetest repository, and we will move them to stable repositories this week.
If the fix is in the stable respectively enterprise repository, I couldn't find anything about this in the changelogs.
 
Yes, it is fixed.
pvesr is working if you have any problems please open a new thread and provided information about your problem.