From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Stefan Hanreich <s.hanreich@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-manager 1/1] pve8to9: check for legacy ipam db or mac cache files
Date: Fri, 1 Aug 2025 16:27:26 +0200 [thread overview]
Message-ID: <175405843764.2400340.3708674077051882138.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250801121029.201766-3-s.hanreich@proxmox.com>
On Fri, 01 Aug 2025 14:10:26 +0200, Stefan Hanreich wrote:
> Check if there are any not-yet-migrated ipam / mac cache files in
> pmxcfs. Those should have been migrated over in the pve-network
> postinst, but if something went wrong during this process we can
> explicitly notify users here again to avoid any unpleasant suprises
> after the upgrade.
>
> If all nodes are on PVE 9, it is safe to delete the legacy files,
> print a notice informing the users.
>
> [...]
Applied, thanks!
[1/1] pve8to9: check for legacy ipam db or mac cache files
commit: 17488fc091be297e2732a66be387b839a333e36b
_______________________________________________
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-08-01 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-01 12:10 [pve-devel] [PATCH cluster/manager/network 0/3] remove legacy ipam and mac db from observed files Stefan Hanreich
2025-08-01 12:10 ` [pve-devel] [PATCH pve-cluster 1/1] pmxcfs: remove legacy ipam db and mac cache files Stefan Hanreich
2025-08-01 12:52 ` Thomas Lamprecht
2025-08-01 12:10 ` [pve-devel] [PATCH pve-manager 1/1] pve8to9: check for legacy ipam db or " Stefan Hanreich
2025-08-01 14:27 ` Thomas Lamprecht [this message]
2025-08-01 12:10 ` [pve-devel] [PATCH pve-network 1/1] ipam: remove fallback code for ipam.db and mac cache Stefan Hanreich
2025-08-01 13:19 ` 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=175405843764.2400340.3708674077051882138.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.