yahoo-eng-team team mailing list archive

[Scott Moser <ssmoser2+ubuntu@xxxxxxxxx>]

This bug is believed to be fixed in cloud-init in 1705804. If this is
still a problem for you, please make a comment and set the state back to
New

Thank you.

** Changed in: cloud-init
       Status: Fix Committed => 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/1721157

Title:
  netplan render drops bridge_stp setting

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

Bug description:
  cloud-init tip fails to render a netplan bridge configuration with a
  stp value.

  % cat network_configs/bridge-simple.yaml 
  showtrace: true
  network:
      version: 1
      config:
          # Physical interfaces.
          - type: physical
            name: eth0
            mac_address: "52:54:00:12:34:00"
            subnets:
                - type: dhcp4
          - type: physical
            name: eth1
            mac_address: "52:54:00:12:34:02"
          # Bridge
          - type: bridge
            name: br0
            bridge_interfaces:
              - eth1
            params:
                bridge_fd: 150
                bridge_stp: 'off'

  
  Currently renders a netplan config of:

  network:
      version: 2
      ethernets:
          eth0:
              dhcp4: true
              match:
                  macaddress: '52:54:00:12:34:00'
              set-name: eth0
          eth1:
              match:
                  macaddress: '52:54:00:12:34:02'
              set-name: eth1
      bridges:
          br0:
              interfaces:
              - eth1
              parameters:
                  forward-delay: 150

  
  netplan in artful with bridge stp support enables STP by default (unless disabled)
  This prevents setting some values of forward-delay.  In any case, we should translate
  the bridge_stp value to the netplan boolean.

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