subject:"\\\\\\\[Group.of.nepali.translators\\\\\\\] \\\\\\\[Bug 1735331\\\\\\\] Re\\\\\\\: ec2\\\\\\\: zesty tempfile sandbox dhclient.pid file can't be created"

[Group.of.nepali.translators] [Bug 1735331] Re: ec2: zesty tempfile sandbox dhclient.pid file can't be created

2017-12-14 Thread Scott Moser

This bug is believed to be fixed in cloud-init in 1705804. 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/1735331

Title:
  ec2: zesty tempfile sandbox dhclient.pid file can't be created

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 Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Ec2 instances could hit race condition with tempdir removal where dhclient 
doesn't write a pidfile and DataSourceEc2Local hits a traceback trying to read 
that non-existent pidfile. This traceback causes the instance to fallback and 
get discovered in init-network stage as DataSourceEc2. The thrashing costs 
instances a couple extra seconds to boot while re-discovering in a different 
stage.

  [Test Case]

  # Launch instance under test
  $ for release in xenial zesty artful; do
  echo "Handling $release";
  launch-ec2 --series $release;
  ssh ubuntu@ cat /run/cloud-init/result.json;
  ssh ubuntu@ grep Trace /var/log/cloud-init.log;
  ssh ubuntu@ sudo sed 's/ $release / $release-proposed /' 
/etc/apt/sources.list;
  ssh ubuntu@ sudo apt update;
  ssh ubuntu@ sudo apt install cloud-init;
  # Show upgrade without restart doesn't break
  ssh ubuntu@ sudo cloud-init init;
  # Show clean install doesn't break
  ssh ubuntu@ 'sudo rm -rf /var/log/cloud-init* 
/var/lib/cloud; sudo reboot'
  ssh ubuntu@ 'sudo cat /run/cloud-init/result.json
  ssh ubuntu@ 'sudo grep Trace /var/log/cloud-init*';
  # Asssert no intermittent tracebacks from dhcp_discovery and no leaked 
dhcpclients;
  ssh ubuntu@ "sudo python3 -c 'from cloudinit.net.dhcp import 
maybe_perform_dhcp_discovery; maybe_perform_dhcp_discovery()";
  sudo ps -afe |grep dhclient;
    done

  [Regression Potential]
  Regression would still result in Tracebacks in DataSourceEc2Local which would 
cause cloud-init to fallback to DataSourceEc2 in init-network stage.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=7acc9e68f
  === End SRU Template ===

  === Original Description ===

  Saw an issue once on EC2 zesty image with 17.1.41 during SRU testing.

  Looks like we hit an inability to create the pid file (from syslog)

   syslog
  Nov 30 04:20:35 ip-10-0-20-176 cloud-init[440]: Cloud-init v. 17.1 running 
'init-local' at Thu, 30 Nov 2017 04:20:32 +. Up 7.16 seconds.
  Nov 30 04:20:35 ip-10-0-20-176 cloud-init[440]: 2017-11-30 04:20:32,768 - 
util.py[WARNING]: Getting data from  failed
  Nov 30 04:20:35 ip-10-0-20-176 dhclient[669]: Can't create 
/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhclient.pid: No such file or 
directory

   end syslog

  A traceback when trying to read the temporary pid file that was
  created  by our dhclient run during Ec2Local setup. Maybe we exited
  out of the dhcp run before we could read the pid file?

  ...
  2017-11-30 04:20:32,738 - util.py[DEBUG]: Running command ['ip', 'link', 
'set', 'dev', 'eth0', 'up'] with allowed return codes [0] (shell=False, 
capture=True)
  2017-11-30 04:20:32,744 - util.py[DEBUG]: Running command 
['/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhclient', '-1', '-v', '-lf', 
'/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhcp.leases', '-pf', 
'/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhclient.pid', 'eth0', '-sf', 
'/bin/true'] with allowed return codes [0] (shell=False, capture=True)
  2017-11-30 04:20:32,768 - util.py[DEBUG]: Reading from 
/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhclient.pid (quiet=False)
  2017-11-30 04:20:32,768 - handlers.py[DEBUG]: finish: 
init-local/search-Ec2Local: FAIL: no local data found from DataSourceEc2Local
  2017-11-30 04:20:32,768 - util.py[WARNING]: Getting data from  failed
  2017-11-30 04:20:32,768 - util.py[DEBUG]: Getting data from  failed
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 
332, in find_source
  if s.get_data():
    File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceEc2.py", 
line 378, in get_data
  return super(DataSourceEc2Local, self).get_data()
    File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceEc2.py", 
line 100, in get_data
  self.fallback_interface)
    File "/usr/lib/python3/dist-packages/cloudinit/net/dhcp.py", line 57, in 
maybe_perform_dhcp_discovery
  return dhcp_discovery(dhclient_path, nic, tdir)

[Group.of.nepali.translators] [Bug 1735331] Re: ec2: zesty tempfile sandbox dhclient.pid file can't be created

2017-12-12 Thread Launchpad Bug Tracker

This bug was fixed in the package cloud-init -
17.1-46-g7acc9e68-0ubuntu1~17.04.1

---
cloud-init (17.1-46-g7acc9e68-0ubuntu1~17.04.1) zesty-proposed; urgency=medium

  * New upstream snapshot.
- ec2: Fix sandboxed dhclient background process cleanup.
  (LP: #1735331)
- tests: NoCloudKVMImage do not modify the original local cache image.
- tests: Enable bionic in integration tests. [Joshua Powers]
- tests: Use apt-get to install a deb so that depends get resolved.
- sysconfig: Correctly render dns and dns search info.
  [Ryan McCabe]

cloud-init (17.1-41-g76243487-0ubuntu1~17.04.1) zesty-proposed;
urgency=medium

  * debian/cloud-init.templates: Fix capitilazation in 'AliYun'
(LP: #1728186)
  * New upstream snapshot (LP: #1733653)
- integration test: replace curtin test ppa with cloud-init test ppa.
- EC2: Fix bug using fallback_nic and metadata when restoring from cache.
- EC2: Kill dhclient process used in sandbox dhclient.
- ntp: fix configuration template rendering for openSUSE and SLES
- centos: Provide the failed #include url in error messages
- Catch UrlError when #include'ing URLs [Andrew Jorgensen]
- hosts: Fix openSUSE and SLES setup for /etc/hosts and clarify docs.
  [Robert Schweikert]
- rh_subscription: Perform null checks for enabled and disabled repos.
  [Dave Mulford]
- Improve warning message when a template is not found.
  [Robert Schweikert]
- Replace the temporary i9n.brickies.net with i9n.cloud-init.io.
- Azure: don't generate network configuration for SRIOV devices
- tests: address some minor feedback missed in last merge.
- tests: integration test cleanup and full pass of nocloud-kvm.
- Gentoo: chmod +x on all files in sysvinit/gentoo/
  [Carlos Konstanski]

 -- Chad Smith   Fri, 01 Dec 2017 10:02:24
-0700

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

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

Title:
  ec2: zesty tempfile sandbox dhclient.pid file can't be created

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 Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Ec2 instances could hit race condition with tempdir removal where dhclient 
doesn't write a pidfile and DataSourceEc2Local hits a traceback trying to read 
that non-existent pidfile. This traceback causes the instance to fallback and 
get discovered in init-network stage as DataSourceEc2. The thrashing costs 
instances a couple extra seconds to boot while re-discovering in a different 
stage.

  [Test Case]

  # Launch instance under test
  $ for release in xenial zesty artful; do
  echo "Handling $release";
  launch-ec2 --series $release;
  ssh ubuntu@ cat /run/cloud-init/result.json;
  ssh ubuntu@ grep Trace /var/log/cloud-init.log;
  ssh ubuntu@ sudo sed 's/ $release / $release-proposed /' 
/etc/apt/sources.list;
  ssh ubuntu@ sudo apt update;
  ssh ubuntu@ sudo apt install cloud-init;
  # Show upgrade without restart doesn't break
  ssh ubuntu@ sudo cloud-init init;
  # Show clean install doesn't break
  ssh ubuntu@ 'sudo rm -rf /var/log/cloud-init* 
/var/lib/cloud; sudo reboot'
  ssh ubuntu@ 'sudo cat /run/cloud-init/result.json
  ssh ubuntu@ 'sudo grep Trace /var/log/cloud-init*';
  # Asssert no intermittent tracebacks from dhcp_discovery and no leaked 
dhcpclients;
  ssh ubuntu@ "sudo python3 -c 'from cloudinit.net.dhcp import 
maybe_perform_dhcp_discovery; maybe_perform_dhcp_discovery()";
  sudo ps -afe |grep dhclient;
    done

  [Regression Potential]
  Regression would still result in Tracebacks in DataSourceEc2Local which would 
cause cloud-init to fallback to DataSourceEc2 in init-network stage.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=7acc9e68f
  === End SRU Template ===

  === Original Description ===

  Saw an issue once on EC2 zesty image with 17.1.41 during SRU testing.

  Looks like we hit an inability to create the pid file (from syslog)

   syslog
  Nov 30 04:20:35 ip-10-0-20-176 cloud-init[440]: Cloud-init v. 17.1 running 
'init-local' at Thu, 30 Nov 2017 04:20:32 +. Up 7.16 seconds.
  Nov 30 04:20:35 ip-10-0-20-176 cloud-init[440]: 2017-11-30 04:20:32,768 - 
util.py[WARNING]: Getting data from  failed
  Nov 30 04:20:35 ip-10-0-20-176 dhclient[669]: Can't

[Group.of.nepali.translators] [Bug 1735331] Re: ec2: zesty tempfile sandbox dhclient.pid file can't be created

2017-12-12 Thread Launchpad Bug Tracker

This bug was fixed in the package cloud-init -
17.1-46-g7acc9e68-0ubuntu1~16.04.1

---
cloud-init (17.1-46-g7acc9e68-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream snapshot.
- ec2: Fix sandboxed dhclient background process cleanup.
  (LP: #1735331)
- tests: NoCloudKVMImage do not modify the original local cache image.
- tests: Enable bionic in integration tests. [Joshua Powers]
- tests: Use apt-get to install a deb so that depends get resolved.
- sysconfig: Correctly render dns and dns search info.
  [Ryan McCabe]

cloud-init (17.1-41-g76243487-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * debian/cloud-init.templates: Fix capitilazation in 'AliYun'
(LP: #1728186)
  * New upstream snapshot (LP: #1733653)
- integration test: replace curtin test ppa with cloud-init test ppa.
- EC2: Fix bug using fallback_nic and metadata when restoring from cache.
- EC2: Kill dhclient process used in sandbox dhclient.
- ntp: fix configuration template rendering for openSUSE and SLES
- centos: Provide the failed #include url in error messages
- Catch UrlError when #include'ing URLs [Andrew Jorgensen]
- hosts: Fix openSUSE and SLES setup for /etc/hosts and clarify docs.
  [Robert Schweikert]
- rh_subscription: Perform null checks for enabled and disabled repos.
  [Dave Mulford]
- Improve warning message when a template is not found.
  [Robert Schweikert]
- Replace the temporary i9n.brickies.net with i9n.cloud-init.io.
- Azure: don't generate network configuration for SRIOV devices
- tests: address some minor feedback missed in last merge.
- tests: integration test cleanup and full pass of nocloud-kvm.
- Gentoo: chmod +x on all files in sysvinit/gentoo/
  [Carlos Konstanski]

 -- Chad Smith   Fri, 01 Dec 2017 10:05:01
-0700

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

Title:
  ec2: zesty tempfile sandbox dhclient.pid file can't be created

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 Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Ec2 instances could hit race condition with tempdir removal where dhclient 
doesn't write a pidfile and DataSourceEc2Local hits a traceback trying to read 
that non-existent pidfile. This traceback causes the instance to fallback and 
get discovered in init-network stage as DataSourceEc2. The thrashing costs 
instances a couple extra seconds to boot while re-discovering in a different 
stage.

  [Test Case]

  # Launch instance under test
  $ for release in xenial zesty artful; do
  echo "Handling $release";
  launch-ec2 --series $release;
  ssh ubuntu@ cat /run/cloud-init/result.json;
  ssh ubuntu@ grep Trace /var/log/cloud-init.log;
  ssh ubuntu@ sudo sed 's/ $release / $release-proposed /' 
/etc/apt/sources.list;
  ssh ubuntu@ sudo apt update;
  ssh ubuntu@ sudo apt install cloud-init;
  # Show upgrade without restart doesn't break
  ssh ubuntu@ sudo cloud-init init;
  # Show clean install doesn't break
  ssh ubuntu@ 'sudo rm -rf /var/log/cloud-init* 
/var/lib/cloud; sudo reboot'
  ssh ubuntu@ 'sudo cat /run/cloud-init/result.json
  ssh ubuntu@ 'sudo grep Trace /var/log/cloud-init*';
  # Asssert no intermittent tracebacks from dhcp_discovery and no leaked 
dhcpclients;
  ssh ubuntu@ "sudo python3 -c 'from cloudinit.net.dhcp import 
maybe_perform_dhcp_discovery; maybe_perform_dhcp_discovery()";
  sudo ps -afe |grep dhclient;
    done

  [Regression Potential]
  Regression would still result in Tracebacks in DataSourceEc2Local which would 
cause cloud-init to fallback to DataSourceEc2 in init-network stage.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=7acc9e68f
  === End SRU Template ===

  === Original Description ===

  Saw an issue once on EC2 zesty image with 17.1.41 during SRU testing.

  Looks like we hit an inability to create the pid file (from syslog)

   syslog
  Nov 30 04:20:35 ip-10-0-20-176 cloud-init[440]: Cloud-init v. 17.1 running 
'init-local' at Thu, 30 Nov 2017 04:20:32 +. Up 7.16 seconds.
  Nov 30 04:20:35 ip-10-0-20-176 cloud-init[440]: 2017-11-30 04:20:32,768 - 
util.py[WARNING]: Getting data from  failed
  Nov 30 04:20:35 ip-10-0-20-176 dhclient[669]: Can't create 
/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhclient.pid: No such file or

[Group.of.nepali.translators] [Bug 1735331] Re: ec2: zesty tempfile sandbox dhclient.pid file can't be created

2017-11-30 Thread Launchpad Bug Tracker

This bug was fixed in the package cloud-init -
17.1-46-g7acc9e68-0ubuntu1

---
cloud-init (17.1-46-g7acc9e68-0ubuntu1) bionic; urgency=medium

  * New upstream snapshot.
- ec2: Fix sandboxed dhclient background process cleanup.
  [Chad Smith] (LP: #1735331)
- tests: NoCloudKVMImage do not modify the original local cache image.
- tests: Enable bionic in integration tests. [Joshua Powers]
- tests: Use apt-get to install a deb so that depends get resolved.
- sysconfig: Correctly render dns and dns search info.
  [Ryan McCabe] (LP: #1705804)

 -- Scott Moser   Thu, 30 Nov 2017 21:59:55 -0500

** Changed in: cloud-init (Ubuntu Bionic)
   Status: New => 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/1735331

Title:
  ec2: zesty tempfile sandbox dhclient.pid file can't be created

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  New
Status in cloud-init source package in Zesty:
  New
Status in cloud-init source package in Artful:
  New
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  Saw an issue once on EC2 zesty image with 17.1.41 during SRU testing.

  Looks like we hit an inability to create the pid file (from syslog)

  
   syslog
  Nov 30 04:20:35 ip-10-0-20-176 cloud-init[440]: Cloud-init v. 17.1 running 
'init-local' at Thu, 30 Nov 2017 04:20:32 +. Up 7.16 seconds.
  Nov 30 04:20:35 ip-10-0-20-176 cloud-init[440]: 2017-11-30 04:20:32,768 - 
util.py[WARNING]: Getting data from  failed
  Nov 30 04:20:35 ip-10-0-20-176 dhclient[669]: Can't create 
/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhclient.pid: No such file or 
directory


   end syslog


  
  A traceback when trying to read the temporary pid file that was created  by 
our dhclient run during Ec2Local setup. Maybe we exited out of the dhcp run 
before we could read the pid file?

  ...
  2017-11-30 04:20:32,738 - util.py[DEBUG]: Running command ['ip', 'link', 
'set', 'dev', 'eth0', 'up'] with allowed return codes [0] (shell=False, 
capture=True)
  2017-11-30 04:20:32,744 - util.py[DEBUG]: Running command 
['/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhclient', '-1', '-v', '-lf', 
'/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhcp.leases', '-pf', 
'/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhclient.pid', 'eth0', '-sf', 
'/bin/true'] with allowed return codes [0] (shell=False, capture=True)
  2017-11-30 04:20:32,768 - util.py[DEBUG]: Reading from 
/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhclient.pid (quiet=False)
  2017-11-30 04:20:32,768 - handlers.py[DEBUG]: finish: 
init-local/search-Ec2Local: FAIL: no local data found from DataSourceEc2Local
  2017-11-30 04:20:32,768 - util.py[WARNING]: Getting data from  failed
  2017-11-30 04:20:32,768 - util.py[DEBUG]: Getting data from  failed
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 
332, in find_source
  if s.get_data():
    File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceEc2.py", 
line 378, in get_data
  return super(DataSourceEc2Local, self).get_data()
    File "/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceEc2.py", 
line 100, in get_data
  self.fallback_interface)
    File "/usr/lib/python3/dist-packages/cloudinit/net/dhcp.py", line 57, in 
maybe_perform_dhcp_discovery
  return dhcp_discovery(dhclient_path, nic, tdir)
    File "/usr/lib/python3/dist-packages/cloudinit/net/dhcp.py", line 124, in 
dhcp_discovery
  pid = int(util.load_file(pid_file).strip())
    File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1257, in 
load_file
  with open(fname, 'rb') as ifh:
  FileNotFoundError: [Errno 2] No such file or directory: 
'/var/tmp/cloud-init/cloud-init-dhcp-hnatdvwi/dhclient.pid'

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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1735331] Re: ec2: zesty tempfile sandbox dhclient.pid file can't be created

[Group.of.nepali.translators] [Bug 1735331] Re: ec2: zesty tempfile sandbox dhclient.pid file can't be created

[Group.of.nepali.translators] [Bug 1735331] Re: ec2: zesty tempfile sandbox dhclient.pid file can't be created

[Group.of.nepali.translators] [Bug 1735331] Re: ec2: zesty tempfile sandbox dhclient.pid file can't be created

4 matches

Site Navigation

Mail list logo

Footer information