From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-manager 1/1] pvestatd: prevent warnings for non-existing network devices
Date: Wed, 30 Jul 2025 14:51:29 +0200 [thread overview]
Message-ID: <175387988824.3542403.7324409681373265744.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250730124451.184806-1-s.hanreich@proxmox.com>
On Wed, 30 Jul 2025 14:44:48 +0200, Stefan Hanreich wrote:
> pvestatd runs the update loop for every network device present on the
> host. This includes many dynamically created / removed network
> interfaces (tap devices, veths, fw bridges). This triggers a warning
> if the network device isn't yet in the cached version of the ip link
> output:
>
> pvestatd[1011]: Use of uninitialized value in string eq at /usr/share/perl5/PVE/Network.pm line 998.
>
> [...]
Applied, thanks!
[1/1] pvestatd: prevent warnings for non-existing network devices
commit: 09f7410dd3067d8717b17c5e620bb45309968271
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-30 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 12:44 Stefan Hanreich
2025-07-30 12:51 ` Thomas Lamprecht [this message]
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=175387988824.3542403.7324409681373265744.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.hanreich@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.