[pkg-lxc-devel] Bug#1010469: Bug#1010469: Bug#1010437: autopkgtest: autopkgtest-build-lxc fails to build working lxc environment

[Julian Gilbey]

On Mon, Feb 06, 2023 at 11:56:51PM +0100, Pierre-Elliott Bécue wrote:
> 
> Julian Gilbey <jdg at debian.org> wrote on 08/08/2022 at 15:47:08+0100:
> 
> > On Mon, Aug 01, 2022 at 10:44:16PM +0200, Pierre-Elliott Bécue wrote:
> >> Julian Gilbey <jdg at debian.org> wrote on 08/06/2022 at 10:50:18+0200:
> 
> Hrmpf, this one slipped out of my todolist, I'm sorry for this, this is
> bad.
> 
> When you indeed reinstalled your system, which version of Debian did you
> install?
> 
> Did you do anything specific before things turned bad again?

Hi Pierre-Elliott,

I was using debian testing (whatever state it was in at the time).

I've just tried reinstalling lxc from scratch with the current debian
testing.  I haven't been able to get as far as reproducing this error,
as I've hit a different snag:

# lxc-create -n debian-sid -t download -- -d debian -r sid -a amd64
# lxc-start -n debian-sid --logfile /tmp/lxc.log --logpriority DEBUG
lxc-start: debian-sid: ../src/lxc/lxccontainer.c: wait_on_daemonized_start: 878 Received container state "ABORTING" instead of "RUNNING"
lxc-start: debian-sid: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: debian-sid: ../src/lxc/tools/lxc_start.c: main: 309 To get more details, run the container in foreground mode
lxc-start: debian-sid: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options

The resulting log file contains the cryptic error messages:

lxc-start debian-sid 20230511122856.360 ERROR    network - ../src/lxc/network.c:netdev_configure_server_veth:711 - No such file or directory - Failed to attach "vethQ4rt4x" to bridge "lxcbr0", bridge interface doesn't exist

That's super-weird; I have no idea what "vethQ4rt4x" is meant to mean.
I think this should probably be a separate bug report, though.
Despite some web searching, I have no idea how to fix this problem,
but I now can't use lxc at all :( I think it's something about lxc-net
not connecting the bridging device to the correct network device
(which in my case is enp5s0).

Best wishes,

   Julian