From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager] report: add replication configuration
Date: Thu, 23 Oct 2025 10:36:36 +0200 [thread overview]
Message-ID: <20251023083637.122453-1-m.sandoval@proxmox.com> (raw)
This was added right after jobs, in a sense, they are a kind of job.
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
Replication related problems are already hard to debug, this would prevent and
extra roundtrip in many support cases.
PVE/Report.pm | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/PVE/Report.pm b/PVE/Report.pm
index 34094a87..549a5d23 100644
--- a/PVE/Report.pm
+++ b/PVE/Report.pm
@@ -113,6 +113,12 @@ my $init_report_cmds = sub {
'cat /etc/pve/jobs.cfg',
],
},
+ replication => {
+ order => 67,
+ cmds => [
+ 'cat /etc/pve/replication.cfg',
+ ],
+ },
hardware => {
order => 70,
cmds => [
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-10-23 8:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251023083637.122453-1-m.sandoval@proxmox.com \
--to=m.sandoval@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