yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1776958@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init -
18.2-77-g4ce67201-0ubuntu1

---------------
cloud-init (18.2-77-g4ce67201-0ubuntu1) cosmic; urgency=medium

  * New upstream snapshot.
    - lxd: Delete default network and detach device if lxd-init created them.
      (LP: #1776958)
    - openstack: avoid unneeded metadata probe on non-openstack platforms
      (LP: #1776701)
    - stages: fix tracebacks if a module stage is undefined or empty
      [Robert Schweikert] (LP: #1770462)
    - Be more safe on string/bytes when writing multipart user-data to disk.
      (LP: #1768600)
    - Fix get_proc_env for pids that have non-utf8 content in environment.
      (LP: #1775371)
    - tests: fix salt_minion integration test on bionic and later
    - tests: provide human-readable integration test summary when --verbose
    - tests: skip chrony integration tests on lxd running artful or older
    - test: add optional --preserve-instance arg to integraiton tests
    - netplan: fix mtu if provided by network config for all rendered types
      (LP: #1774666)
    - tests: remove pip install workarounds for pylxd, take upstream fix.
    - subp: support combine_capture argument.
    - tests: ordered tox dependencies for pylxd install

 -- Chad Smith <chad.smith@xxxxxxxxxxxxx>  Fri, 15 Jun 2018 20:05:07
-0600

** Changed in: cloud-init (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1776958

Title:
  error creating lxdbr0.

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  $ cat > my.yaml <<EOF
  #cloud-config
  lxd:
    init:
      storage_backend: dir
    bridge:
      mode: new
      name: lxdbr0
      ipv4_address: 10.100.100.1
      ipv4_netmask: 24
      ipv4_dhcp_first: 10.100.100.100
      ipv4_dhcp_last: 10.100.100.200
      ipv4_nat: true
      domain: lxd
  EOF

  $ name=c1
  $ lxc launch ubuntu-daily:cosmic $name "--config=user.user-data=$(cat my.yaml)"
  $ sleep 10
  $ lxc exec $name cat /run/cloud-init/result.json
  {
   "v1": {
    "datasource": "DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]",
    "errors": [
     "('lxd', ProcessExecutionError(\"Unexpected error while running command.\\nCommand: ['lxc', 'network', 'create', 'lxdbr0', 'ipv4.address=10.100.100.1/24', 'ipv4.dhcp.ranges=10.100.100.100-10.100.100.200', 'ipv6.address=none', 'dns.domain=lxd', '--force-local']\\nExit code: 1\\nReason: -\\nStdout: \\nStderr: Error: The network already exists\",))"
    ]
   }
  }

  The integration test case tests/cloud_tests/testcases/modules/lxd_bridge.py
  is demonstrates this failure on cosmic.  It currently only occurs on
  cosmic but will occur anywhere with lxd 3.1.0.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cloud-init 18.2-64-gbbcc5e82-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  CloudName: LXD
  Date: Thu Jun 14 18:34:15 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)
  cloud-init-log-warnings:
   2018-06-14 18:34:08,417 - util.py[WARNING]: Running module lxd (<module 'cloudinit.config.cc_lxd' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_lxd.py'>) failed
   cloudinit.util.ProcessExecutionError: Unexpected error while running command.
   Stderr: Error: The network already exists

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1776958/+subscriptions