[SOLVED] Can't delete not working replication job (pvesr)

[fireon]

Hello,

in pvesr there was the bug that the job is not working with IPV6. That is fixed now in the changlogs. So i would like to delete the job. This has not worked for me. I've delet it for two weeks the first time, then once again and agian... There is only the message:

Replication job removal is a background task and will take some time.

But nothing is happenings. I also can't delete the VM:

There is a replication job '101-0' for guest '101' - Please remove that first.

proxmox-ve: 5.0-19 (running kernel: 4.10.17-2-pve)
pve-manager: 5.0-30 (running version: 5.0-30/5ab26bc)
pve-kernel-4.10.17-2-pve: 4.10.17-19
pve-kernel-4.10.15-1-pve: 4.10.15-15
libpve-http-server-perl: 2.0-5
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-3
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.11.2-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90

So how i can delete the job?

 

[pabernethy]

Do you know if replication was already started? If it wasn't it should be safe to force deletion. If it was you need cleanup after forcing deletion.

 

[fireon]

Thank you forcing have worked. But the replication did not work. Same error as before the fix:

2017-08-11 15:59:00 108-0: start replication job
2017-08-11 15:59:00 108-0: guest => VM 108, running => 21033
2017-08-11 15:59:00 108-0: volumes => HDD-vmdata-KVM:vm-108-disk-1,HDD-vmdata-KVM:vm-108-disk-2
2017-08-11 15:59:00 108-0: (remote_prepare_local_job) Host key verification failed.
2017-08-11 15:59:00 108-0: (remote_prepare_local_job)
2017-08-11 15:59:00 108-0: end replication job with error: command '/usr/bin/ssh -o 'BatchMode=yes' -o 'HostKeyAlias=virtu01' root@2001:470:1e0c:569:ea3:7aff:fe35:e7a0 -- pvesr prepare-local-job 108-0 HDD-vmdata-KVM:vm-108-disk-1 HDD-vmdata-KVM:vm-108-disk-2 --last_sync 0' failed: exit code 255

When i do an ssh manualy i can login normaly.

 

[fireon]

It does work now. Problem was that the hostname only must also able to use with. This is strange. IP's are working IPV6 and IPV4, also the FQDN. So i have done an "ssh myhostname" too. After i acceppt the key it works fine.