[PATCH v2 manager 09/13] pvestatd: apply the cluster-wide multipath config on each node

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

Write out the cluster-wide multipath.cfg on each node once per status
loop: build the local multipathd drop-ins and reload multipathd when
they change. The work is a cheap no-op unless multipath is in use, and
the logic is kept out of pvestatd itself, so this is just a thin
trigger.

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

Changes in v2:
 - broadcast whether this node could apply the config
 - use PVE::Multipath explicitly instead of relying on the generator
   pulling it in

 PVE/Service/pvestatd.pm | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/PVE/Service/pvestatd.pm b/PVE/Service/pvestatd.pm
index 34f9da71f..1bdd1db65 100755
--- a/PVE/Service/pvestatd.pm
+++ b/PVE/Service/pvestatd.pm
@@ -20,6 +20,8 @@ use PVE::RS::SDN::Fabrics;
 use PVE::NodeConfig;
 use PVE::Cluster qw(cfs_read_file);
 use PVE::Storage;
+use PVE::Multipath;
+use PVE::Multipath::Generator;
 use PVE::QemuServer;
 use PVE::QemuServer::Monitor;
 use PVE::LXC;
@@ -848,6 +850,16 @@ sub update_status {
     $err = $@;
     syslog('err', "storage status update error: $err") if $err;
 
+    # apply the cluster-wide multipath config on this node; a cheap no-op unless multipath is in
+    # use, and the logic is kept out of pvestatd so this stays a thin trigger. Broadcast a failed
+    # apply so a node drifting from the configured state shows up in the datacenter view.
+    my $apply_err = eval { PVE::Multipath::Generator::sync(); };
+    $apply_err = $@ if $@;
+    syslog('err', "multipath config sync error: $apply_err") if $apply_err;
+    eval { PVE::Multipath::broadcast_apply_status($apply_err); };
+    $err = $@;
+    syslog('err', "multipath apply-status broadcast error: $err") if $err;
+
     eval { remove_stale_lxc_consoles(); };
     $err = $@;
     syslog('err', "lxc console cleanup error: $err") if $err;
-- 
2.47.3