** Description changed:

+ [Impact]
+ 
+ Due to the new rendering of /etc/network/interfaces, clients upgrading
+ to newer Cloud-init versions will not get /etc/resolv.conf rendered
+ correctly due to LP: 1657940 (which changed the rendering of
+ /etc/network/interfaces), trigginer LP: #1675571.
+ 
+ With out this update, users upgrading on DigitalOcean will not get DNS
+ resolution.
+ 
+ [Regression Potential]
+ 
+ Low. This change is scope to DigitalOcean only. DigitalOcean has tested
+ this Datasource exhaustively.
+ 
+ [TEST Cases]
+ - provision on DigitalOcean without a private IP
+ - provision on DigitalOcean with a private IP
+ - provision on DigitalOCean with IPV6 and private IP
+ - provision on DigitalOcean with IPV6
+ 
+ In all cases, interfaces should be configured and DNS resolution should
+ work.
+ 
+ 
+ [ORIGINAL REPORT]
+ 
  This is a request to merge the improvements to the linked PR that
  improves the DigitalOcean datasource.
  
  The changes:
  - No longer bind the nameservers to a specific interface to bring it inline 
with the other DataSources like OpenStack and SmartOS.
  - Fix mis-binding the IPV4all address to a secondary interface by considering 
'eth0' or 'ens3' first
  - Consider all network definitions, not just 'public' or 'private'.

** Description changed:

  [Impact]
  
  Due to the new rendering of /etc/network/interfaces, clients upgrading
  to newer Cloud-init versions will not get /etc/resolv.conf rendered
- correctly due to LP: 1657940 (which changed the rendering of
+ correctly due to LP: #1657940 (which changed the rendering of
  /etc/network/interfaces), trigginer LP: #1675571.
  
  With out this update, users upgrading on DigitalOcean will not get DNS
  resolution.
  
  [Regression Potential]
  
  Low. This change is scope to DigitalOcean only. DigitalOcean has tested
  this Datasource exhaustively.
  
  [TEST Cases]
  - provision on DigitalOcean without a private IP
  - provision on DigitalOcean with a private IP
  - provision on DigitalOCean with IPV6 and private IP
  - provision on DigitalOcean with IPV6
  
  In all cases, interfaces should be configured and DNS resolution should
  work.
  
- 
  [ORIGINAL REPORT]
  
  This is a request to merge the improvements to the linked PR that
  improves the DigitalOcean datasource.
  
  The changes:
  - No longer bind the nameservers to a specific interface to bring it inline 
with the other DataSources like OpenStack and SmartOS.
  - Fix mis-binding the IPV4all address to a secondary interface by considering 
'eth0' or 'ens3' first
  - Consider all network definitions, not just 'public' or 'private'.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676908

Title:
  DigitalOcean network improvements

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to