group.of.nepali.translators team mailing list archive

[Joshua Powers <josh.powers@xxxxxxxxxxxxx>]

Marking all fixed-released and unsubscribing field-critical.

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

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1815051

Title:
  Bionic netplan render invalid yaml duplicate anchor declaration for
  nameserver entries

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released
Status in cloud-init source package in Cosmic:
  Fix Released

Bug description:
  The netplan configuration redeclares the nameservers anchor for every
  single section (vlans, bonds), and use the same id for similar entries
  (id001).

  In this specific case the network configuration in maas have a bond0
  with two vlans, bond0.3502 and bond0.3503, and an untagged bond1
  without vlans. The rendered 50-cloud-init.yaml looks like this:

  network:
      version: 2
      ethernets:
  ...
      bonds:
  ...
          bond1:
  ...
              nameservers: &id001 <- anchor declaration here
                  addresses:
                  - 255.255.255.1
                  - 255.255.255.2
                  - 255.255.255.3
                  - 255.255.255.5
                  search:
                  - customer.domain
                  - maas
  ...
          bondM:
  ...
              nameservers: *id001

     vlans:
          bond0.3502:
  ...
              nameservers: &id001 <- anchor redeclaration here
                  addresses:
                  - 255.255.255.1
                  - 255.255.255.2
                  - 255.255.255.3
                  - 255.255.255.5
                  search:
                  - customer.domain
                  - maas
          bond0.3503:
  ...
              nameservers: *id001

  As the cloudinit renders an invalid yaml file, the netplan apply
  produces the following error: (due to the anchor redeclaration in the
  vlans section):

     Invalid YAML at /etc/netplan/50-cloud-init.yaml line 118 column 25:
  second occurence

  This render bug prevents us using the untagged bond and the bond with
  the vlans in the same configuration.

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