group.of.nepali.translators 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 नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1670052

Title:
  cloud-init raises an exception when it sees more than 3 nameservers

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact] 
  When rendering sysconfig (redhat/centos) output there was a bug
  where cloud-init would error if provided with more than 3 nameservers.

  That was changed to a warning.
     
  [Test Case]
  This can't really be tested on Ubuntu, as ubuntu does not render
  sysconfig network information.
   
  [Regression Potential] 
  Low everywhere (change ValueError to a WARN) and lower on Ubuntu,
  where the code is not in the run path.
     
  [Other Info]
  Upstream commit:
   https://git.launchpad.net/cloud-init/commit/?id=657fd40f9ee692a
     
  === End SRU Template ===

  When running in an environment that provides more than 3 nameservers,
  cloud-init will raise a ValueError exception:

    Mar 04 18:03:01 localhost.localdomain cloud-init[901]: ValueError:
  Adding '8.8.8.8' would go beyond the '3' maximum name servers

  While that is a legitimate complaint, raising an exception seems like
  the wrong response, because this results in *no* nameserver
  configuration, which can have a substantial operational impact on the
  system.  Cloud-init should probably just log a warning in this case,
  and ignore any nameservers received after the first three.

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