Your message dated Mon, 29 May 2023 10:37:05 +0200
with message-id <82ae307c-3d95-b335-9708-1b5944dad...@debian.org>
and subject line Re: Bug#1032268: release-notes: upgrading a xen VM to bookworm
will change network interface name to predictable scheme
has caused the Debian Bug report #1032268,
regarding release-notes: upgrading a xen VM to bookworm will change network
interface name to predictable scheme
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1032268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: normal
X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org
Dear Maintainer,
I upgraded a virtual machine (xen guest) from Debian 11 to bookworm,
everything went well, but lost network on reboot.
The interface had changed its name from eth0 to enX0, I guess due to
this change in systemd v 250:
* The predictable naming logic for network interfaces has been extended
to generate stable names from Xen netfront device information.
(ref: https://github.com/systemd/systemd/releases/tag/v250 )
I wonder if it would be nice to mention this in the systemd NEWS file or
in the release notes, so people do the needed changes in their machines
before rebooting the system after upgrade.
Sending this bug to release-notes but CC'ng pkg-systemd-maintainers@
Thanks!
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona
--- End Message ---
--- Begin Message ---
Hi Laura,
On 23-05-2023 18:48, Laura Arjona Reina wrote:
Proposed text handled here:
https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/175
I'm not sure about all the possible cases where this issue would need to be
handled (and probably there are different 'ways' like changing the name in all
the files where the interface is referenced, or disabling the predictable
naming scheme) so a generic text as you propose looks the best to me.
I just pushed the changes that should cover this issue.
Thanks for your attention.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
