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 86CFE6A203 for ; Thu, 25 Feb 2021 22:23:40 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 850478FA9 for ; Thu, 25 Feb 2021 22:23:40 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [212.186.127.180]) (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 firstgate.proxmox.com (Proxmox) with ESMTPS id 0236C8F89 for ; Thu, 25 Feb 2021 22:23:39 +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 BEBFB4633D for ; Thu, 25 Feb 2021 22:23:38 +0100 (CET) From: Stoiko Ivanov To: pve-devel@lists.proxmox.com Date: Thu, 25 Feb 2021 22:23:03 +0100 Message-Id: <20210225212305.17954-1-s.ivanov@proxmox.com> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.063 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_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH storage/manager] fix cosmetic api issue with zpool status output X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Feb 2021 21:23:40 -0000 As reported in a thread in our community forum: https://forum.proxmox.com/threads/zfs-storage-detail-produces-result-verification-failed-400-error.84839/#post-372939 the 'scan' property of the API call (a.k.a. the scan-line in zpool status output) is not present, if a pool has never been scrubbed. the patch for pve-storage fixes the issue of failed result verification. the patch for pve-manager is optional, but I thought that a pool, that never has been scrubbed is worth an informational notice. pve-storage: Stoiko Ivanov (1): disks: zfs: scan is only returned optionally PVE/API2/Disks/ZFS.pm | 1 + 1 file changed, 1 insertion(+) pve-manager: Stoiko Ivanov (1): ui: zpool status detail: add default for scrub information www/manager6/node/ZFS.js | 1 + 1 file changed, 1 insertion(+) -- 2.20.1