← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1822353] Re: 19.04 minimal images on GCE intermittently fail to set up networking

 

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => Expired

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

Title:
  19.04 minimal images on GCE intermittently fail to set up networking

Status in cloud-init:
  Expired

Bug description:
  Related to https://bugs.launchpad.net/cloud-init/+bug/1766287 I'd like
  to open a new bug following Disco minimal images failing to set up
  networking due to similar reasons as lp:1766287 with the only
  difference being that no nic was found.

  A workaround was found to set up cloud-init service config:

  /etc/systemd/system/cloud-init-local.service.d/gcp.conf
  ```
  [Unit]
  After=systemd-udev-trigger.service

  [Service]
  ExecStartPre=/bin/udevadm settle
  ```

  The goal of this workaround is to:

  1) ensure that cloud-init-local.service runs after
     systemd-udev-trigger.service starts (this is what triggers
     udev coldplug events, like plugging in the nic)
  2) Run udevadm settle before we start cloud-init local so that any
     nic processing is completed before cloud-init starts looking for
     a nic.

  Currently this is only required on minimal images but there is a
  chance it could occur in base images too should they boot quick
  enough. Minimal disco does not have snap preseeding as base images do and
  due to snap preseeding running before cloud-init it makes it extremely unlikely to
  happen in base images.

  I understand that cloud-init might not be the place to fix the issue
  for all images but I'd like to re-open this bug to start that
  discussion.

  I have attached cloud-init logs, netplan yaml, image manifest and
  sosreports from an instance that failed to set up networking.

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


References