yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

This bug is believed to be fixed in cloud-init in 17.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/1693251

Title:
  cloud-init should configure networkmanager to not manage
  /etc/resolv.conf

Status in cloud-init:
  Fix Released

Bug description:
  Currently, cloud-init adds nameserver entries directly to
  /etc/resolv.conf but does not configure namservers in per-interface
  configuration files.  This could be problematic because information
  received from other sources (e.g., from another interface that is
  using dhcp) could clobber the information in /etc/resolv.conf.

  Unfortunately, at least under OpenStack, the nameserver information is
  not interface-scoped so it is not *possible* to correctly configure
  the interface configuration files.

  The solution in this case is to ensure that NM will not attempt to
  update /etc/resolv.conf.  The simplest way of doing this is to drop a
  file into /etc/NetworkManager/conf.d containing:

    [main]
    dns=none

  This will prevent NetworkManager from managing /etc/resolv.conf.

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