yahoo-eng-team team mailing list archive

[Bert JW Regeer <1620807@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Related to https://bugs.launchpad.net/cloud-init/+bug/1620796 I have
found that even when I have fixed cloud-init to properly write
resolv.conf it gets overwritten as soon as network is started because
NetworkManager takes over control:

/etc/resolv.conf

# Generated by NetworkManager
search novalocal


# No nameservers found; try putting DNS servers into your
# ifcfg files in /etc/sysconfig/network-scripts like so:
#
# DNS1=xxx.xxx.xxx.xxx
# DNS2=xxx.xxx.xxx.xxx
# DOMAIN=lab.foo.com bar.foo.com

instead any DNS entries should be added directly to the ifcfg-eth* files
that are generated, then let NM figure out what DNS resolvers it wants
to add to /etc/resolv.conf.

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


** Tags: centos rhel

** Tags added: rhel

** Tags added: centos

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

Title:
  resolv.conf on CentOS 7/RHEL 7 is NetworkManager managed

Status in cloud-init:
  New

Bug description:
  Related to https://bugs.launchpad.net/cloud-init/+bug/1620796 I have
  found that even when I have fixed cloud-init to properly write
  resolv.conf it gets overwritten as soon as network is started because
  NetworkManager takes over control:

  /etc/resolv.conf

  # Generated by NetworkManager
  search novalocal

  
  # No nameservers found; try putting DNS servers into your
  # ifcfg files in /etc/sysconfig/network-scripts like so:
  #
  # DNS1=xxx.xxx.xxx.xxx
  # DNS2=xxx.xxx.xxx.xxx
  # DOMAIN=lab.foo.com bar.foo.com

  instead any DNS entries should be added directly to the ifcfg-eth*
  files that are generated, then let NM figure out what DNS resolvers it
  wants to add to /etc/resolv.conf.

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