yahoo-eng-team team mailing list archive

[Chad Smith <1817368@xxxxxxxxxxxxxxxxxx>]

This bug is believed to be fixed in cloud-init in version 19.2-1. 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/1817368

Title:
  udev needs to be triggered if rules are written to a new file

Status in cloud-init:
  Fix Released

Bug description:
  On a VM with many interfaces it is possible that udev is slow. This
  may lead to the situation that 70-persistent-net.rules is being
  written to by cloud-init while also being written to by the net rules
  generator (75-persistent-net-generator.rules). This may lead to
  interleaving, duplicate definitions or incomplete data.

  The user can already specify an optional rules file with the
  "netrules_path". However this will not have any effect when the file
  gets written as udev is not re-triggered. When the user configures a
  custom file (which logically should be something like 71-persistent-
  net.rules) cloud-init should trigger udev to add any new rules the
  code might have written.

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