yahoo-eng-team team mailing list archive

[Michał Sawicz <1905983@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

We're implementing extra networking support in Multipass, and relying on
cloud-init to configure them.

On Ubuntu Core 18 images the extra interface's configuration gets purged
after rebooting a couple times.

On first boot:

$ cat /etc/netplan/50-cloud-init.yaml 
# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    ethernets:
        default:
            dhcp4: true
            match:
                macaddress: 52:54:00:f3:9f:51
        extra0:
            dhcp4: true
            dhcp4-overrides:
                route-metric: 200
            match:
                macaddress: 52:54:00:1a:4f:f9
            optional: true
    version: 2

But after (an automatic, due to refresh) reboot or two:

$ cat /etc/netplan/50-cloud-init.yaml 
# This file is generated from information provided by the datasource.  Changes
# to it will not persist across an instance reboot.  To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    ethernets:
        eth0:
            dhcp4: true
            match:
                macaddress: 52:54:00:f3:9f:51
            set-name: eth0
    version: 2

Attached is the result of `collect-logs`.

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Attachment added: "cloud-init.tar.gz"
   https://bugs.launchpad.net/bugs/1905983/+attachment/5438770/+files/cloud-init.tar.gz

-- 
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/1905983

Title:
  Secondary network interface left unconfigured after reboot of Core 18

Status in cloud-init:
  New

Bug description:
  We're implementing extra networking support in Multipass, and relying
  on cloud-init to configure them.

  On Ubuntu Core 18 images the extra interface's configuration gets
  purged after rebooting a couple times.

  On first boot:

  $ cat /etc/netplan/50-cloud-init.yaml 
  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
      ethernets:
          default:
              dhcp4: true
              match:
                  macaddress: 52:54:00:f3:9f:51
          extra0:
              dhcp4: true
              dhcp4-overrides:
                  route-metric: 200
              match:
                  macaddress: 52:54:00:1a:4f:f9
              optional: true
      version: 2

  But after (an automatic, due to refresh) reboot or two:

  $ cat /etc/netplan/50-cloud-init.yaml 
  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
      ethernets:
          eth0:
              dhcp4: true
              match:
                  macaddress: 52:54:00:f3:9f:51
              set-name: eth0
      version: 2

  Attached is the result of `collect-logs`.

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