Le 28/09/22 à 14:50, Fabian Grünbichler a écrit : > which wraps the remote_migrate_vm API endpoint, but does the > precondition checks that can be done up front itself. > > this now just leaves the FP retrieval and target node name lookup to the > sync part of the API endpoint, which should be do-able in <30s .. > > an example invocation: > > $ qm remote-migrate 1234 4321 > 'host=123.123.123.123,apitoken=pveapitoken=user@pve!incoming=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee,fingerprint=aa:bb:cc:dd:ee:ff:aa:bb:cc:dd:ee:ff:aa:bb:cc:dd:ee:ff:aa:bb:cc:dd:ee:ff:aa:bb:cc:dd:ee:ff:aa:bb' > --target-bridge vmbr0 --target-storage zfs-a:rbd-b,nfs-c:dir-d,zfs-e --online
"apitoken=pveapitoken=user@pve!incoming should be "apitoken=PVEAPIToken=user@pve!incoming" as PVEAPIToken is case sensitive _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
