From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] 8 to 9 checks: warn if old udev-mac-pinning still present
Date: Mon, 4 Aug 2025 21:31:18 +0200 [thread overview]
Message-ID: <175433587244.954244.13973227027307058959.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250804183856.773378-1-s.ivanov@proxmox.com>
On Mon, 04 Aug 2025 20:38:56 +0200, Stoiko Ivanov wrote:
> We observed this in a host which has been updated through many major
> versions (at least since PVE 4). The 70-persistent-net.rules was
> used keeping the NICs with 'ethX' names. With the first reboot
> into trixie the NICs got their predictable names, and networking was
> broken (because the 'ethX' names are not present as altname the
> support for this does not help in this case)
>
> [...]
Applied, thanks!
[1/1] 8 to 9 checks: warn if old udev-mac-pinning still present
commit: 73f1b8b46f37cf4450849f77226c068b97c57248
_______________________________________________
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-08-04 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 18:38 [pve-devel] " Stoiko Ivanov
2025-08-04 19:31 ` 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=175433587244.954244.13973227027307058959.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@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