From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 86E4E6003A for ; Wed, 2 Dec 2020 09:14:23 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 7BF9918493 for ; Wed, 2 Dec 2020 09:14:23 +0100 (CET) Received: from smtp12.dentaku.gol.com (smtp12.dentaku.gol.com [203.216.5.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 1856718485 for ; Wed, 2 Dec 2020 09:14:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gol.com; s=mail; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Subject:To:From:Date; bh=asRscJx8sZyVwAM1HIKXEtZzs1xpvDyq2FHHtNmoyIE=; b=FptX6tArKnWDxZxzY2OZ4DLuw2mx4lK0fG6D4NqX/NQJ+VuUnEHaaC9+K8jA4BqBGM2dT7bdIu8wAoQGDlohMlDNvPy+o4QVIHjFhQMB/G1EKLDc5QHgm07z9BZUmoDcg+8+6fa50qiHaEdT+qPwV1Lkeuy0cCY8MOssJAg9n1GUEmVYMmqV4VAq8LKBDTzVDPunITjTLuWU4c3lBbXe4c7CB9acQZ8+aik3XRJrr2MOFh0DnGOgzKMlWM7K1aZG4l1d7ibfk5vytt1Kb7OVMcCwxRlWaIcTHfjxx15fvs42C54kyK5l1OFFWU7Ei90zwUcMDB8Ku1nl4E8ANRkvXQ==; Received: from batzmaru.gol.ad.jp ([203.216.0.80]) by smtp12.dentaku.gol.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Dentaku) (envelope-from ) id 1kkNE8-000481-2X for pve-user@lists.proxmox.com; Wed, 02 Dec 2020 17:11:04 +0900 Date: Wed, 2 Dec 2020 17:11:02 +0900 From: Christian Balzer To: Proxmox VE user list Message-ID: <20201202171102.03c7f2e2@batzmaru.gol.ad.jp> Organization: Rakuten Communications X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL (outbound) X-GOL-Outbound-Spam-Score: -1.9 X-Abuse-Complaints: abuse@gol.com X-SPAM-LEVEL: Spam detection results: 0 DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust RCVD_IN_MSPIKE_H3 0.001 Good reputation (+3) RCVD_IN_MSPIKE_WL 0.001 Mailspike good senders SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [gol.com] Subject: [PVE-User] Live VM migration 6.3 to 6.2 fails X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Dec 2020 08:14:23 -0000 Hello, yes I know that migrating back to an older version is not guaranteed but I'm rather confused as to why this happens. Firstly this, more details below: --- 2020-12-02 16:34:08 start migrate command to tcp:10.0.0.11:60000 2020-12-02 16:34:09 migration status error: failed 2020-12-02 16:34:09 ERROR: online migrate failure - aborting 2020-12-02 16:34:09 aborting phase 2 - cleanup resources 2020-12-02 16:34:09 migrate_cancel 2020-12-02 16:34:11 ERROR: migration finished with problems (duration 00:00:08) TASK ERROR: migration problems --- That's all I get, where would one find the exact issue? Now for the details, in the previous minor upgrade we saw a similar issue, but that only affected VMs which had been created on an upgraded node, old ones were fine to move in both ways. OK, that was because of new features int he VM definition not present on the old version, understandable. With this one on a (more frequently updated) test cluster 6.3 to 6.2 migrations also works, the test cluster old nodes are at pve-manager (6.2-12), the one with issues are pve-manager (6.2-6). I however see nothing in the changelogs which would explain this difference. In general being able to live migrate back to a node with the previous version is a very desirable situation, since if there are issues/bugs (on the VM level) with the new version there no longer is an impact free way of reverting if this functionality is not present. Regards, Christian -- Christian Balzer Network/Systems Engineer chibi@gol.com Rakuten Mobile Inc.