pvecm: remove RPCEnvironment use clause

We do not use it anywhere and it triggers an cyclic build dependency
between pve-access-control and pve-cluster.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>

diff --git a/data/PVE/CLI/pvecm.pm b/data/PVE/CLI/pvecm.pm
index 1dce0491347c56c29f966c270d2ff7c1f3c64927..53fcb3a62d751aa9736180075254af5e91b3e125 100755 (executable)
--- a/data/PVE/CLI/pvecm.pm
+++ b/data/PVE/CLI/pvecm.pm
@@ -13,7 +13,6 @@ use PVE::Tools;
 use PVE::Cluster;
 use PVE::INotify;
 use PVE::JSONSchema;
-use PVE::RPCEnvironment;
 use PVE::CLIHandler;
 
 use base qw(PVE::CLIHandler);

diff --git a/data/PVE/pvecm b/data/PVE/pvecm
index 35f3ff778594e205129b0225e087b15056148bcf..87bc9f6963cad0908d5f1bba1df0a63da01dac3f 100755 (executable)
--- a/data/PVE/pvecm
+++ b/data/PVE/pvecm
@@ -17,4 +17,4 @@ my $prepare = sub {
     my $local_ip_address = PVE::Cluster::remote_node_ip($nodename);
 };
 
-PVE::CLI::pvecm->run_cli(undef, undef, $prepare);
+PVE::CLI::pvecm->run_cli_handler(prepare => $prepare, no_rpcenv => 1);