Bug#930367: marked as done (vagrant images: network setup in libvirt images are not consistent with Debian defaults)
Your message dated Sun, 28 Feb 2021 15:30:10 +0100
with message-id <20210228143010.GA23170@xanadu.blop.info>
and subject line Re: Bug#930367: Virtualbox default network behaviour for Buster
has caused the Debian Bug report #930367,
regarding vagrant images: network setup in libvirt images are not consistent with Debian defaults
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 owner@bugs.debian.org
immediately.)
--
930367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930367
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: cloud.debian.org: vagrant images: use systemd-networkd for virtualbox provider
- From: Nicolas Quiniou-Briand <nqb@azyx.fr>
- Date: Tue, 11 Jun 2019 16:15:12 +0200
- Message-id: <0f79be33-0b0a-2092-12bb-976c09123728@azyx.fr>
Package: cloud.debian.org
Severity: normal
Dear Maintainer,
I noticed a difference between providers for the same box
(debian/stretch64):
* with libvirt provider, `systemd-networkd` service is enabled and started
after first boot of VM.
* with virtualbox provider, `systemd-networkd`
service is disabled and stopped after first boot of VM.
It will be better to have only one way to manage network for the same
image with different providers.
--- End Message ---
--- Begin Message ---
- To: Emmanuel Kasper <emmanuel@libera.cc>, 930367-done@bugs.debian.org
- Subject: Re: Bug#930367: Virtualbox default network behaviour for Buster
- From: Lucas Nussbaum <lucas@debian.org>
- Date: Sun, 28 Feb 2021 15:30:10 +0100
- Message-id: <20210228143010.GA23170@xanadu.blop.info>
- In-reply-to: <ecd4d69e-3ce6-d7bc-1d41-83d3a9cd5d7a@libera.cc>
- References: <0f79be33-0b0a-2092-12bb-976c09123728@azyx.fr> <ecd4d69e-3ce6-d7bc-1d41-83d3a9cd5d7a@libera.cc>
Hi,
This was fixed with today's update of buster64 and contrib-buster64 for
those images. (see
https://lists.debian.org/debian-cloud/2021/02/msg00070.html )
I think that the bug can be closed even if it is not fixed in the
stretch image. I consider the bug 'wontfix' for stretch (it is a bit
late to change that behaviour now). But feel free to disagree and
reopen.
Lucas
--- End Message ---
Reply to: