From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Hannes Laimer <h.laimer@proxmox.com>
Subject: applied: [PATCH pve-network] config: release the addresses of a NIC removed from a running container
Date: Sat, 14 Nov 2026 22:33:00 +0100 [thread overview]
Message-ID: <179469198018.2480055.16504677006494155269.b4-ty@b4> (raw)
In-Reply-To: <20261112104059.2377096-1-h.laimer@proxmox.com>
On Thu, 12 Nov 2026 11:40:59 +0100, Hannes Laimer wrote:
> Without `$class->..` the passed options ended up as the first
> argument, and the `undef` check on the second argument, `!$data`,
> ended up returning an empty hash. So the NIC's addresses were never
> released in the IPAM, and the DHCP client of a host-managed NIC was
> not stopped. Destroying the container did not release them either,
> since the NIC is gone from the config by then.
>
> [...]
Applied, thanks!
[1/1] config: release the addresses of a NIC removed from a running container
commit: b91881f0cc5bcf533dfb153c4ffa0f282101d1a2
prev parent reply other threads:[~2026-11-14 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 10:40 [PATCH pve-network] config: release the addresses of a NIC removed from a running container Hannes Laimer
2026-11-12 10:46 ` Hannes Laimer
2026-11-14 21:33 ` 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=179469198018.2480055.16504677006494155269.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@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