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

2017-09-22 Thread Scott Moser 
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/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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

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

2017-04-20 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init - 0.7.9-90-g61eb03fe-
0ubuntu1~16.04.1

---
cloud-init (0.7.9-90-g61eb03fe-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/cloud-init.templates: add Bigstep to list of sources. (LP: #1676460)
  * New upstream snapshot.
- OpenStack: add 'dvs' to the list of physical link types. (LP: #1674946)
- Fix bug that resulted in an attempt to rename bonds or vlans.
  (LP: #1669860)
- tests: update OpenNebula and Digital Ocean to not rely on host
  interfaces.
- net: in netplan renderer delete known image-builtin content.
  (LP: #1675576)
- doc: correct grammar in capabilities.rst [David Tagatac]
- ds-identify: fix detecting of maas datasource. (LP: #1677710)
- netplan: remove debugging prints, add debug logging [Ryan Harper]
- ds-identify: do not write None twice to datasource_list.
- support resizing partition and rootfs on system booted without
  initramfs.  [Steve Langasek] (LP: #1677376)
- apt_configure: run only when needed. (LP: #1675185)
- OpenStack: identify OpenStack by product 'OpenStack Compute'.
  (LP: #1675349)
- GCE: Search GCE in ds-identify, consider serial number in check.
  (LP: #1674861)
- Add support for setting hashed passwords [Tore S. Lonoy] (LP: #1570325)
- Fix filesystem creation when using "partition: auto"
  [Jonathan Ballet] (LP: #1634678)
- ConfigDrive: support reading config drive data from /config-drive.
  (LP: #1673411)
- ds-identify: fix detection of Bigstep datasource. (LP: #1674766)
- test: add running of pylint [Joshua Powers]
- ds-identify: fix bug where filename expansion was left on.
- advertise network config v2 support (NETWORK_CONFIG_V2) in features.
- Bigstep: fix bug when executing in python3. [root]
- Fix unit test when running in a system deployed with cloud-init.
- Bounce network interface for Azure when using the built-in path.
  [Brent Baude] (LP: #1674685)
- cloudinit.net: add network config v2 parsing and rendering [Ryan Harper]
- net: Fix incorrect call to isfile [Joshua Powers] (LP: #1674317)
- net: add renderers for automatically selecting the renderer.
- doc: fix config drive doc with regard to unpartitioned disks.
  (LP: #1673818)
- test: Adding integratiron test for password as list [Joshua Powers]
- render_network_state: switch arguments around, do not require target
- support 'loopback' as a device type.
- Integration Testing: improve testcase subclassing [Wesley Wiedenmeier]
- gitignore: adding doc/rtd_html [Joshua Powers]
- doc: add instructions for running integration tests via tox.
  [Joshua Powers]
- test: avoid differences in 'date' output due to daylight savings.
- Fix chef config module in omnibus install. [Jeremy Melvin] (LP: #1583837)
- Add feature flags to cloudinit.version. [Wesley Wiedenmeier]
- tox: add a citest environment
- Support chpasswd/list being a list in addition to a string.
  [Sergio Lystopad] (LP: #1665694)
- doc: Fix configuration example for cc_set_passwords module.
  [Sergio Lystopad] (LP: #1665773)
- net: support both ipv4 and ipv6 gateways in sysconfig.
  [Lars Kellogg-Stedman] (LP: #1669504)
- net: do not raise exception for > 3 nameservers
  [Lars Kellogg-Stedman] (LP: #1670052)

 -- Scott Moser   Mon, 03 Apr 2017 11:52:56 -0400

** Changed in: cloud-init (Ubuntu Xenial)
   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/1670052

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

Status in cloud-init:
  Fix Committed
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

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

2017-04-20 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init - 0.7.9-90-g61eb03fe-
0ubuntu1~16.10.1

---
cloud-init (0.7.9-90-g61eb03fe-0ubuntu1~16.10.1) yakkety; urgency=medium

  * debian/cloud-init.templates: add Bigstep to list of sources. (LP: #1676460)
  * New upstream snapshot.
- OpenStack: add 'dvs' to the list of physical link types. (LP: #1674946)
- Fix bug that resulted in an attempt to rename bonds or vlans.
  (LP: #1669860)
- tests: update OpenNebula and Digital Ocean to not rely on host
  interfaces.
- net: in netplan renderer delete known image-builtin content.
  (LP: #1675576)
- doc: correct grammar in capabilities.rst [David Tagatac]
- ds-identify: fix detecting of maas datasource. (LP: #1677710)
- netplan: remove debugging prints, add debug logging [Ryan Harper]
- ds-identify: do not write None twice to datasource_list.
- support resizing partition and rootfs on system booted without
  initramfs.  [Steve Langasek] (LP: #1677376)
- apt_configure: run only when needed. (LP: #1675185)
- OpenStack: identify OpenStack by product 'OpenStack Compute'.
  (LP: #1675349)
- GCE: Search GCE in ds-identify, consider serial number in check.
  (LP: #1674861)
- Add support for setting hashed passwords [Tore S. Lonoy] (LP: #1570325)
- Fix filesystem creation when using "partition: auto"
  [Jonathan Ballet] (LP: #1634678)
- ConfigDrive: support reading config drive data from /config-drive.
  (LP: #1673411)
- ds-identify: fix detection of Bigstep datasource. (LP: #1674766)
- test: add running of pylint [Joshua Powers]
- ds-identify: fix bug where filename expansion was left on.
- advertise network config v2 support (NETWORK_CONFIG_V2) in features.
- Bigstep: fix bug when executing in python3. [root]
- Fix unit test when running in a system deployed with cloud-init.
- Bounce network interface for Azure when using the built-in path.
  [Brent Baude] (LP: #1674685)
- cloudinit.net: add network config v2 parsing and rendering [Ryan Harper]
- net: Fix incorrect call to isfile [Joshua Powers] (LP: #1674317)
- net: add renderers for automatically selecting the renderer.
- doc: fix config drive doc with regard to unpartitioned disks.
  (LP: #1673818)
- test: Adding integratiron test for password as list [Joshua Powers]
- render_network_state: switch arguments around, do not require target
- support 'loopback' as a device type.
- Integration Testing: improve testcase subclassing [Wesley Wiedenmeier]
- gitignore: adding doc/rtd_html [Joshua Powers]
- doc: add instructions for running integration tests via tox.
  [Joshua Powers]
- test: avoid differences in 'date' output due to daylight savings.
- Fix chef config module in omnibus install. [Jeremy Melvin] (LP: #1583837)
- Add feature flags to cloudinit.version. [Wesley Wiedenmeier]
- tox: add a citest environment
- Support chpasswd/list being a list in addition to a string.
  [Sergio Lystopad] (LP: #1665694)
- doc: Fix configuration example for cc_set_passwords module.
  [Sergio Lystopad] (LP: #1665773)
- net: support both ipv4 and ipv6 gateways in sysconfig.
  [Lars Kellogg-Stedman] (LP: #1669504)
- net: do not raise exception for > 3 nameservers
  [Lars Kellogg-Stedman] (LP: #1670052)

 -- Scott Moser   Mon, 03 Apr 2017 12:03:30 -0400

** Changed in: cloud-init (Ubuntu Yakkety)
   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/1670052

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

Status in cloud-init:
  Fix Committed
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

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

2017-04-04 Thread Scott Moser 
** 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 Yahoo!
Engineering Team, which is subscribed to cloud-init.
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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp