From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <d.csapak@proxmox.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 3DC75646C3 for <pve-devel@lists.proxmox.com>; Fri, 28 Jan 2022 10:25:05 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3B5372C93D for <pve-devel@lists.proxmox.com>; Fri, 28 Jan 2022 10:25:05 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id C5DE52C934 for <pve-devel@lists.proxmox.com>; Fri, 28 Jan 2022 10:25:04 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 9DAAA46D20 for <pve-devel@lists.proxmox.com>; Fri, 28 Jan 2022 10:25:04 +0100 (CET) From: Dominik Csapak <d.csapak@proxmox.com> To: pve-devel@lists.proxmox.com Date: Fri, 28 Jan 2022 10:25:04 +0100 Message-Id: <20220128092504.2076825-1-d.csapak@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.164 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [pve-storage.target] Subject: [pve-devel] [PATCH manager] order pvescheduler after pve-guests 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, 28 Jan 2022 09:25:05 -0000 that way a running backup cannot prevent pve-guests from starting a a vm which was marked with 'onboot' Signed-off-by: Dominik Csapak <d.csapak@proxmox.com> --- services/pvescheduler.service | 1 + 1 file changed, 1 insertion(+) diff --git a/services/pvescheduler.service b/services/pvescheduler.service index e6f10832..6d0d0985 100644 --- a/services/pvescheduler.service +++ b/services/pvescheduler.service @@ -3,6 +3,7 @@ Description=Proxmox VE scheduler ConditionPathExists=/usr/bin/pvescheduler Wants=pve-cluster.service After=pve-cluster.service +After=pve-guests.service After=pve-storage.target [Service] -- 2.30.2