yahoo-eng-team team mailing list archive

[Ian Johnson <1905983@xxxxxxxxxxxxxxxxxx>]

> The problem is that snapd is configuring cloud-init in a way that
ensures that cloud-init will detect all subsequent boots as first ones
if the instance ID is only provided by a configuration ISO

What if snapd also recorded the same instance_id in the zzzz_snapd.cfg
file as from first-boot? would cloud-init then do the right thing on
reboots?

I admit I'm a bit unclear what the right thing for cloud-init to do here
is, because the behavior is confusing to me. It really seems to me like
cloud-init should cache or otherwise process the data it gets from the
first-boot so that other things like netplan or systemd apply the
configuration on subsequent boots without needing cloud-init to run. Or
is the issue that when cloud-init runs on subsequent boots it _undoes_
the processing from cloud-init on the first boot?

** Also affects: snapd
   Importance: Undecided
       Status: New

-- 
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:
  Incomplete
Status in snapd:
  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