From: Philipp Hufnagl <p.hufnagl@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH storage v3 4/4] pbs: fix #5008: Check if datastore and namespace is valid on add- and update hooks
Date: Thu, 16 Nov 2023 11:35:47 +0100 [thread overview]
Message-ID: <20231116103547.47205-5-p.hufnagl@proxmox.com> (raw)
In-Reply-To: <20231116103547.47205-1-p.hufnagl@proxmox.com>
This adds a check if the datastore and the namespace is valid when a
user attempts to add a new PBS datastore.
Since the namespace only can be checked after the datastore is
validated, the datastore will be checked as well, regardless that it
will be done later in the superclass anyway.
The functionallity to check namespaces is added with this commit. For
checking the datastore, existing code that has previously been
refactored will be reused
Signed-off-by: Philipp Hufnagl <p.hufnagl@proxmox.com>
---
src/PVE/Storage/PBSPlugin.pm | 41 ++++++++++++++++++++++++++++++++++++
1 file changed, 41 insertions(+)
diff --git a/src/PVE/Storage/PBSPlugin.pm b/src/PVE/Storage/PBSPlugin.pm
index 3e0e155..0797cec 100644
--- a/src/PVE/Storage/PBSPlugin.pm
+++ b/src/PVE/Storage/PBSPlugin.pm
@@ -566,6 +566,11 @@ sub on_add_hook {
pbs_delete_master_pubkey($scfg, $storeid);
}
+ my $password = pbs_get_password($scfg, $storeid);
+ my $conn = pbs_api_connect($scfg, $password);
+ check_datastore_exists($class, $storeid, $scfg, $password, $conn);
+ check_namespace_exists($class, $storeid, $scfg, $password, $conn);
+
return $res;
}
@@ -614,6 +619,11 @@ sub on_update_hook {
}
}
+ my $password = pbs_get_password($scfg, $storeid);
+ my $conn = pbs_api_connect($scfg, $password);
+ check_datastore_exists($class, $storeid, $scfg, $password, $conn);
+ check_namespace_exists($class, $storeid, $scfg, $password, $conn);
+
return $res;
}
@@ -817,6 +827,18 @@ sub scan_datastores {
return $response;
}
+
+sub scan_namespaces {
+ my ($scfg, $datastore, $password, $conn) = @_;
+
+ $conn = pbs_api_connect($scfg, $password) if !defined($conn);
+
+ my $namespaces = eval { $conn->get("/api2/json/admin/datastore/$datastore/namespace", {}); };
+ die "error fetching namespaces - $@" if $@;
+
+ return $namespaces;
+}
+
sub check_datastore_exists {
my ($class, $storeid, $scfg, $password, $conn) = @_;
@@ -833,6 +855,25 @@ sub check_datastore_exists {
die "$storeid: Cannot find datastore '$datastore', check permissions and existence!\n";
}
+sub check_namespace_exists {
+ my ($class, $storeid, $scfg, $password, $conn) = @_;
+
+ my $namespace = $scfg->{namespace};
+ return 1 if !defined($namespace);
+ my $datastore = $scfg->{datastore};
+
+ my $namespaces = eval { scan_namespaces($scfg, $datastore, $password, $conn) };
+ die "$storeid: $@" if $@;
+
+ for my $ns (@$namespaces) {
+ if ($ns->{ns} eq $namespace) {
+ return 1;
+ }
+ }
+
+ die "$storeid: Cannot find namespace '$namespace', check permissions and existence!\n";
+}
+
sub activate_storage {
my ($class, $storeid, $scfg, $cache) = @_;
--
2.39.2
next prev parent reply other threads:[~2023-11-16 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 10:35 [pve-devel] [PATCH storage v3 0/4] pbs: fix #5008: Prevent adding pbs storage with invalid namespace Philipp Hufnagl
2023-11-16 10:35 ` [pve-devel] [PATCH storage v3 1/4] pbs: Move pbs_api_connect earlyer in the code Philipp Hufnagl
2023-11-16 10:35 ` [pve-devel] [PATCH storage v3 2/4] pbs: Make it possible to reuse PBS connection for datastore API call Philipp Hufnagl
2023-11-16 10:35 ` [pve-devel] [PATCH storage v3 3/4] pbs: Extraxt check_datastore_exists from activate_storage Philipp Hufnagl
2023-11-16 10:35 ` Philipp Hufnagl [this message]
2023-11-21 12:16 ` [pve-devel] [PATCH storage v3 0/4] pbs: fix #5008: Prevent adding pbs storage with invalid namespace Christian Ebner
2023-11-21 13:12 ` Philipp Hufnagl
2023-11-21 13:40 ` Christian Ebner
2023-11-21 14:13 ` Philipp Hufnagl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231116103547.47205-5-p.hufnagl@proxmox.com \
--to=p.hufnagl@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox