yahoo-eng-team team mailing list archive

[Robert Schweikert <1812853@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

If the user does not supply any dns resolution information in the
configuartion cloud-init should not write a resolv.conf file that just
contains the header. Putting a basically empty resolv.conf file in place
prevents other tools to write the resolv.conf file as it is preseumed
the file is user modified and thus will not be overwritten. However,
what happens is that the resolv.conf file is empty and thus name
resolution is not possible.

Observed on SUSE Linux Enterprise server with config that has no dns
information.

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

** Summary changed:

- shold not write an "empty" resolve.conf file
+ should not write an "empty" resolve.conf file

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

Title:
  should not write an "empty" resolve.conf file

Status in cloud-init:
  New

Bug description:
  If the user does not supply any dns resolution information in the
  configuartion cloud-init should not write a resolv.conf file that just
  contains the header. Putting a basically empty resolv.conf file in
  place prevents other tools to write the resolv.conf file as it is
  preseumed the file is user modified and thus will not be overwritten.
  However, what happens is that the resolv.conf file is empty and thus
  name resolution is not possible.

  Observed on SUSE Linux Enterprise server with config that has no dns
  information.

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