group.of.nepali.translators team mailing list archive

Thread
Date

[Bug 1670052] Re: cloud-init raises an exception when it sees more than 3 nameservers

To: group.of.nepali.translators@xxxxxxxxxxxxxxxxxxx
From: Scott Moser <smoser@xxxxxxxxxx>
Date: Tue, 04 Apr 2017 20:43:35 -0000
Reply-to: Bug 1670052 <1670052@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu)
       Status: New => Fix Released

** Changed in: cloud-init (Ubuntu)
   Importance: Undecided => Medium

** Also affects: cloud-init (Ubuntu Zesty)
   Importance: Medium
       Status: Fix Released

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu Xenial)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Yakkety)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

-- 
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:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Fix Released

Bug description:
  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