From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <aderumier@odiso.com> 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 C956961249 for <pve-devel@pve.proxmox.com>; Fri, 4 Sep 2020 17:46:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BB4C522893 for <pve-devel@pve.proxmox.com>; Fri, 4 Sep 2020 17:46:53 +0200 (CEST) Received: from mailpro.odiso.net (mailpro.odiso.net [89.248.211.110]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id D76E822884 for <pve-devel@pve.proxmox.com>; Fri, 4 Sep 2020 17:46:51 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id D050F1842E30 for <pve-devel@pve.proxmox.com>; Fri, 4 Sep 2020 17:46:44 +0200 (CEST) Received: from mailpro.odiso.net ([127.0.0.1]) by localhost (mailpro.odiso.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id oTLkFLN_oktr for <pve-devel@pve.proxmox.com>; Fri, 4 Sep 2020 17:46:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id B23521842E2F for <pve-devel@pve.proxmox.com>; Fri, 4 Sep 2020 17:46:44 +0200 (CEST) X-Virus-Scanned: amavisd-new at mailpro.odiso.com Received: from mailpro.odiso.net ([127.0.0.1]) by localhost (mailpro.odiso.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 4GyFqDyl1TRE for <pve-devel@pve.proxmox.com>; Fri, 4 Sep 2020 17:46:44 +0200 (CEST) Received: from mailpro.odiso.net (mailpro.odiso.net [10.1.31.111]) by mailpro.odiso.net (Postfix) with ESMTP id 9CA091842E2D for <pve-devel@pve.proxmox.com>; Fri, 4 Sep 2020 17:46:44 +0200 (CEST) Date: Fri, 4 Sep 2020 17:46:44 +0200 (CEST) From: Alexandre DERUMIER <aderumier@odiso.com> To: pve-devel <pve-devel@pve.proxmox.com> Message-ID: <1746471147.372129.1599234404405.JavaMail.zimbra@odiso.com> In-Reply-To: <216436814.339545.1599142316781.JavaMail.zimbra@odiso.com> References: <216436814.339545.1599142316781.JavaMail.zimbra@odiso.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 8.8.12_GA_3866 (ZimbraWebClient - GC83 (Linux)/8.8.12_GA_3844) Thread-Topic: corosync bug: cluster break after 1 node clean shutdown Thread-Index: BDCUNDa2t04O78rYKqmARZV+ZCSDiv7ycJ1h X-SPAM-LEVEL: Spam detection results: 0 AWL 0.035 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] corosync bug: cluster break after 1 node clean shutdown X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 04 Sep 2020 15:46:53 -0000 What I'm not sure, is what was the running libknet version. package was upgraded everywhere to 1.16, but I have notice that corosync process is not restarted when libknet is upgraded. so it's quite possible that corosync was still running 1.13 libknet. (I need to find a way to find last corosync or node restart). I think we should force corosync restart on libknet upgrade. (or maybe bump corosync package version at the same time)