From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Cc: "pve-devel" <pve-devel-bounces@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container/qemu-server v4 0/2] Fix RRD PNG Graph creation
Date: Wed, 03 Sep 2025 14:30:36 +0200 [thread overview]
Message-ID: <DCJ608UR2V2L.AP3HNBE3E8G2@proxmox.com> (raw)
In-Reply-To: <20250828125810.3642601-1-a.lauterer@proxmox.com>
Tested this by manually calling both API endpoints. With the patches
applied, the returned filename now contains the data sources provided in
the params and also returns data for the image again.
Tested-by: Michael Köppl <m.koeppl@proxmox.com>
On Thu Aug 28, 2025 at 2:58 PM CEST, Aaron Lauterer wrote:
> This series fixes the RRD graph generation to PNGs for CTs and VMs.
>
> qemu-server:
>
> Aaron Lauterer (1):
> api: rrd: add missing ds parameter for png graph
>
> src/PVE/API2/Qemu.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
> container:
>
> Aaron Lauterer (1):
> api: rrd: add missing ds parameter for png graph
>
> src/PVE/API2/LXC.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
> Summary over all repositories:
> 2 files changed, 2 insertions(+), 2 deletions(-)
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-09-03 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 12:58 Aaron Lauterer
2025-08-28 12:58 ` [pve-devel] [PATCH qemu-server v4 1/1] api: rrd: add missing ds parameter for png graph Aaron Lauterer
2025-08-28 12:58 ` [pve-devel] [PATCH container " Aaron Lauterer
2025-09-03 11:37 ` [pve-devel] [PATCH container/qemu-server v4 0/2] Fix RRD PNG Graph creation Aaron Lauterer
2025-09-03 12:30 ` Michael Köppl [this message]
2025-09-03 16:38 ` [pve-devel] applied-series: " Thomas Lamprecht
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=DCJ608UR2V2L.AP3HNBE3E8G2@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=pve-devel-bounces@lists.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