touch-packages team mailing list archive

[Adam Stokes <adam.stokes@xxxxxxxxxxxxx>]

** Description changed:

  [Problem]
  The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes:
  
  It inspects the network to try to pick a 10.0.N.0 network that isn't
  being used, with N starting at 3, so this appears to have picked
  10.0.3.0 when it was installed on whatever system was generating the
  image. This conflicts with the network that eth0 gets attached to when
  the image is brought up in a container, because it gets attached to the
  host's lxcbr0, which is using 10.0.3.x.
  
- This affects LXC, and should affect LXD but doesn't currently. (see #2)
+ This affects LXC, and should affect LXD but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release.
  The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host:
  
  [Test Case]
  
  sudo lxc-create -t ubuntu-cloud -n wily
  sudo lxc-start -n wily
  sudo lxc-attach -n wily
  # inside container, test connectivity, eg:
  apt-get update
  
  [Regression Potentional]
  Currently none as networking didn't work initially.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414

Title:
  lxc postinst script checks available interfaces, can choose

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  [Problem]
  The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes:

  It inspects the network to try to pick a 10.0.N.0 network that isn't
  being used, with N starting at 3, so this appears to have picked
  10.0.3.0 when it was installed on whatever system was generating the
  image. This conflicts with the network that eth0 gets attached to when
  the image is brought up in a container, because it gets attached to
  the host's lxcbr0, which is using 10.0.3.x.

  This affects LXC, and should affect LXD but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release.
  The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host:

  [Test Case]

  sudo lxc-create -t ubuntu-cloud -n wily
  sudo lxc-start -n wily
  sudo lxc-attach -n wily
  # inside container, test connectivity, eg:
  apt-get update

  [Regression Potentional]
  Currently none as networking didn't work initially.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions