[Yahoo-eng-team] [Bug 1715095] Re: network is only configured on first boot

2020-10-09 Thread Joshua Powers
** Changed in: cloud-images
   Status: New => Invalid

-- 
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/1715095

Title:
  network is only configured on first boot

Status in cloud-images:
  Invalid
Status in cloud-init:
  Incomplete

Bug description:
  When I create a new VM with an Ubuntu Server Cloud image and using
  cloud-init, the network is only configured on the first boot. After
  the machine has been shut-down and powered up again, the network is no
  longer configured static and instead uses DHCP.

  I’m using the, at the time newest, xenial server cloud image
  (30.08.2017) and use a VM manager called oVirt that uses KVM for
  virtualization.

  cloud-init version 0.7.9
  Ubuntu 16.04.3 LTS

  Steps to reproduce:

  • Download Ubuntu cloud image from https://cloud-images.ubuntu.com/xenial/
  • Mount disk to fix bug #1573095 
(https://bugs.launchpad.net/cloud-images/+bug/1573095)
  • Fix bug with instructions from comment https://bugs.launchpad.net/cloud-
  images/+bug/1573095/comments/15
  • Unmount disk image.
  • Import Image into oVirt.
  • Create new virtual machine in oVirt.
  • Assign disk image to virtual machine.
  • Add cloud init parameters (including static IP conf.) to virtual 
machine.
  • Boot virtual machine.
  • See that networking works and a static IP is configured (ifconfig).
  • See that the network is configured in 
/etc/network/interfaces.d/50-cloud-init.cfg
  • Shutdown (NOT reboot) the virtual machine.
  • Power On the virtual machine.
  • See that DHCP service runs for 5min.
  • After boot see that network is not configured.
  • See that file /etc/network/interfaces.d/50-cloud-init.cfg lost its 
configuration.

  Other possible causes:
  • The cloud image might be wrongly configured to run cloud-init at every 
boot (As reboots 
  are not affected and the server listens for cloud-init configuration 
data after first 
  boot. Also the ssh hostkey is reset every time the machine boots).

  My current workaround:
  • I added the following line to my cloud-init runcmd parameters to copy 
the cloud network 
  file:
  - "cp /etc/network/interfaces.d/50-cloud-init.cfg 
/etc/network/interfaces"
  • I disable cloud-init manually after first boot by adding the following 
line to my cloud-
  init runcmd parameters:
  - [ touch, "/etc/cloud/cloud-init.disabled" ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1715095/+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 1621075] Re: Allow console login is possible when cloud-init fails to run

2020-10-09 Thread Joshua Powers
Hi Kiko,

I am going to add the cloud-init task and let them comment on this.

Thanks!

** Also affects: cloud-init
   Importance: Undecided
   Status: New

** Changed in: cloud-images
   Status: New => Incomplete

-- 
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/1621075

Title:
  Allow console login is possible when cloud-init fails to run

Status in cloud-images:
  Incomplete
Status in cloud-init:
  New

Bug description:
  We are currently investigating how to improve our handling of failures
  during enlistment and commissioning. This bug discusses the situation
  where the boot process did correctly kick off, but cloud-init itself
  failed to correctly start; for instance, the network configuration may
  be incorrect or incomplete.

  The first instinct when there is a failure is to log into the machine,
  but unfortunately that's not currently possible, because there are no
  credentials enabled on the machine. That makes debugging these
  failures particularly difficult.

  Could we detect that cloud-init has failed to run and enable console
  login, perhaps analogously to what happens when Ubuntu fails to mount
  the root filesystem?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1621075/+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 1767131] Re: Pre-seeded snaps are not necessarily available for use in cloud-init user-data

2020-10-09 Thread Joshua Powers
** Changed in: cloud-images
   Status: New => 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/1767131

Title:
  Pre-seeded snaps are not necessarily available for use in cloud-init
  user-data

Status in cloud-images:
  Fix Released
Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  With some cloud software being moved to snaps, cloud-init needs to
  ensure that snaps have been preseeded before user scripts are run, as
  those user scripts may rely on the software within the snap being
  available for use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1767131/+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 1896604] Re: Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal instances

2020-10-09 Thread Joshua Powers
** Changed in: cloud-images
   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/1896604

Title:
  Groovy kernel (5.8.0-1004-aws) creates broken /dev/console on i3.metal
  instances

Status in cloud-images:
  Fix Released
Status in cloud-init:
  Fix Released
Status in linux-aws package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  Starting with kernel 5.8 the default nr_uarts has been changed from 4
  to 2 for amd64, but this seems to affect i3.metal instances in AWS,
  because ttyS0 is now remapped to ttyS4 and this is breaking tools like
  cloud-init (and probably something else).

  [Test case]

  # echo > /dev/console
  bash: echo: write error: Input/output error

  [Fix]

  Setting nr_uarts=4 by default (via CONFIG_SERIAL_8250_RUNTIME_UARTS)
  restores the previous behavior and writing to /dev/console works
  without returning any error.

  [Regression potential]

  Minimal. Restores the old behavior used in 5.4 (that shouldn't have
  changed in the first place).

  [Original bug report]

  Hi,

  When running Groovy daily images on i3.metal instances a broken
  /dev/console is created. The char device appears to be writable but
  writing to it causes an Input/output error. This is breaking cloud-
  init, as it tries to log to /dev/console, and is likely to break other
  programs.

  On Focal:

  root@ip-172-31-24-163:~# ls -l /dev/console
  crw--- 1 root root 5, 1 Sep 21 16:07 /dev/console
  root@ip-172-31-24-163:~# echo x > /dev/console
  root@ip-172-31-24-163:~#

  On Groovy:

  root@ip-172-31-20-184:~# ls -l /dev/console
  crw--w 1 root tty 5, 1 Sep 21 16:03 /dev/console
  root@ip-172-31-20-184:~# echo x > /dev/console
  bash: echo: write error: Input/output error

  The Groovy kernel log has a

  [ 3.561696] fbcon: Taking over console

  line in it, which is not present in the Focal kernel log
  (5.4.0-1024-aws). Perhaps fbcon should be prevented from taking over
  console?

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1896604/+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 1888298] Re: cc_timezone fails on Ubuntu Bionic and Xenial minimal

2020-07-24 Thread Joshua Powers
** Changed in: cloud-init
   Status: Incomplete => New

** Changed in: cloud-images
   Status: New => Invalid

-- 
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/1888298

Title:
  cc_timezone fails on Ubuntu Bionic and Xenial minimal

Status in cloud-images:
  Invalid
Status in cloud-init:
  New

Bug description:
  Summary
  ===
  On Ubuntu Bionic and Xenial minimal images, there is no tzdata package. As a 
result, when cloud-init tries to set the timezone it will fail and produce a 
stack trace.

  Expected Result
  ===
  No trace and no failure of the cloud-config.service :)

  Actual result
  ===
  2020-07-20 18:13:22,515 - util.py[DEBUG]: Running module timezone () failed
    File "/usr/lib/python3/dist-packages/cloudinit/config/cc_timezone.py", line 
47, in handle
  cloud.distro.set_timezone(timezone)
    File "/usr/lib/python3/dist-packages/cloudinit/distros/debian.py", line 
165, in set_timezone
  distros.set_etc_timezone(tz=tz, tz_file=self._find_tz_file(tz))
  OSError: Invalid timezone America/Vancouver, no file found at 
/usr/share/zoneinfo/America/Vancouver

  Steps to reproduce
  ===
  $ wget 
https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img
  $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img 
--name=bionic-minimal
  $ multipass exec bionic-minimal -- sudo systemctl list-units --failed 
--no-legend
  # note that cloud-config.service fails
  $ multipass exec bionic-minimal -- sudo cat /var/log/cloud-init.log | grep 
timezone

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1888298/+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 1888298] [NEW] cc_timezone fails on Ubuntu Bionic and Xenial minimal

2020-07-20 Thread Joshua Powers
Public bug reported:

Summary
===
On Ubuntu Bionic and Xenial minimal images, there is no tzdata package. As a 
result, when cloud-init tries to set the timezone it will fail and produce a 
stack trace.

Expected Result
===
No trace and no failure of the cloud-config.service :)

Actual result
===
2020-07-20 18:13:22,515 - util.py[DEBUG]: Running module timezone () failed
  File "/usr/lib/python3/dist-packages/cloudinit/config/cc_timezone.py", line 
47, in handle
cloud.distro.set_timezone(timezone)
  File "/usr/lib/python3/dist-packages/cloudinit/distros/debian.py", line 165, 
in set_timezone
distros.set_etc_timezone(tz=tz, tz_file=self._find_tz_file(tz))
OSError: Invalid timezone America/Vancouver, no file found at 
/usr/share/zoneinfo/America/Vancouver

Steps to reproduce
===
$ wget 
https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img
$ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img 
--name=bionic-minimal
$ multipass exec bionic-minimal -- sudo systemctl list-units --failed 
--no-legend
# note that cloud-config.service fails
$ multipass exec bionic-minimal -- sudo cat /var/log/cloud-init.log | grep 
timezone

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Description changed:

  Summary
  ===
  On Ubuntu Bionic and Xenial minimal images, there is no tzdata package. As a 
result, when cloud-init tries to set the timezone it will fail and produce a 
stack trace.
  
  Expected Result
  ===
- Options: a) we depend on tzdata b) we do not try to set timezone if tzdata is 
not available c) fail gracefully d) other?
+ No trace and no failure of the cloud-config.service :)
  
  Actual result
  ===
  2020-07-20 18:13:22,515 - util.py[DEBUG]: Running module timezone () failed
-   File "/usr/lib/python3/dist-packages/cloudinit/config/cc_timezone.py", line 
47, in handle
- cloud.distro.set_timezone(timezone)
-   File "/usr/lib/python3/dist-packages/cloudinit/distros/debian.py", line 
165, in set_timezone
- distros.set_etc_timezone(tz=tz, tz_file=self._find_tz_file(tz))
+   File "/usr/lib/python3/dist-packages/cloudinit/config/cc_timezone.py", line 
47, in handle
+ cloud.distro.set_timezone(timezone)
+   File "/usr/lib/python3/dist-packages/cloudinit/distros/debian.py", line 
165, in set_timezone
+ distros.set_etc_timezone(tz=tz, tz_file=self._find_tz_file(tz))
  OSError: Invalid timezone America/Vancouver, no file found at 
/usr/share/zoneinfo/America/Vancouver
  
  Steps to reproduce
  ===
  $ wget 
https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img
  $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img 
--name=bionic-minimal
  $ multipass exec bionic-minimal -- sudo systemctl list-units --failed 
--no-legend
  # note that cloud-config.service fails
  $ multipass exec bionic-minimal -- sudo cat /var/log/cloud-init.log | grep 
timezone

-- 
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/1888298

Title:
  cc_timezone fails on Ubuntu Bionic and Xenial minimal

Status in cloud-init:
  New

Bug description:
  Summary
  ===
  On Ubuntu Bionic and Xenial minimal images, there is no tzdata package. As a 
result, when cloud-init tries to set the timezone it will fail and produce a 
stack trace.

  Expected Result
  ===
  No trace and no failure of the cloud-config.service :)

  Actual result
  ===
  2020-07-20 18:13:22,515 - util.py[DEBUG]: Running module timezone () failed
    File "/usr/lib/python3/dist-packages/cloudinit/config/cc_timezone.py", line 
47, in handle
  cloud.distro.set_timezone(timezone)
    File "/usr/lib/python3/dist-packages/cloudinit/distros/debian.py", line 
165, in set_timezone
  distros.set_etc_timezone(tz=tz, tz_file=self._find_tz_file(tz))
  OSError: Invalid timezone America/Vancouver, no file found at 
/usr/share/zoneinfo/America/Vancouver

  Steps to reproduce
  ===
  $ wget 
https://cloud-images.ubuntu.com/daily/server/minimal/releases/bionic/release/ubuntu-18.04-minimal-cloudimg-amd64.img
  $ multipass launch file:///$(pwd)/ubuntu-18.04-minimal-cloudimg-amd64.img 
--name=bionic-minimal
  $ multipass exec bionic-minimal -- sudo systemctl list-units --failed 
--no-legend
  # note that cloud-config.service fails
  $ multipass exec bionic-minimal -- sudo cat /var/log/cloud-init.log | grep 
timezone

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1888298/+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 1827021] Re: SSH Documentation should mention "Host Key"

2020-01-14 Thread Joshua Powers
This was merged as is live, so marking fix released.

** Changed in: cloud-init
   Status: Triaged => 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/1827021

Title:
  SSH Documentation should mention "Host Key"

Status in cloud-init:
  Fix Released

Bug description:
  The documentation for the SSH module should mention that it is working
  with SSH *Host* Keys, since many people will commonly understand the
  term "SSH Key" to mean a key being used for User Authentication. This
  is somewhat ambiguous, I ended up building my own solution to replace
  host keys.

  The wording could be:
  Summary: configure ssh and ssh host keys

  This module handles most configuration for ssh and ssh host keys. Many
  images have default ssh host keys, which can be removed using
  ssh_deletekeys. This prevents re-use of a private key from an image on
  multiple machines. Since removing default keys is usually the desired
  behavior this option is enabled by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1827021/+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 1856352] [NEW] cloud-id: add re-run option

2019-12-13 Thread Joshua Powers
Public bug reported:

There are times where a user, or more likely a developer, wants to re-
run cloud-id from scratch. Rather than needing to run a number of
different options, we should give a shortcut. Something like:

$ cloud-id --force

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1856352

Title:
  cloud-id: add re-run option

Status in cloud-init:
  New

Bug description:
  There are times where a user, or more likely a developer, wants to re-
  run cloud-id from scratch. Rather than needing to run a number of
  different options, we should give a shortcut. Something like:

  $ cloud-id --force

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1856352/+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 1856353] [NEW] cloud-id: add debug option

2019-12-13 Thread Joshua Powers
Public bug reported:

There are times where a user, or more likely a developer, needs to
understand why the platform was chosen or their platform was missed by
ds-identify. Currently we give them a lengthy command that is not easily
discovered. Giving a simple command would be much easier:

$ cloud-id --debug

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1856353

Title:
  cloud-id: add debug option

Status in cloud-init:
  New

Bug description:
  There are times where a user, or more likely a developer, needs to
  understand why the platform was chosen or their platform was missed by
  ds-identify. Currently we give them a lengthy command that is not
  easily discovered. Giving a simple command would be much easier:

  $ cloud-id --debug

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1856353/+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 1856096] [NEW] unittest failure on LXD: no such file or dir: 'ud'

2019-12-11 Thread Joshua Powers
Public bug reported:

When building master on LXD or running tox on a fresh Bionic LXD the
following test failures show up:

https://paste.ubuntu.com/p/5p8cfjFN8D/

This is not reproduced on a VM or baremetal.

This is slightly confusing as the load_file function has not be touched
since in multiple years, nor as the query cmd. Is this related to the
SRU lxd issues?

Steps to reproduce
---
lxc launch ubuntu-daily:b b
lxc exec b bash
git clone https://github.com/canonical/cloud-init
cd cloud-init
sudo apt update -qq
sudo apt install tox -y
tox

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Summary changed:

- test escape on LXD: no such file or dir: 'ud'
+ unittest failure on LXD: no such file or dir: 'ud'

-- 
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/1856096

Title:
  unittest failure on LXD: no such file or dir: 'ud'

Status in cloud-init:
  New

Bug description:
  When building master on LXD or running tox on a fresh Bionic LXD the
  following test failures show up:

  https://paste.ubuntu.com/p/5p8cfjFN8D/

  This is not reproduced on a VM or baremetal.

  This is slightly confusing as the load_file function has not be
  touched since in multiple years, nor as the query cmd. Is this related
  to the SRU lxd issues?

  Steps to reproduce
  ---
  lxc launch ubuntu-daily:b b
  lxc exec b bash
  git clone https://github.com/canonical/cloud-init
  cd cloud-init
  sudo apt update -qq
  sudo apt install tox -y
  tox

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1856096/+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 1734167] Re: DNS doesn't work in no-cloud as launched by ubuntu

2019-10-25 Thread Joshua Powers
** Changed in: cloud-init
   Status: Confirmed => Fix Released

** Changed in: cloud-init (Ubuntu Artful)
   Status: Confirmed => Won't Fix

-- 
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/1734167

Title:
  DNS doesn't work in no-cloud as launched by ubuntu

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * resolved does not start early enough in the boot-process preventing
  DNS resolution to be operational during early boot, for example as
  required by special early stages of cloud-init, resulting in failure
  to boot / provision the instance fully.

  [Test Case]

   * Boot container or a VM with a nocloud-net data source, and a URL pointing 
to the datasource as explained below
   * Observe that boot completes and provisioning is successful
   * Check that there are no dns-resolution errors in the cloud-init log / boot 
log

  [Regression Potential]

   * starting resolved earlier may prevent it from connecting to dbus,
  and may require a restart later on when re-triggered over dbus. This
  is on artful only, as in bionic resolved has gained ability to
  reconnected to dbus post-start. Backporting that, however, is too
  large for an SRU as it requires sd-bus changes.

  [Other Info]
   
   * Original bug report.

  I use no-cloud to test the kernel in CI (I am maintainer of the bcache
  subsystem), and have been running it successfully under 16.04 cloud
  images from qemu, using a qemu command that includes:

  -smbios "type=1,serial=ds=nocloud-
  net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-
  metadata/linuxtst/"

  As documented here:

  http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html

  Under the new 17.10 cloud images, this doesn't work: the network comes
  up, but name resolution doesn't work-- /etc/resolv.conf is a symlink
  to a nonexistent file at this point of the boot and systemd-resolved
  is not running.  When I manually hack /etc/resolv.conf in the cloud
  image to point to 4.2.2.1 it works fine.

  I don't know if nameservice not working is by design, but it seems
  like it should work.  The documentation states:

  "With ds=nocloud-net, the seedfrom value must start with http://,
  https:// or ftp://";

  And https is not going to work for a raw IP address.

  Related bugs:
   * bug 1734939: #include fails silently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1734167/+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 1823381] [NEW] Enable log rotation

2019-04-05 Thread Joshua Powers
Public bug reported:

As reported on the Debian cloud mailing list [1] we should consider
enabling or including a log rotation script.

[1] https://lists.debian.org/debian-cloud/2019/04/msg00022.html

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1823381

Title:
  Enable log rotation

Status in cloud-init:
  New

Bug description:
  As reported on the Debian cloud mailing list [1] we should consider
  enabling or including a log rotation script.

  [1] https://lists.debian.org/debian-cloud/2019/04/msg00022.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1823381/+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 1815051] Re: Bionic netplan render invalid yaml duplicate anchor declaration for nameserver entries

2019-03-20 Thread Joshua Powers
Marking all fixed-released and unsubscribing field-critical.

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

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

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

** Changed in: cloud-init (Ubuntu Cosmic)
   Status: Confirmed => 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/1815051

Title:
  Bionic netplan render invalid yaml duplicate anchor declaration for
  nameserver entries

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

Bug description:
  The netplan configuration redeclares the nameservers anchor for every
  single section (vlans, bonds), and use the same id for similar entries
  (id001).

  In this specific case the network configuration in maas have a bond0
  with two vlans, bond0.3502 and bond0.3503, and an untagged bond1
  without vlans. The rendered 50-cloud-init.yaml looks like this:

  network:
  version: 2
  ethernets:
  ...
  bonds:
  ...
  bond1:
  ...
  nameservers: &id001 <- anchor declaration here
  addresses:
  - 255.255.255.1
  - 255.255.255.2
  - 255.255.255.3
  - 255.255.255.5
  search:
  - customer.domain
  - maas
  ...
  bondM:
  ...
  nameservers: *id001

 vlans:
  bond0.3502:
  ...
  nameservers: &id001 <- anchor redeclaration here
  addresses:
  - 255.255.255.1
  - 255.255.255.2
  - 255.255.255.3
  - 255.255.255.5
  search:
  - customer.domain
  - maas
  bond0.3503:
  ...
  nameservers: *id001

  As the cloudinit renders an invalid yaml file, the netplan apply
  produces the following error: (due to the anchor redeclaration in the
  vlans section):

 Invalid YAML at /etc/netplan/50-cloud-init.yaml line 118 column 25:
  second occurence

  This render bug prevents us using the untagged bond and the bond with
  the vlans in the same configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1815051/+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 1816627] Re: test

2019-02-19 Thread Joshua Powers
** Changed in: cloud-init
   Status: New => Invalid

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

** Changed in: cloud-init (Ubuntu Disco)
   Status: New => Invalid

-- 
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/1816627

Title:
  test

Status in cloud-init:
  Invalid
Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-init source package in Xenial:
  Invalid
Status in cloud-init source package in Disco:
  Invalid

Bug description:
  test

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1816627/+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 1816627] [NEW] test

2019-02-19 Thread Joshua Powers
Public bug reported:

test

** Affects: cloud-init
 Importance: Undecided
 Status: Invalid

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: cloud-init (Ubuntu Xenial)
 Importance: Undecided
 Status: Invalid

** Affects: cloud-init (Ubuntu Disco)
 Importance: Undecided
 Status: Invalid

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

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

-- 
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/1816627

Title:
  test

Status in cloud-init:
  Invalid
Status in cloud-init package in Ubuntu:
  Invalid
Status in cloud-init source package in Xenial:
  Invalid
Status in cloud-init source package in Disco:
  Invalid

Bug description:
  test

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1816627/+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 1758409] [NEW] integration tests: restructure ssh timeout

2018-03-23 Thread Joshua Powers
Public bug reported:

# Summary
During the integration tests, currently if SSH to instance times out it holds 
up testing for over an hour in an attempt to SSH to an instance; note the 
timestamp jump on: https://paste.ubuntu.com/p/NBQKwm9wdG/

The _ssh_connect function was originally written for the nocloud_kvm
platform and used as a method for determining if an instance was up and
accessible. As such, the function is doing double duty and not correctly
focused on SSH'ing to an up and running instance and has a bug in it as
it is waiting far too long.

# Action plan

1. For the nocloud_kvm platform when when starting and before
_wait_for_system, there should be a check if an instance is accessible
during the is_running check. This could be done again by SSH with a
number of retries, but should be taken care of inside the nocloud_kvm
platform itself and not in the SSH connect function.

2. Update the _ssh_connect to timeout quickly, reduce wait on banner,
and only retry up to 3 times.

# Noted Files
tests/cloud_tests/platforms/platforms.py:_ssh_connect()
tests/cloud_tests/platforms/nocloudkvm/instance.py:start()

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1758409

Title:
  integration tests: restructure ssh timeout

Status in cloud-init:
  New

Bug description:
  # Summary
  During the integration tests, currently if SSH to instance times out it holds 
up testing for over an hour in an attempt to SSH to an instance; note the 
timestamp jump on: https://paste.ubuntu.com/p/NBQKwm9wdG/

  The _ssh_connect function was originally written for the nocloud_kvm
  platform and used as a method for determining if an instance was up
  and accessible. As such, the function is doing double duty and not
  correctly focused on SSH'ing to an up and running instance and has a
  bug in it as it is waiting far too long.

  # Action plan

  1. For the nocloud_kvm platform when when starting and before
  _wait_for_system, there should be a check if an instance is accessible
  during the is_running check. This could be done again by SSH with a
  number of retries, but should be taken care of inside the nocloud_kvm
  platform itself and not in the SSH connect function.

  2. Update the _ssh_connect to timeout quickly, reduce wait on banner,
  and only retry up to 3 times.

  # Noted Files
  tests/cloud_tests/platforms/platforms.py:_ssh_connect()
  tests/cloud_tests/platforms/nocloudkvm/instance.py:start()

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1758409/+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 1745663] [NEW] tests: lxd console code breaks when using lxd as snap

2018-01-26 Thread Joshua Powers
Public bug reported:

Running the integration tests using the lxd backend fails when lxd is installed 
as a snap:
https://paste.ubuntu.com/26465769/

The failure is a result of the
tests/cloud_tests/platforms/lxd.py:_setup_console_log() function
attempting to modify the configuration:

49 cfg = "lxc.console.logfile=%s" % logf
50 orig = self._pylxd_container.config.get('raw.lxc', "")
51 if orig:
52 orig += "\n"
53 self._pylxd_container.config['raw.lxc'] = orig + cfg

LXD logs: https://paste.ubuntu.com/26465860/
My lxd setup/config: https://paste.ubuntu.com/26465838/

The specific issue I believe is that LXD as a snap is confined and does
not have access to /tmp (need to confirm this) hence the error message:

console.c:lxc_console_create:561 - No such file or directory - failed to
open console log file "/tmp/LXDInstance-cloud-test-ubuntu-xenial-image-
modification-em88d5kzvxzdrzsgod029n8iztb/console.log"

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Description changed:

  Running the integration tests using the lxd backend fails when lxd is 
installed as a snap:
  https://paste.ubuntu.com/26465769/
  
  The failure is a result of the
  tests/cloud_tests/platforms/lxd.py:_setup_console_log() function
  attempting to modify the configuration:
  
  49 cfg = "lxc.console.logfile=%s" % logf
  50 orig = self._pylxd_container.config.get('raw.lxc', "")
  51 if orig:
  52 orig += "\n"
  53 self._pylxd_container.config['raw.lxc'] = orig + cfg
  
  LXD logs: https://paste.ubuntu.com/26465860/
  My lxd setup/config: https://paste.ubuntu.com/26465838/
  
  The specific issue I believe is that LXD as a snap is confined and does
- not have access to /tmp hence the error message:
+ not have access to /tmp (need to confirm this) hence the error message:
  
  console.c:lxc_console_create:561 - No such file or directory - failed to
  open console log file "/tmp/LXDInstance-cloud-test-ubuntu-xenial-image-
  modification-em88d5kzvxzdrzsgod029n8iztb/console.log"

-- 
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/1745663

Title:
  tests: lxd console code breaks when using lxd as snap

Status in cloud-init:
  New

Bug description:
  Running the integration tests using the lxd backend fails when lxd is 
installed as a snap:
  https://paste.ubuntu.com/26465769/

  The failure is a result of the
  tests/cloud_tests/platforms/lxd.py:_setup_console_log() function
  attempting to modify the configuration:

  49 cfg = "lxc.console.logfile=%s" % logf
  50 orig = self._pylxd_container.config.get('raw.lxc', "")
  51 if orig:
  52 orig += "\n"
  53 self._pylxd_container.config['raw.lxc'] = orig + cfg

  LXD logs: https://paste.ubuntu.com/26465860/
  My lxd setup/config: https://paste.ubuntu.com/26465838/

  The specific issue I believe is that LXD as a snap is confined and
  does not have access to /tmp (need to confirm this) hence the error
  message:

  console.c:lxc_console_create:561 - No such file or directory - failed
  to open console log file "/tmp/LXDInstance-cloud-test-ubuntu-xenial-
  image-modification-em88d5kzvxzdrzsgod029n8iztb/console.log"

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1745663/+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 1724951] Re: Ntp schema definition permits empty ntp cloud-config, but code disallows

2017-10-24 Thread Joshua Powers
** Also affects: cloud-init (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

-- 
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/1724951

Title:
  Ntp schema definition permits empty ntp cloud-config, but code
  disallows

Status in cloud-init:
  In Progress
Status in cloud-init package in Ubuntu:
  New
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

Bug description:
  http://pad.lv/1724951
  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1724951

  === Begin SRU Template ===
  [Impact]
  Customers who provide the following cloud-config will get a Runtime error
  #cloud-config
  ntp:

  The expected behavior, per docs, is that an empty ntp configuration will 
result in
  "4 pools will be used in the format {0-3}.{distro}.pool.ntp.org.".

  [Test Case]

  
  if [ ! -f './lxc-proposed-snapshot' ]; then
    wget 
https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot;
    chmod 755 lxc-proposed-snapshot;
  fi

  # 1. Provide a empty ntp configuration to cloud-init
  cat > install-ntp.conf 

[Yahoo-eng-team] [Bug 1718681] Re: Package copyright file omits Apache 2 license

2017-09-21 Thread Joshua Powers
** Changed in: cloud-init
   Status: New => Confirmed

** Changed in: cloud-init
   Importance: Undecided => High

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

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

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

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

** Changed in: cloud-init
   Status: Confirmed => Invalid

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

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

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

-- 
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/1718681

Title:
  Package copyright file omits Apache 2 license

Status in cloud-init:
  Invalid
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Confirmed

Bug description:
  In the Ubuntu package source, packages/debian/copyright says the
  License is either GPL-3 or Apache 2.0 and includes summaries of both
  licenses with links to the full license texts.

  debian/copyright says that the license is either GPL-3 or Apache 2.0,
  but only includes the GPL-3 summary and link (together with the MIT
  licence terms for cloudinit/boto_utils.py)

  I believe the terms of the Apache licence and the terms the LICENSE
  file require the inclusion of the Apache 2 summary and link in the
  debian/copyright file.

  cloud-init.tar is not relevant to this issue.

  Seen on Azure
  $ dpkg-query -W -f='${Version}' cloud-init
  0.7.9-233-ge586fe35-0ubuntu1~16.04.1
  $ cat /usr/share/doc/cloud-init/copyright 
  Format-Specification: 
http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=file&rev=135
  Name: cloud-init
  Maintainer: Scott Moser 
  Source: https://launchpad.net/cloud-init

  This package was debianized by Soren Hansen  on
  Thu, 04 Sep 2008 12:49:15 +0200 as ec2-init.  It was later renamed to
  cloud-utils by Scott Moser 

  Upstream Author: Scott Moser 
  Soren Hansen 
  Chuck Short 

  Copyright: 2010, Canonical Ltd.
  License: GPL-3 or Apache-2.0
   This program is free software: you can redistribute it and/or modify
   it under the terms of the GNU General Public License version 3, as
   published by the Free Software Foundation.

   This program is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   GNU General Public License for more details.

   You should have received a copy of the GNU General Public License
   along with this program.  If not, see .

   The complete text of the GPL version 3 can be seen in
   /usr/share/common-licenses/GPL-3.

  Files: cloudinit/boto_utils.py
  Copyright: 2006,2007, Mitch Garnaat http://garnaat.org/
  License: MIT
   Permission is hereby granted, free of charge, to any person obtaining a
   copy of this software and associated documentation files (the
   "Software"), to deal in the Software without restriction, including
   without limitation the rights to use, copy, modify, merge, publish, dis-
   tribute, sublicense, and/or sell copies of the Software, and to permit
   persons to whom the Software is furnished to do so, subject to the fol-
   lowing conditions:

   The above copyright notice and this permission notice shall be included
   in all copies or substantial portions of the Software.

   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
   OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABIL-
   ITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
   SHALL THE AUTHOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
   WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
   OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
   IN THE SOFTWARE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1718681/+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 1257435] Re: Chef does not run with all install types

2017-09-11 Thread Joshua Powers
Per the last comment, I am marking this fix released. If you are still
having issues, make sure you are using the latest version of cloud-init
and if so please file a new bug with details on the latest failure.

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

** Changed in: cloud-init
   Status: New => 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/1257435

Title:
  Chef does not run with all install types

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  When using #cloud-config and a chef directive, the initial `chef-
  client` run only happens when install_type is set to "gems".

  Expected behavior: No matter the install_type, an initial `chef-
  client` run will execute.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cloud-init 0.7.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Dec  3 13:04:27 2013
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1257435/+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 1177432] Re: [SRU] cloud-init archive template should match Ubuntu Server

2017-09-11 Thread Joshua Powers
** Changed in: cloud-init
   Status: New => 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/1177432

Title:
  [SRU] cloud-init archive template should match Ubuntu Server

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Precise:
  Fix Released
Status in cloud-init source package in Trusty:
  Fix Released
Status in cloud-init source package in Vivid:
  Fix Released
Status in cloud-init source package in Wily:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification]
  Ubuntu Cloud Images are inconsistent with desktop and bare-metal server 
installations since backports, restricted and multiverse are not enabled. This 
is effected via cloud-init that uses a template to select an in-cloud archive.

  [FIX] Make the cloud-init template match that of Ubuntu-server.

  [REGRESION] The potential for regression is low. However, all users
  will experience slower fetch times on apt-get updates especially on
  slower or high latency networks.

  [TEST]
  1. Build image from -proposed
  2. Boot up image
  3. Confirm that "sudo apt-get update" pulls in backports, restricted and 
multiverse.

  Backports are currently not enabled in the cloud-init template. This
  is needed in order to get the backport kernels on cloud images.

  Related bugs:
   * bug 997371:  Create command to add "multiverse" and "-backports" to apt 
sources
   * bug 1513529:  cloud image built-in /etc/apt/sources.list needs updating

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1177432/+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 1714376] [NEW] unittests: OpenStack DS escape or timeout

2017-08-31 Thread Joshua Powers
Public bug reported:

Similar to LP: #1714117, there appears to be a pair of tests that are
escaping and timing out, resulting in extra time that is not required
for the unit tests:

tests.unittests.test_datasource.test_openstack.TestOpenStackDataSource.test_datasource
tests.unittests.test_datasource.test_openstack.TestOpenStackDataSource.test_bad_datasource_meta

Here are the raw results and methodology:
Python 2 results: https://paste.ubuntu.com/25441590/
Python 3 results: https://paste.ubuntu.com/25441592/

$ git clone https://git.launchpad.net/cloud-init
$ cd cloud-init
# pip[3] install --user -r requirements.txt -r test-requirements.txt nose-timer
$ python[3] -m nose --with-timer --timer-ok 1 --timer-warning 1 --timer-top-n 
10 tests/unittests

** Affects: cloud-init
 Importance: Undecided
 Status: Confirmed

** Changed in: cloud-init
   Status: New => Confirmed

-- 
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/1714376

Title:
  unittests: OpenStack DS escape or timeout

Status in cloud-init:
  Confirmed

Bug description:
  Similar to LP: #1714117, there appears to be a pair of tests that are
  escaping and timing out, resulting in extra time that is not required
  for the unit tests:

  
tests.unittests.test_datasource.test_openstack.TestOpenStackDataSource.test_datasource
  
tests.unittests.test_datasource.test_openstack.TestOpenStackDataSource.test_bad_datasource_meta

  Here are the raw results and methodology:
  Python 2 results: https://paste.ubuntu.com/25441590/
  Python 3 results: https://paste.ubuntu.com/25441592/

  $ git clone https://git.launchpad.net/cloud-init
  $ cd cloud-init
  # pip[3] install --user -r requirements.txt -r test-requirements.txt 
nose-timer
  $ python[3] -m nose --with-timer --timer-ok 1 --timer-warning 1 --timer-top-n 
10 tests/unittests

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1714376/+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 1714117] [NEW] tox: long CI times

2017-08-30 Thread Joshua Powers
Public bug reported:

On Aug 10, 2017 the nightly and CI tests began taking 20 additional
minutes. The additional time is occurring during the tox run,
specifically during the 'py27' and 'xenial' environments. Here are
comparisons of run times:

Aug 8: 1 min 52 seconds
Aug 9: 1 min 47 seconds
Aug 10: 19 mins

These tests are run at ~23:40 UTC each day, therefore a change would
have occurred during the day resulting in the end-of-day run to see the
effect.

>From the Aug 10 run these two tox environments are adding a huge amount of 
>time:
py27: Ran 980 tests in 525.871s
xenial: Ran 980 tests in 518.678s

Here are timing results from the Aug 9 run:
py27: Ran 978 tests in 9.051s
xenial: Ran 978 tests in 14.122s

Per the git log I believe it is tied to this revision:
https://git.launchpad.net/cloud-init/commit/?id=d5f855dd96ccbea77f61b0515b574ad2c43d116d

Which added two new tests:
test_ec2_local_returns_false_on_bsd
test_ec2_local_performs_dhcp_on_non_bsd
hence the increase the number of tests run. I am not however, saying that these 
two tests are the cause of the additional test time.

** Affects: cloud-init
 Importance: Undecided
 Status: Confirmed

** Changed in: cloud-init
   Status: New => Confirmed

-- 
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/1714117

Title:
  tox: long CI times

Status in cloud-init:
  Confirmed

Bug description:
  On Aug 10, 2017 the nightly and CI tests began taking 20 additional
  minutes. The additional time is occurring during the tox run,
  specifically during the 'py27' and 'xenial' environments. Here are
  comparisons of run times:

  Aug 8: 1 min 52 seconds
  Aug 9: 1 min 47 seconds
  Aug 10: 19 mins

  These tests are run at ~23:40 UTC each day, therefore a change would
  have occurred during the day resulting in the end-of-day run to see
  the effect.

  From the Aug 10 run these two tox environments are adding a huge amount of 
time:
  py27: Ran 980 tests in 525.871s
  xenial: Ran 980 tests in 518.678s

  Here are timing results from the Aug 9 run:
  py27: Ran 978 tests in 9.051s
  xenial: Ran 978 tests in 14.122s

  Per the git log I believe it is tied to this revision:
  
https://git.launchpad.net/cloud-init/commit/?id=d5f855dd96ccbea77f61b0515b574ad2c43d116d

  Which added two new tests:
  test_ec2_local_returns_false_on_bsd
  test_ec2_local_performs_dhcp_on_non_bsd
  hence the increase the number of tests run. I am not however, saying that 
these two tests are the cause of the additional test time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1714117/+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 1648645] Re: Cannot specify version of salt-minion

2017-08-25 Thread Joshua Powers
Hey thanks for following up! Sorry about the original delay in getting
back to you, but I appreciate you letting us know your change.

If you wanted to, you could contribute to the salt module to allow for a
version from a specific URL or apt repo, but the solution you came up
with works as well!

** Changed in: cloud-init
   Status: Incomplete => Invalid

-- 
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/1648645

Title:
  Cannot specify version of salt-minion

Status in cloud-init:
  Invalid

Bug description:
  When installing salt-minion via cloud-init it always installs the
  latest version, providing no way to specify a specific version of the
  package.

  The file https://git.launchpad.net/cloud-
  init/tree/cloudinit/config/cc_salt_minion.py installs the package and
  this can't even be overridden using the arbitrary package install
  (packages property).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1648645/+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 1588041] Re: [2.0 rc1] juju can't access vSphere VM deployed with Xenial, cloud-init fails to set SSH keys

2017-08-25 Thread Joshua Powers
** Changed in: cloud-init
   Status: New => 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/1588041

Title:
  [2.0 rc1] juju can't access vSphere VM deployed with Xenial,  cloud-
  init fails to set SSH keys

Status in cloud-init:
  Fix Released
Status in juju:
  Fix Released

Bug description:
  I tried to do a bootstrap with vsphere as a provider using vsphere 6.0 and 
juju 1.25.5.
  -
    vsphere:
  type: vsphere
  host: '**.***.*.***'
  user: 'administra...@vsphere.oil'
  password: '**'
  datacenter: 'dc0'
  bootstrap-timeout: 1800
  logging-config: 
"=DEBUG;juju=DEBUG;golxc=TRACE;juju.container.lxc=TRACE"
  agent-stream: released
  -

  Initially, I did not specify the default series and bootstrap VM
  deployed with Xenial, however, juju  could not connect to it after
  getting the address and seems stuck trying to connect and I had to
  CTRL-C:

  -
  $ juju bootstrap -e vsphere
  ERROR the "vsphere" provider is provisional in this version of Juju. To use 
it anyway, set JUJU_DEV_FEATURE_FLAGS="vsphere-provider" in your shell 
environment
  $ export JUJU_DEV_FEATURE_FLAGS="vsphere-provider"
  $ juju bootstrap -e vsphere
  Bootstrapping environment "vsphere"
  Starting new instance for initial state server
  Launching instance
   - juju-e33e5800-edd9-4af7-8654-6d59b1e98eb9-machine-0
  Installing Juju agent on bootstrap instance
  Waiting for address
  Attempting to connect to 10.245.39.94:22
  Attempting to connect to fe80::250:56ff:fead:1b03:22
  ^CInterrupt signalled: waiting for bootstrap to exit
  ERROR failed to bootstrap environment: interrupted
  -

  When I specified the default series to be trusty, it worked:
  -
    vsphere:
  type: vsphere
  host: '**.***.*.***'
  user: 'administra...@vsphere.oil'
  password: '**'
  datacenter: 'dc0'
  default-series: trusty
  bootstrap-timeout: 1800
  logging-config: 
"=DEBUG;juju=DEBUG;golxc=TRACE;juju.container.lxc=TRACE"
  agent-stream: released
  -

  This was the output:

  -
  $ juju bootstrap -e vsphere
  Bootstrapping environment "vsphere"
  Starting new instance for initial state server
  Launching instance
   - juju-b157863b-3ed4-4ae5-8c3c-82ae7629bff7-machine-0
  Installing Juju agent on bootstrap instance
  Waiting for address
  Attempting to connect to 10.245.45.153:22
  Attempting to connect to fe80::250:56ff:fead:3fa2:22
  Warning: Permanently added '10.245.45.153' (ECDSA) to the list of known hosts.
  sudo: unable to resolve host ubuntuguest
  Logging to /var/log/cloud-init-output.log on remote host
  Running apt-get update
  Running apt-get upgrade
  Installing package: curl
  Installing package: cpu-checker
  Installing package: bridge-utils
  Installing package: rsyslog-gnutls
  Installing package: cloud-utils
  Installing package: cloud-image-utils
  Installing package: tmux
  Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP 
%{http_code}; time %{time_total}s; size %{size_download} bytes; speed 
%{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz 
<[https://streams.canonical.com/juju/tools/agent/1.25.5/juju-1.25.5-trusty-amd64.tgz]>
  Bootstrapping Juju machine agent
  Starting Juju machine agent (jujud-machine-0)
  Bootstrap agent installed
  vsphere -> vsphere
  Waiting for API to become available
  Waiting for API to become available
  Waiting for API to become available
  Waiting for API to become available
  Bootstrap complete
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1588041/+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 1411829] Re: CentOS 7 should be treated like RHEL 7 in dist/rhel.py

2017-08-25 Thread Joshua Powers
I believe this should be marked as fixed as the uses_systemd function
was updated previous:

https://github.com/cloud-init/cloud-
init/blob/master/cloudinit/distros/__init__.py#L100


** Changed in: cloud-init
   Status: New => 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/1411829

Title:
  CentOS 7 should be treated like RHEL 7 in dist/rhel.py

Status in cloud-init:
  Fix Released

Bug description:
  cloudinit/dists/rhel.py contains the follow code to determine if
  systemd is in use:

  def uses_systemd(self):
  # Fedora 18 and RHEL 7 were the first adopters in their series
  (dist, vers) = util.system_info()['dist'][:2]
  major = (int)(vers.split('.')[0])
  return ((dist.startswith('Red Hat Enterprise Linux') and major >= 7)
  or (dist.startswith('Fedora') and major >= 18))

  
  This will not produce the correct behavior on CentOS 7, Scientific LInux 7, 
or any other RHEL-based distribution.  Among other issues, this will prevent 
cloud-init from setting the system hostname correctly.  Because these 
distributions are treated like RHEL6 and earlier, cloud-init writes the 
persistent hostname into /etc/sysconfig/network, but the hostname is not read 
from this file when the system boots.

  I propose that we replace uses_systemd with the following:

  def uses_systemd(self):
  return os.path.isfile('/usr/bin/systemctl')

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1411829/+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 1249125] Re: smartos datasource should use meta-data for server identification

2017-08-25 Thread Joshua Powers
Per the docs, you are to use "sdc:uuid" which does appear to be in the
SmartOS handler. There are two change log entries for similar work:

Update SmartOS data source to use v2 metadata.
Convert DataSourceSmartOS to use v2 metadata.

I believe this is fixed, so I am marking, fix released. If you disagree
or have additional details on work required, please reply saying so.

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

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

Title:
  smartos datasource should use meta-data for server identification

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  New SmartOS documentation shows that the instance ID should be
  detected through the meta-data.

  http://us-east.manta.joyent.com/jmc/public/mdata/index.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1249125/+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 1643041] Re: snappy module does not install snaps

2017-08-25 Thread Joshua Powers
** Changed in: cloud-init
   Status: New => Invalid

-- 
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/1643041

Title:
  snappy module does not install snaps

Status in cloud-init:
  Invalid

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup snappy to 
install hello-world does not work.

  [cloud-config]
  #cloud-config
  snappy:
system_snappy: yes (or auto)
packages: [hello-world]

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
  cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  snappy is installed, however, `snap list` returns no snaps installed.

  [expected result]
  I would have expected the "hello-world" snap to be installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643041/+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 1643022] Re: landscape module does not work

2017-08-25 Thread Joshua Powers
** Changed in: cloud-init
   Status: New => Invalid

-- 
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/1643022

Title:
  landscape module does not work

Status in cloud-init:
  Invalid

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup landscape does 
not install the landscape-client or set up the config and has no error message.

  [cloud-config]
  #cloud-conifg
  landscape:
client:
  log_level: "info"
  url: "https://landscape.canonical.com/message-system";
  ping_url: "http://landscape.canonical.com/ping";
  data_path: "/var/lib/landscape/client"
  http_proxy: "http://my.proxy.com/foobar";
  https_proxy: "https://my.proxy.com/foobar";
  tags: "server,cloud"
  computer_title: "footitle"
  registration_key: "fookey"
  account_name: "fooaccount"

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
  cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  root@xenial-lxd:/var/log# cat cloud-init.log  | grep landscape
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] stages.py[DEBUG]: Running module 
landscape () with 
frequency once-per-instance
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: start: 
modules-final/config-landscape: running config-landscape with frequency 
once-per-instance
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/xenial-lxd/sem/config_landscape - wb: [420] 24 bytes
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] helpers.py[DEBUG]: Running 
config-landscape using lock ()
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: finish: 
modules-final/config-landscape: SUCCESS: config-landscape ran successfully

  [expected result]
  I would have expected landscape-client to get installed and the configuration 
file to be written.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643022/+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 1551747] Re: ubuntu-fan causes issues during network configuration

2017-07-28 Thread Joshua Powers
** Changed in: cloud-init
   Status: New => Invalid

-- 
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/1551747

Title:
  ubuntu-fan causes issues during network configuration

Status in cloud-init:
  Invalid
Status in Snappy:
  Confirmed
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Yakkety:
  Fix Released

Bug description:
  it seems that ubuntu-fan is causing issues with network configuration.

  On 16.04 daily image:

  root@localhost:~# snappy list
  NameDate   Version  Developer
  canonical-pi2   2016-02-02 3.0  canonical
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical
  ubuntu-core 2016-02-22 16.04.0-10.armhf canonical

  I see this when I'm activating a wifi card on a raspberry pi 2.

  root@localhost:~# ifdown wlan0
  ifdown: interface wlan0 not configured
  root@localhost:~# ifup wlan0
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   Socket/fallback
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e)
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e)
  DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 
(xid=0x5ec9c081)
  DHCPOFFER of 192.168.0.170 from 192.168.0.251
  DHCPACK of 192.168.0.170 from 192.168.0.251
  RTNETLINK answers: File exists
  bound to 192.168.0.170 -- renewal in 17145 seconds.
  run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1
  Failed to bring up wlan0.

  ===
  [Impact]

  Installing ubuntu-fan can trigger error messages when initialising
  with no fan configuration.

  [Test Case]

  As above.

  [Regression Potential]

  Low, suppresses errorneous error messages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1551747/+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 1585193] Re: walinuxagent not found on Centos when cloud-init is started

2017-07-28 Thread Joshua Powers
Marking invalid per comment above.

** Changed in: cloud-init
   Status: New => Invalid

-- 
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/1585193

Title:
  walinuxagent not found on Centos when cloud-init is started

Status in cloud-init:
  Invalid

Bug description:
  Hello,

  I'm trying to use cloud-init on Centos and Azure, but the the Azure
  agent has a different name (waagent instead of walinuxagent) from
  Ubuntu and it is hardcoded in the source code. Do you plan to make a
  condition for RHEL distro ?

  Here is the python stack :

  May 24 14:22:50 test cloud-init: 2016-05-24 14:22:50,899 - util.py[DEBUG]: 
agent command '['service', 'walinuxagent', 'start']' failed.
  May 24 14:22:50 test cloud-init: Traceback (most recent call last):
  May 24 14:22:50 test cloud-init: File 
"/usr/lib/python2.7/site-packages/cloudinit/sources/DataSourceAzure.py", line 
166, in get_data
  May 24 14:22:50 test cloud-init: invoke_agent(mycfg['agent_command'])
  May 24 14:22:50 test cloud-init: File 
"/usr/lib/python2.7/site-packages/cloudinit/sources/DataSourceAzure.py", line 
400, in invoke_agent
  May 24 14:22:50 test cloud-init: util.subp(cmd, shell=(not isinstance(cmd, 
list)))
  May 24 14:22:51 test cloud-init: File 
"/usr/lib/python2.7/site-packages/cloudinit/util.py", line 1539, in subp
  May 24 14:22:51 test cloud-init: cmd=args)
  May 24 14:22:51 test cloud-init: ProcessExecutionError: Unexpected error 
while running command.
  May 24 14:22:51 test cloud-init: Command: ['service', 'walinuxagent', 'start']
  May 24 14:22:51 test cloud-init: Exit code: 6
  May 24 14:22:51 test cloud-init: Reason: -
  May 24 14:22:51 test cloud-init: Stdout: ''
  May 24 14:22:51 test cloud-init: Stderr: 'Redirecting to /bin/systemctl start 
 walinuxagent.service\nFailed to start walinuxagent.service: Unit 
walinuxagent.service failed to load: No such file or directory.\n'

  Thanks.

  Best,
  Antoine Rouaze

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1585193/+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 1685831] Re: pylint: cloudinit.util 'closing' has no 'read' member

2017-07-27 Thread Joshua Powers
Fixed inside pylint and updated our version of pylint to grab fix:
https://git.launchpad.net/cloud-init/commit/?id=9c33cb24b8a834aa8034db4c989725901a0814c6

Pylint fix:
https://github.com/PyCQA/pylint/issues/1444

** Changed in: cloud-init
   Status: New => Invalid

** Changed in: cloud-init
   Status: Invalid => Fix Committed

** Bug watch added: github.com/PyCQA/pylint/issues #1444
   https://github.com/PyCQA/pylint/issues/1444

-- 
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/1685831

Title:
  pylint: cloudinit.util 'closing' has no 'read' member

Status in cloud-init:
  Fix Committed

Bug description:
  Tip style checker [1] discovered the following errors, but I believe
  this is a false positive:

  * Module cloudinit.util
  cloudinit/util.py:480: [E1101(no-member), decomp_gzip] Instance of 'closing' 
has no 'read' member
  cloudinit/util.py:482: [E1101(no-member), decomp_gzip] Instance of 'closing' 
has no 'read' member

  Offending code [2] and upstream bug filed [3]

  [1] https://paste.ubuntu.com/24448453/
  [2] https://paste.ubuntu.com/24448487/
  [3] https://github.com/PyCQA/pylint/issues/1444

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1685831/+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 1703697] [NEW] tox fails under python 3.6

2017-07-11 Thread Joshua Powers
Public bug reported:

Steps to reproduce:
1. lxc launch ubuntu-daily:a a
2. lxc exec a bash
3. add-apt-repository ppa:canonical-foundations/python3.6-as-default -y
4. apt-get update
5. apt-get upgrade -y
6. apt-get install tox
6. git clone https://git.launchpad.net/cloud-init
7. cd cloud-init
8. tox

Expected results:
All tests pass

Actual results:
Numerous unittest failures, see:
http://paste.ubuntu.com/25071344/

There appear to be three types of errors:

9x jsonpatch issues related: http://paste.ubuntu.com/25071366/
2x unexpected None type: http://paste.ubuntu.com/25071385/
1x incorrect assert/mock(?) http://paste.ubuntu.com/25071375/

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1703697

Title:
  tox fails under python 3.6

Status in cloud-init:
  New

Bug description:
  Steps to reproduce:
  1. lxc launch ubuntu-daily:a a
  2. lxc exec a bash
  3. add-apt-repository ppa:canonical-foundations/python3.6-as-default -y
  4. apt-get update
  5. apt-get upgrade -y
  6. apt-get install tox
  6. git clone https://git.launchpad.net/cloud-init
  7. cd cloud-init
  8. tox

  Expected results:
  All tests pass

  Actual results:
  Numerous unittest failures, see:
  http://paste.ubuntu.com/25071344/

  There appear to be three types of errors:

  9x jsonpatch issues related: http://paste.ubuntu.com/25071366/
  2x unexpected None type: http://paste.ubuntu.com/25071385/
  1x incorrect assert/mock(?) http://paste.ubuntu.com/25071375/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1703697/+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 1702717] [NEW] test: keyid specified does not match ppa

2017-07-06 Thread Joshua Powers
Public bug reported:

The keyid specified for the modules/apt_configure_sources_keyserver
integration test does not match the repo that is imported:

#cloud-config
  apt:
source1:
  keyid: 0165013E
  keyserver: keyserver.ubuntu.com
  source: "deb http://ppa.launchpad.net/cloud-init-dev/test-archive/ubuntu 
$RELEASE main"

That keyid is for the curtin developers test-archive ppa and not the
cloud-init developer's test-archive ppa.

Expected result:
`apt-key list` should specify an entry for:
  Launchpad PPA for cloud init development team
  1FF0 D853 5EF7 E719 E5C8  1B9C 083D 06FB E4D3 04DF

Actual result:
  A curtin developers entry.

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1702717

Title:
  test: keyid specified does not match ppa

Status in cloud-init:
  New

Bug description:
  The keyid specified for the modules/apt_configure_sources_keyserver
  integration test does not match the repo that is imported:

  #cloud-config
apt:
  source1:
keyid: 0165013E
keyserver: keyserver.ubuntu.com
source: "deb 
http://ppa.launchpad.net/cloud-init-dev/test-archive/ubuntu $RELEASE main"

  That keyid is for the curtin developers test-archive ppa and not the
  cloud-init developer's test-archive ppa.

  Expected result:
  `apt-key list` should specify an entry for:
Launchpad PPA for cloud init development team
1FF0 D853 5EF7 E719 E5C8  1B9C 083D 06FB E4D3 04DF

  Actual result:
A curtin developers entry.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1702717/+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 1695918] [NEW] 'jsonschema' imported but unused

2017-06-05 Thread Joshua Powers
Public bug reported:

>From latest build tests:
tests/unittests/test_handler/test_handler_ntp.py:20: 'jsonschema' imported but 
unused
tests/unittests/test_handler/test_schema.py:16: 'jsonschema' imported but unused

Steps to reproduce:
# git clone master
# cd cloud-init
# tox -e tip-pyflakes

The offending code in both files is:
try:
import jsonschema  # NOQA
_missing_jsonschema_dep = False
except ImportError:
_missing_jsonschema_dep = True

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1695918

Title:
  'jsonschema' imported but unused

Status in cloud-init:
  New

Bug description:
  From latest build tests:
  tests/unittests/test_handler/test_handler_ntp.py:20: 'jsonschema' imported 
but unused
  tests/unittests/test_handler/test_schema.py:16: 'jsonschema' imported but 
unused

  Steps to reproduce:
  # git clone master
  # cd cloud-init
  # tox -e tip-pyflakes

  The offending code in both files is:
  try:
  import jsonschema  # NOQA
  _missing_jsonschema_dep = False
  except ImportError:
  _missing_jsonschema_dep = True

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1695918/+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 1695333] [NEW] snapcraft.yaml: classic snap should not have plugs

2017-06-02 Thread Joshua Powers
Public bug reported:

It has come to my attention when attempting to publish the cloud-init
snap that because it is a classic snap it should not actually have any
plugs. This is because as a classic snap it has access to the system by
default and does not require any additional access to be specified.

Failure text:
confinement 'classic' not allowed with plugs/slots 
lint-snap-v2_confinement_classic_with_interfaces
Refrence LP: #1655369

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1695333

Title:
  snapcraft.yaml: classic snap should not have plugs

Status in cloud-init:
  New

Bug description:
  It has come to my attention when attempting to publish the cloud-init
  snap that because it is a classic snap it should not actually have any
  plugs. This is because as a classic snap it has access to the system
  by default and does not require any additional access to be specified.

  Failure text:
  confinement 'classic' not allowed with plugs/slots 
lint-snap-v2_confinement_classic_with_interfaces
  Refrence LP: #1655369

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1695333/+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 1695322] [NEW] bddeb script fails to build source package

2017-06-02 Thread Joshua Powers
Public bug reported:

Using the packages bddeb script fails with the recent commits.

Steps to reproduce:
1. Checkout master
2. ./packages/bddeb -S

Results:
https://paste.ubuntu.com/24749957/

Expected results:
Builds with no issues

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1695322

Title:
  bddeb script fails to build source package

Status in cloud-init:
  New

Bug description:
  Using the packages bddeb script fails with the recent commits.

  Steps to reproduce:
  1. Checkout master
  2. ./packages/bddeb -S

  Results:
  https://paste.ubuntu.com/24749957/

  Expected results:
  Builds with no issues

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1695322/+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 1695325] [NEW] pylxd 2.2.3 broken with lxd 2.14

2017-06-02 Thread Joshua Powers
Public bug reported:

The cloud-init integration tests utilize pylxd to complete the
management of containers for testing. The test system auto updated to
lxd 2.14, but has an incompatibility with pylxd 2.2.3 due to a missing
attribute resulting in a stack trace from pylxd [1].

This has halted integration testing until:
1) Revert back from lxd 2.14
2) Fixed version of pylxd gets published and test systems are updated with it

The fix [2] was checked in a number of days ago to pylxd, but no new
release was published. There is a merge request [3] available to up the
version number, but still requires someone to publish it to pypi.

[1] https://paste.ubuntu.com/24750053/
[2] https://github.com/lxc/pylxd/pull/230
[3] https://github.com/lxc/pylxd/pull/233

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1695325

Title:
  pylxd 2.2.3 broken with lxd 2.14

Status in cloud-init:
  New

Bug description:
  The cloud-init integration tests utilize pylxd to complete the
  management of containers for testing. The test system auto updated to
  lxd 2.14, but has an incompatibility with pylxd 2.2.3 due to a missing
  attribute resulting in a stack trace from pylxd [1].

  This has halted integration testing until:
  1) Revert back from lxd 2.14
  2) Fixed version of pylxd gets published and test systems are updated with it

  The fix [2] was checked in a number of days ago to pylxd, but no new
  release was published. There is a merge request [3] available to up
  the version number, but still requires someone to publish it to pypi.

  [1] https://paste.ubuntu.com/24750053/
  [2] https://github.com/lxc/pylxd/pull/230
  [3] https://github.com/lxc/pylxd/pull/233

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1695325/+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 1695318] [NEW] centos 6/7 schema unittests failing

2017-06-02 Thread Joshua Powers
Public bug reported:

With the recent merge of the validation work the unit tests are now failing on 
the centos 6 and 7 platforms. Here are the test failures:
centos 6: https://paste.ubuntu.com/24749874/
centos 7: https://paste.ubuntu.com/24749876/

Steps to reproduce:
1. lxc launch images:centos/[6|7] c[6|7]
2. lxc exec c[6|7] bash
3. yum install epel-release -y
4. install dependencies
5. git clone https://git.launchpad.net/cloud-init 
6. cd cloud-init
7. nosetests tests/unittests

Expected behavior:
Tests pass with no failures

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1695318

Title:
  centos 6/7 schema unittests failing

Status in cloud-init:
  New

Bug description:
  With the recent merge of the validation work the unit tests are now failing 
on the centos 6 and 7 platforms. Here are the test failures:
  centos 6: https://paste.ubuntu.com/24749874/
  centos 7: https://paste.ubuntu.com/24749876/

  Steps to reproduce:
  1. lxc launch images:centos/[6|7] c[6|7]
  2. lxc exec c[6|7] bash
  3. yum install epel-release -y
  4. install dependencies
  5. git clone https://git.launchpad.net/cloud-init 
  6. cd cloud-init
  7. nosetests tests/unittests

  Expected behavior:
  Tests pass with no failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1695318/+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 1692960] Re: tests: pycodestyle regression - expected 2 blank lines

2017-05-26 Thread Joshua Powers
Fixed in:
https://git.launchpad.net/cloud-init/commit/?id=2825a917e5fa130818c0d77219f32961b99a057f

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

** Changed in: cloud-init
   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/1692960

Title:
  tests: pycodestyle regression - expected 2 blank lines

Status in cloud-init:
  Fix Released

Bug description:
  On May 22, 2017 the cloud-init-style tip job that runs pycodestyle
  discovered a failure:

  cloudinit/sources/DataSourceAzure.py:167:1: E305 expected 2 blank
  lines after class or function definition, found 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1692960/+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 1693307] Re: tests: centos6 env failures

2017-05-26 Thread Joshua Powers
Fixed in:
https://git.launchpad.net/cloud-init/commit/?id=e5b2c011440aefe036c71a8c5e8ec547cc80f270

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

** Changed in: cloud-init
   Importance: Undecided => High

-- 
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/1693307

Title:
  tests: centos6 env failures

Status in cloud-init:
  Fix Released

Bug description:
  There are two current test failures on centos6 tox env.

  
  Steps to reproduce:
  0. lxc launch images:centos/6 c6
  1. lxc exec c6 bash
  2. yum install epel-release -y
  3. yum install git python-pip -y
  4. git clone master
  5. cd cloud-init
  6. tox -e centos6

  ==
  ERROR: Test read_user_data_callback() no files are found.
  --
  Traceback (most recent call last):
File "/root/cloud-init/tests/unittests/test_datasource/test_altcloud.py", 
line 422, in test_callback_none
  self.assertIsNone(dsac.read_user_data_callback(self.mount_dir))
  AttributeError: 'TestReadUserDataCallback' object has no attribute 
'assertIsNone'

  ==
  FAIL: test_scripts_shebanged 
(tests.unittests.test_datasource.test_smartos.TestSmartOSDataSource)
  --
  Traceback (most recent call last):
File "/root/cloud-init/tests/unittests/test_datasource/test_smartos.py", 
line 465, in test_scripts_shebanged
  self.assertEqual(shebang, "#!/bin/bash")
  AssertionError: '/bin/true' != '#!/bin/bash'
  - /bin/true
  + #!/bin/bash

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1693307/+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 1693307] [NEW] tests: centos6 env failures

2017-05-24 Thread Joshua Powers
Public bug reported:

There are two current test failures on centos6 tox env.


Steps to reproduce:
0. lxc launch images:centos/6 c6
1. lxc exec c6 bash
2. yum install epel-release -y
3. yum install git python-pip -y
4. git clone master
5. cd cloud-init
6. tox -e centos6

==
ERROR: Test read_user_data_callback() no files are found.
--
Traceback (most recent call last):
  File "/root/cloud-init/tests/unittests/test_datasource/test_altcloud.py", 
line 422, in test_callback_none
self.assertIsNone(dsac.read_user_data_callback(self.mount_dir))
AttributeError: 'TestReadUserDataCallback' object has no attribute 
'assertIsNone'

==
FAIL: test_scripts_shebanged 
(tests.unittests.test_datasource.test_smartos.TestSmartOSDataSource)
--
Traceback (most recent call last):
  File "/root/cloud-init/tests/unittests/test_datasource/test_smartos.py", line 
465, in test_scripts_shebanged
self.assertEqual(shebang, "#!/bin/bash")
AssertionError: '/bin/true' != '#!/bin/bash'
- /bin/true
+ #!/bin/bash

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1693307

Title:
  tests: centos6 env failures

Status in cloud-init:
  New

Bug description:
  There are two current test failures on centos6 tox env.

  
  Steps to reproduce:
  0. lxc launch images:centos/6 c6
  1. lxc exec c6 bash
  2. yum install epel-release -y
  3. yum install git python-pip -y
  4. git clone master
  5. cd cloud-init
  6. tox -e centos6

  ==
  ERROR: Test read_user_data_callback() no files are found.
  --
  Traceback (most recent call last):
File "/root/cloud-init/tests/unittests/test_datasource/test_altcloud.py", 
line 422, in test_callback_none
  self.assertIsNone(dsac.read_user_data_callback(self.mount_dir))
  AttributeError: 'TestReadUserDataCallback' object has no attribute 
'assertIsNone'

  ==
  FAIL: test_scripts_shebanged 
(tests.unittests.test_datasource.test_smartos.TestSmartOSDataSource)
  --
  Traceback (most recent call last):
File "/root/cloud-init/tests/unittests/test_datasource/test_smartos.py", 
line 465, in test_scripts_shebanged
  self.assertEqual(shebang, "#!/bin/bash")
  AssertionError: '/bin/true' != '#!/bin/bash'
  - /bin/true
  + #!/bin/bash

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1693307/+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 1692686] Re: tests: ntp integration test regression

2017-05-23 Thread Joshua Powers
Fixed via:
https://git.launchpad.net/cloud-init/commit/?id=9fa17d4bc1ef2564e30ab655bf6de462296aecad
https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/324429

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

** Changed in: cloud-init
   Importance: Undecided => High

-- 
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/1692686

Title:
  tests: ntp integration test regression

Status in cloud-init:
  Fix Released

Bug description:
  After Friday, May 19, an NTP merge regressed the NTP integration tests
  as the wrong file was called to check for output. Test output:

  AssertionError: File "ntp_conf_pools" missing from collect data

  The code was mistakenly updated to say "ntp_conf_pools" when it should
  say "ntp_conf_servers".

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1692686/+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 1692960] [NEW] tests: pycodestyle regression - expected 2 blank lines

2017-05-23 Thread Joshua Powers
Public bug reported:

On May 22, 2017 the cloud-init-style tip job that runs pycodestyle
discovered a failure:

cloudinit/sources/DataSourceAzure.py:167:1: E305 expected 2 blank lines
after class or function definition, found 1

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1692960

Title:
  tests: pycodestyle regression - expected 2 blank lines

Status in cloud-init:
  New

Bug description:
  On May 22, 2017 the cloud-init-style tip job that runs pycodestyle
  discovered a failure:

  cloudinit/sources/DataSourceAzure.py:167:1: E305 expected 2 blank
  lines after class or function definition, found 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1692960/+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 1692686] [NEW] tests: ntp integration test regression

2017-05-22 Thread Joshua Powers
Public bug reported:

After Friday, May 19, an NTP merge regressed the NTP integration tests
as the wrong file was called to check for output. Test output:

AssertionError: File "ntp_conf_pools" missing from collect data

The code was mistakenly updated to say "ntp_conf_pools" when it should
say "ntp_conf_servers".

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1692686

Title:
  tests: ntp integration test regression

Status in cloud-init:
  New

Bug description:
  After Friday, May 19, an NTP merge regressed the NTP integration tests
  as the wrong file was called to check for output. Test output:

  AssertionError: File "ntp_conf_pools" missing from collect data

  The code was mistakenly updated to say "ntp_conf_pools" when it should
  say "ntp_conf_servers".

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1692686/+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 1691517] [NEW] centos7 unit tests fail due to hard coded mkfs.ext4

2017-05-17 Thread Joshua Powers
Public bug reported:

A recent merge that added a mkfs.ext4 tests has a hard coded location
for the binary of mkfs.ext4. The result is that on centos 7, which has
the command in a different location than Ubuntu, is a failed test:

https://paste.ubuntu.com/24589593/

Steps to reproduce:
lxc launch images:centos/7 c7
lxc exec c7 bash
yum install --assumeyes epel-release
yum install --assumeyes pyserial python-argparse python-cheetah 
python-configobj python-jinja2 python-jsonpatch python-oauthlib 
python-prettytable python-requests python-six python-pip PyYAML git file 
e2fsprogs
pip install contextlib2 httpretty mock nose pep8 unittest2
git clone https://git.launchpad.net/cloud-init
cd cloud-init
nosetests tests/unittests

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Description changed:

  A recent merge that added a mkfs.ext4 tests has a hard coded location
  for the binary of mkfs.ext4. The result is that on centos 7, which has
  the command in a different location than Ubuntu, is a failed test:
  
  https://paste.ubuntu.com/24589593/
- 
  
  Steps to reproduce:
  lxc launch images:centos/7 c7
  lxc exec c7 bash
  yum install --asumeyes python-pip
  yum install --assumeyes git python-pip file e2fsprogs
  pip install setuptools tox virtualenv contextlib2 httpretty mock nose pep8 
unittest2
- git clone https://git.launchpad.net/cloud-init 
+ git clone https://git.launchpad.net/cloud-init
  cd cloud-init
- tox
+ nosetests tests/unittests

-- 
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/1691517

Title:
  centos7 unit tests fail due to hard coded mkfs.ext4

Status in cloud-init:
  New

Bug description:
  A recent merge that added a mkfs.ext4 tests has a hard coded location
  for the binary of mkfs.ext4. The result is that on centos 7, which has
  the command in a different location than Ubuntu, is a failed test:

  https://paste.ubuntu.com/24589593/

  Steps to reproduce:
  lxc launch images:centos/7 c7
  lxc exec c7 bash
  yum install --assumeyes epel-release
  yum install --assumeyes pyserial python-argparse python-cheetah 
python-configobj python-jinja2 python-jsonpatch python-oauthlib 
python-prettytable python-requests python-six python-pip PyYAML git file 
e2fsprogs
  pip install contextlib2 httpretty mock nose pep8 unittest2
  git clone https://git.launchpad.net/cloud-init
  cd cloud-init
  nosetests tests/unittests

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1691517/+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 1690880] Re: test_snappy_version fails on artful

2017-05-15 Thread Joshua Powers
Steps to reproduce:

$ lxc launch ubuntu-daily:artful a
$ lxc exec a bash
# snap --version
snap snapctl  
root@a:~# snap --version
snap2.26.1+17.10
snapd   unavailable
series  -

** Also affects: snappy
   Importance: Undecided
   Status: New

** Description changed:

- Integration tests reported a failure in artful as of May 15, 2017:
+ Steps to reproduce:
+ 
+ $ lxc launch ubuntu-daily:artful a
+ $ lxc exec a bash
+ # snap --version
+ snap snapctl
+ root@a:~# snap --version
+ snap 2.26.1+17.10
+ snapd unavailable
+ series -
+ 
+ As stated below it appears that snapd was not running. Upon inspection
+ the service was not running and could not be started manually. systemctl
+ output: https://paste.ubuntu.com/24583118/
+ 
+ 
+ cloud-init integration tests reported a failure in artful as of May 15, 2017:
  
  ==
  FAIL: test_snappy_version (tests.cloud_tests.testcases.get_suite..tmp)
  --
  Traceback (most recent call last):
-   File 
"/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-integration-a/cloud-init/tests/cloud_tests/testcases/modules/snappy.py",
 line 16, in test_snappy_version
- self.assertIn('ubuntu ', out)
+   File 
"/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-integration-a/cloud-init/tests/cloud_tests/testcases/modules/snappy.py",
 line 16, in test_snappy_version
+ self.assertIn('ubuntu ', out)
  AssertionError: 'ubuntu ' not found in 'snap2.26.1+17.10\nsnapd   
unavailable\nseries  -\n'
  
- 
- This test runs the 'snap --verison' command and gets the output. Then 
verifies the following are contained in the output:
+ This test runs the 'snap --verison' command and gets the output. Then
+ verifies the following are contained in the output:
  
  self.assertIn('snap ', out)
  self.assertIn('snapd ', out)
  self.assertIn('series ', out)
  self.assertIn('ubuntu ', out)
  
- Output on Zesty:
+ Output on Zesty LXD using ubuntu-daily image:
  snap2.24.1+17.04
  snapd   2.24.1+17.04
  series  16
  ubuntu  17.04
  kernel  4.10.0-20-generic
  
- Output on Artful:
+ Output on Artful LXD using ubuntu-daily image:
  snap2.26.1+17.10
  snapd   unavailable
  series  -

-- 
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/1690880

Title:
  test_snappy_version fails on artful

Status in cloud-init:
  New
Status in Snappy:
  New

Bug description:
  Steps to reproduce:

  $ lxc launch ubuntu-daily:artful a
  $ lxc exec a bash
  # snap --version
  snap snapctl
  root@a:~# snap --version
  snap 2.26.1+17.10
  snapd unavailable
  series -

  As stated below it appears that snapd was not running. Upon inspection
  the service was not running and could not be started manually.
  systemctl output: https://paste.ubuntu.com/24583118/

  
  cloud-init integration tests reported a failure in artful as of May 15, 2017:

  ==
  FAIL: test_snappy_version (tests.cloud_tests.testcases.get_suite..tmp)
  --
  Traceback (most recent call last):
    File 
"/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-integration-a/cloud-init/tests/cloud_tests/testcases/modules/snappy.py",
 line 16, in test_snappy_version
  self.assertIn('ubuntu ', out)
  AssertionError: 'ubuntu ' not found in 'snap2.26.1+17.10\nsnapd   
unavailable\nseries  -\n'

  This test runs the 'snap --verison' command and gets the output. Then
  verifies the following are contained in the output:

  self.assertIn('snap ', out)
  self.assertIn('snapd ', out)
  self.assertIn('series ', out)
  self.assertIn('ubuntu ', out)

  Output on Zesty LXD using ubuntu-daily image:
  snap2.24.1+17.04
  snapd   2.24.1+17.04
  series  16
  ubuntu  17.04
  kernel  4.10.0-20-generic

  Output on Artful LXD using ubuntu-daily image:
  snap2.26.1+17.10
  snapd   unavailable
  series  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1690880/+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 1690880] [NEW] test_snappy_version fails on artful

2017-05-15 Thread Joshua Powers
Public bug reported:

Integration tests reported a failure in artful as of May 15, 2017:

==
FAIL: test_snappy_version (tests.cloud_tests.testcases.get_suite..tmp)
--
Traceback (most recent call last):
  File 
"/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-integration-a/cloud-init/tests/cloud_tests/testcases/modules/snappy.py",
 line 16, in test_snappy_version
self.assertIn('ubuntu ', out)
AssertionError: 'ubuntu ' not found in 'snap2.26.1+17.10\nsnapd   
unavailable\nseries  -\n'


This test runs the 'snap --verison' command and gets the output. Then verifies 
the following are contained in the output:

self.assertIn('snap ', out)
self.assertIn('snapd ', out)
self.assertIn('series ', out)
self.assertIn('ubuntu ', out)

Output on Zesty:
snap2.24.1+17.04
snapd   2.24.1+17.04
series  16
ubuntu  17.04
kernel  4.10.0-20-generic

Output on Artful:
snap2.26.1+17.10
snapd   unavailable
series  -

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1690880

Title:
  test_snappy_version fails on artful

Status in cloud-init:
  New

Bug description:
  Integration tests reported a failure in artful as of May 15, 2017:

  ==
  FAIL: test_snappy_version (tests.cloud_tests.testcases.get_suite..tmp)
  --
  Traceback (most recent call last):
File 
"/var/lib/jenkins/slaves/torkoal/workspace/cloud-init-integration-a/cloud-init/tests/cloud_tests/testcases/modules/snappy.py",
 line 16, in test_snappy_version
  self.assertIn('ubuntu ', out)
  AssertionError: 'ubuntu ' not found in 'snap2.26.1+17.10\nsnapd   
unavailable\nseries  -\n'

  
  This test runs the 'snap --verison' command and gets the output. Then 
verifies the following are contained in the output:

  self.assertIn('snap ', out)
  self.assertIn('snapd ', out)
  self.assertIn('series ', out)
  self.assertIn('ubuntu ', out)

  Output on Zesty:
  snap2.24.1+17.04
  snapd   2.24.1+17.04
  series  16
  ubuntu  17.04
  kernel  4.10.0-20-generic

  Output on Artful:
  snap2.26.1+17.10
  snapd   unavailable
  series  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1690880/+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 1685831] [NEW] pylint: cloudinit.util 'closing' has no 'read' member

2017-04-24 Thread Joshua Powers
Public bug reported:

Tip style checker [1] discovered the following errors, but I believe
this is a false positive:

* Module cloudinit.util
cloudinit/util.py:480: [E1101(no-member), decomp_gzip] Instance of 'closing' 
has no 'read' member
cloudinit/util.py:482: [E1101(no-member), decomp_gzip] Instance of 'closing' 
has no 'read' member

Offending code [2] and upstream bug filed [3]

[1] https://paste.ubuntu.com/24448453/
[2] https://paste.ubuntu.com/24448487/
[3] https://github.com/PyCQA/pylint/issues/1444

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1685831

Title:
  pylint: cloudinit.util 'closing' has no 'read' member

Status in cloud-init:
  New

Bug description:
  Tip style checker [1] discovered the following errors, but I believe
  this is a false positive:

  * Module cloudinit.util
  cloudinit/util.py:480: [E1101(no-member), decomp_gzip] Instance of 'closing' 
has no 'read' member
  cloudinit/util.py:482: [E1101(no-member), decomp_gzip] Instance of 'closing' 
has no 'read' member

  Offending code [2] and upstream bug filed [3]

  [1] https://paste.ubuntu.com/24448453/
  [2] https://paste.ubuntu.com/24448487/
  [3] https://github.com/PyCQA/pylint/issues/1444

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1685831/+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 1636531] Re: unittests blkid command fails on slave s390x

2017-04-11 Thread Joshua Powers
Fixed by modifying the jenkins env. path to include
/home/jenkins/bin:/home/jenkins/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin:/snap/bin

** Changed in: cloud-init
   Status: New => Invalid

-- 
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/1636531

Title:
  unittests blkid command fails on slave s390x

Status in cloud-init:
  Invalid

Bug description:
  Running the unittests on our slave s390x system, the blkid command
  fails. Running it manually returns the following:

  jenkins@s1lp04:~$ blkid -tLABEL=CDROM -odevice
  jenkins@s1lp04:~$ echo $?
  2
  jenkins@s1lp04:~$ lsblk
  NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  dasda 94:00  20.6G  0 disk 
  |-dasda1  94:10  19.7G  0 part /
  `-dasda2  94:20 953.5M  0 part [SWAP]

  Full run output:
  https://jenkins.ubuntu.com/server/job/cloud-init-ci/nodes=s390x/53/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1636531/+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 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails

2017-04-10 Thread Joshua Powers
** Changed in: cloud-init
   Status: Confirmed => 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/1499869

Title:
  maas wily deployment to HP Proliant m400 arm64 server cartridge fails

Status in cloud-init:
  Fix Released
Status in curtin:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in cloud-init source package in Wily:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  This is the error seen on the console:

  [   64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: 
Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin
  [  124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - 
url_helper.py[WARNING]: Calling 
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed 
[2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', 
port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id 
(Caused by 
ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect 
timeout=50.0)'))]
  [  124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - 
DataSourceEc2.py[CRITICAL]: Giving up on md from 
['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds
  [  124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - 
url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404]

  This times out eventually and the node is left at the login prompt. I
  can install wily via netboot without issue and some time back, wily
  was deployable to this node from MAAS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1499869/+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 1671937] Re: chpasswd list fails

2017-03-14 Thread Joshua Powers
** Changed in: cloud-init
   Status: New => Invalid

-- 
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/1671937

Title:
  chpasswd list fails

Status in cloud-init:
  Invalid

Bug description:
  While trying to write an intergration test for the new method of
  chpasswd via a list, cloud-init fails while attempting to change the
  password for a user called ["['tom"]. It appears the list based method
  is not being read correctly:

  2017-03-10 20:25:43,934 - cc_set_passwords.py[DEBUG]: Changing
  password for ["['tom"]:

  cloud-conifg:
  https://paste.ubuntu.com/24153626/

  result:
  https://paste.ubuntu.com/24153632/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1671937/+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 1671937] [NEW] chpasswd list fails

2017-03-10 Thread Joshua Powers
Public bug reported:

While trying to write an intergration test for the new method of
chpasswd via a list, cloud-init fails while attempting to change the
password for a user called ["['tom"]. It appears the list based method
is not being read correctly:

2017-03-10 20:25:43,934 - cc_set_passwords.py[DEBUG]: Changing password
for ["['tom"]:

cloud-conifg:
https://paste.ubuntu.com/24153626/

result:
https://paste.ubuntu.com/24153632/

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1671937

Title:
  chpasswd list fails

Status in cloud-init:
  New

Bug description:
  While trying to write an intergration test for the new method of
  chpasswd via a list, cloud-init fails while attempting to change the
  password for a user called ["['tom"]. It appears the list based method
  is not being read correctly:

  2017-03-10 20:25:43,934 - cc_set_passwords.py[DEBUG]: Changing
  password for ["['tom"]:

  cloud-conifg:
  https://paste.ubuntu.com/24153626/

  result:
  https://paste.ubuntu.com/24153632/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1671937/+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 1671883] Re: chpasswd regression

2017-03-10 Thread Joshua Powers
** 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/1671883

Title:
  chpasswd regression

Status in cloud-init:
  Fix Released

Bug description:
  Last night's integration tests failed on a regression to the chpasswd
  value. All three tested releases with the same failures:

  set_password
  set_password_expire
  set_password_list

  Yesterday a new commit was accepted around chpasswd and allowing new types of 
list:
  
https://git.launchpad.net/cloud-init/commit/?id=7f2b51054a5defec4c04fc40026bda7dd29f69fe

  set_password.yaml:  
chpasswd: { expire: False }

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
  plist = plist.spitlines()
  AttributeError: 'str' object has no attribute 'spitlines'

  
  set_password_expire.yaml:  
chpasswd: { expire: True }

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 92, in handle
  if isinstance(chfg['list'], list):
  KeyError: 'list'

  
  set_password_list.yaml:
chpasswd:
  list: |
tom:mypassword123!
dick:R
harry:Random

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
  plist = plist.spitlines()
  AttributeError: 'str' object has no attribute 'spitlines'

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1671883/+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 1671883] [NEW] chpasswd regression

2017-03-10 Thread Joshua Powers
Public bug reported:

Last night's integration tests failed on a regression to the chpasswd
value. All three tested releases with the same failures:

set_password
set_password_expire
set_password_list

Yesterday a new commit was accepted around chpasswd and allowing new types of 
list:
https://git.launchpad.net/cloud-init/commit/?id=7f2b51054a5defec4c04fc40026bda7dd29f69fe

set_password.yaml:  
  chpasswd: { expire: False }

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
freq=freq)
  File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
return self._runners.run(name, functor, args, freq, clear_on_fail)
  File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
results = functor(*args)
  File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
plist = plist.spitlines()
AttributeError: 'str' object has no attribute 'spitlines'


set_password_expire.yaml:  
  chpasswd: { expire: True }

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
freq=freq)
  File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
return self._runners.run(name, functor, args, freq, clear_on_fail)
  File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
results = functor(*args)
  File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 92, in handle
if isinstance(chfg['list'], list):
KeyError: 'list'


set_password_list.yaml:
  chpasswd:
list: |
  tom:mypassword123!
  dick:R
  harry:Random

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
freq=freq)
  File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
return self._runners.run(name, functor, args, freq, clear_on_fail)
  File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
results = functor(*args)
  File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
plist = plist.spitlines()
AttributeError: 'str' object has no attribute 'spitlines'

** Affects: cloud-init
 Importance: High
 Status: Fix Committed

** Changed in: cloud-init
   Importance: Undecided => High

-- 
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/1671883

Title:
  chpasswd regression

Status in cloud-init:
  Fix Committed

Bug description:
  Last night's integration tests failed on a regression to the chpasswd
  value. All three tested releases with the same failures:

  set_password
  set_password_expire
  set_password_list

  Yesterday a new commit was accepted around chpasswd and allowing new types of 
list:
  
https://git.launchpad.net/cloud-init/commit/?id=7f2b51054a5defec4c04fc40026bda7dd29f69fe

  set_password.yaml:  
chpasswd: { expire: False }

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
  plist = plist.spitlines()
  AttributeError: 'str' object has no attribute 'spitlines'

  
  set_password_expire.yaml:  
chpasswd: { expire: True }

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 92, in handle
  if isinstance(chfg['list'], list):
  KeyError: 'list'

  
  set_password_list.yaml:
chpasswd:
  list: |
tom:mypassword123!
dick:R
harry:Random

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 783, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_set_passwords.py", 
line 99, in handle
  plis

[Yahoo-eng-team] [Bug 1606394] Re: Support for LaunchPad git repos

2017-03-06 Thread Joshua Powers
CI in place and running \o/

** Changed in: cloud-init
   Status: Confirmed => Fix Released

** Changed in: jenkins-launchpad-plugin
   Status: Confirmed => 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/1606394

Title:
  Support for LaunchPad git repos

Status in cloud-init:
  Fix Released
Status in jenkins-launchpad-plugin:
  Fix Released

Bug description:
  LaunchPad supports the use of git as a version control system. The
  plugin (as far as I can tell) does not allow specifying a git based
  repo as it was built around the use of bzr.

  In addition to using git over bzr, some of the changes between the two
  systems' URLs are outlined below:

  Merge Request:
  bzr: 
https://code.launchpad.net/~harlowja/cloud-init/cloud-init-tag-distros/+merge/300840
  git: 
https://code.launchpad.net/~harlowja/cloud-init/+git/cloud-init/+merge/301108

  Proposed Branch:
  bzr: https://code.launchpad.net/~harlowja/cloud-init/cloud-init-tag-distros
  git: 
https://code.launchpad.net/~harlowja/cloud-init/+git/cloud-init/+ref/distro-tags

  Merge Branch:
  bzr: https://code.launchpad.net/~cloud-init-dev/cloud-init/trunk
  git: 
https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master

  
  I am currently trying to determine what the best route would be to add git 
support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1606394/+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 1652329] Re: sort out pyflakes flake8 pycodestyle pep8

2017-02-10 Thread Joshua Powers
Resolved via:
https://code.launchpad.net/~powersj/curtin/make-tox-great-again
and
https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+ref/make-tox-revamp

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

** Changed in: curtin
   Status: New => 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/1652329

Title:
  sort out pyflakes flake8 pycodestyle pep8

Status in cloud-init:
  Fix Released
Status in curtin:
  Fix Released

Bug description:
  I was again bit by this... tox works fine (running flake8)
  but built of zesty failed.

  In cloud-init, the Makefile that is run during build runs (currently)
  pep8 and pyflakes (either pyflakes2 or pyflakes3).

  I think what we ultimately want is to run flake8 and let it run
  pyflakes and pep8.

  However, given dependencies and versions in different distro releases,
  this is a bit of a pain.

  One path to this is just to not run any code checking in the distro
  build, assuming that it is already run in trunk.  I think that seems
  like a sane argument actually.

  One thing to note, is that pep8 is now called pycodestyle.

  Out of this, I'd like to have:
   a.) a tox target that tracks upstream pypi versions (but doesn't fail c-i), 
and somethign that runs this fairly often to at least see how bad we are 
getting.
   b.) a tox target that has pinned versions of checking tools, and runs checks 
both for python2 and python3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1652329/+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 1656144] Re: Please update or remove github repo

2017-01-24 Thread Joshua Powers
Mirroring from launchpad master to Github is now taking place 4 times a
day.


** Changed in: cloud-init
   Status: Confirmed => 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/1656144

Title:
  Please update or remove github repo

Status in cloud-init:
  Fix Released

Bug description:
  Please update this GitHub repo or remove it or at least update the
  README to point to the Git repository you are using instead:

  https://github.com/cloud-init/cloud-init

  github issue also opened at https://github.com/cloud-init/cloud-
  init/issues/4

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1656144/+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 1643020] Re: zfs backed lxd fails with missing /dev/zfs

2016-11-23 Thread Joshua Powers
After attempting this on a KVM instance I was able to get past the
error. Ran into other issues, but can confirm that the Xenial LXD
container was unable to successfully create zfs due to the lack of
/dev/zfs.

Therefore this test of LXD ZFS backends will need to be done in KVM.

Closing as invalid.

** Changed in: cloud-init
   Status: New => Invalid

-- 
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/1643020

Title:
  zfs backed lxd fails with missing /dev/zfs

Status in cloud-init:
  Invalid

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup lxd backed by 
zfs fails to create due to a missing /dev/zfs

  [cloud-config]
  #cloud-config
  lxd:
init:
  storage_backend: zfs
  storage_pool: lxd

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  Nov 18 17:27:42 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Running module lxd 
() 
failed#012Traceback (most recent call last):#012  File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 785, in 
_run_modules#012freq=freq)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#012
return self._runners.run(name, functor, args, freq, clear_on_fail)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in run#012
results = functor(*args)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/config/cc_lxd.py", line 104, in 
handle#012util.subp(cmd)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/util.py", line 1832, in subp#012
cmd=args)#012cloudinit.util.ProcessExecutionError: Unexpected error while 
running command.#012Command: ['lxd', 'init', '--auto', '--storage-backend=zfs', 
'--storage-pool=lxd']#012Exit code: 1#012Reas
 on: -#012Stdout: ''#012Stderr: 'error: Invalid ZFS pool: /dev/zfs and 
/proc/self/mounts are required.\n'

  root@xenial-lxd:~# ls /dev/zfs
  ls: cannot access '/dev/zfs': No such file or directory
  root@xenial-lxd:~# ls /proc/self/mounts
  /proc/self/mounts

  [expected result]
  I would have expected zfs to be setup with a pool named 'lxd' and cloud-init 
to complete successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643020/+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 1644043] [NEW] Read Kernel Config tests missing MAC Address

2016-11-22 Thread Joshua Powers
Public bug reported:

Unittests are broken [1] preventing cloud-init from building currently.
The issue is the kernel config tests are looking for a MAC address that
is not there.

[1] https://jenkins.ubuntu.com/server/job/cloud-init-integration-
lts/35/console

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1644043

Title:
  Read Kernel Config tests missing MAC Address

Status in cloud-init:
  New

Bug description:
  Unittests are broken [1] preventing cloud-init from building
  currently. The issue is the kernel config tests are looking for a MAC
  address that is not there.

  [1] https://jenkins.ubuntu.com/server/job/cloud-init-integration-
  lts/35/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1644043/+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 1643043] [NEW] random seed command output not captured

2016-11-18 Thread Joshua Powers
Public bug reported:

[description]
While using a 16.04 (Xenial) lxd cloud image, trying to create random seed data 
with a command does not get put into a specified file.

[cloud-config]
#cloud-config
random_seed:
  command: ["cat", "/proc/sys/kernel/random/uuid"]
  command_required: true
  file: /root/seed

[steps to reproduce]
Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

lxc init ubuntu:xenial/amd64 xenial
lxc config set xenial user.user-data - < cloud-config.yaml
lxc start xenial

[actual result]
There is no file called /root/seed and no error messages even though the 
command is marked as required.

[expected result]
I would have expected the file /root/seed to exist with a uuid in it.

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Attachment added: "cloud-init.log"
   
https://bugs.launchpad.net/bugs/1643043/+attachment/4779452/+files/cloud-init.log

-- 
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/1643043

Title:
  random seed command output not captured

Status in cloud-init:
  New

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to create random seed 
data with a command does not get put into a specified file.

  [cloud-config]
  #cloud-config
  random_seed:
command: ["cat", "/proc/sys/kernel/random/uuid"]
command_required: true
file: /root/seed

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
  cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  There is no file called /root/seed and no error messages even though the 
command is marked as required.

  [expected result]
  I would have expected the file /root/seed to exist with a uuid in it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643043/+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 1643041] [NEW] snappy module does not install snaps

2016-11-18 Thread Joshua Powers
Public bug reported:

[description]
While using a 16.04 (Xenial) lxd cloud image, trying to setup snappy to install 
hello-world does not work.

[cloud-config]
#cloud-config
snappy:
  system_snappy: yes (or auto)
  packages: [hello-world]

[steps to reproduce]
Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

lxc init ubuntu:xenial/amd64 xenial
lxc config set xenial user.user-data - < cloud-config.yaml
lxc start xenial

[actual result]
snappy is installed, however, `snap list` returns no snaps installed.

[expected result]
I would have expected the "hello-world" snap to be installed.

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1643041

Title:
  snappy module does not install snaps

Status in cloud-init:
  New

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup snappy to 
install hello-world does not work.

  [cloud-config]
  #cloud-config
  snappy:
system_snappy: yes (or auto)
packages: [hello-world]

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
  cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  snappy is installed, however, `snap list` returns no snaps installed.

  [expected result]
  I would have expected the "hello-world" snap to be installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643041/+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 1643022] [NEW] landscape module does not work

2016-11-18 Thread Joshua Powers
Public bug reported:

[description]
While using a 16.04 (Xenial) lxd cloud image, trying to setup landscape does 
not install the landscape-client or set up the config and has no error message.

[cloud-config]
#cloud-conifg
landscape:
  client:
log_level: "info"
url: "https://landscape.canonical.com/message-system";
ping_url: "http://landscape.canonical.com/ping";
data_path: "/var/lib/landscape/client"
http_proxy: "http://my.proxy.com/foobar";
https_proxy: "https://my.proxy.com/foobar";
tags: "server,cloud"
computer_title: "footitle"
registration_key: "fookey"
account_name: "fooaccount"

[steps to reproduce]
Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

lxc init ubuntu:xenial/amd64 xenial
lxc config set xenial user.user-data - < cloud-config.yaml
lxc start xenial

[actual result]
root@xenial-lxd:/var/log# cat cloud-init.log  | grep landscape
Nov 18 17:40:00 xenial-lxd [CLOUDINIT] stages.py[DEBUG]: Running module 
landscape () with 
frequency once-per-instance
Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: start: 
modules-final/config-landscape: running config-landscape with frequency 
once-per-instance
Nov 18 17:40:00 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/xenial-lxd/sem/config_landscape - wb: [420] 24 bytes
Nov 18 17:40:00 xenial-lxd [CLOUDINIT] helpers.py[DEBUG]: Running 
config-landscape using lock ()
Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: finish: 
modules-final/config-landscape: SUCCESS: config-landscape ran successfully

[expected result]
I would have expected landscape-client to get installed and the configuration 
file to be written.

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1643022

Title:
  landscape module does not work

Status in cloud-init:
  New

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup landscape does 
not install the landscape-client or set up the config and has no error message.

  [cloud-config]
  #cloud-conifg
  landscape:
client:
  log_level: "info"
  url: "https://landscape.canonical.com/message-system";
  ping_url: "http://landscape.canonical.com/ping";
  data_path: "/var/lib/landscape/client"
  http_proxy: "http://my.proxy.com/foobar";
  https_proxy: "https://my.proxy.com/foobar";
  tags: "server,cloud"
  computer_title: "footitle"
  registration_key: "fookey"
  account_name: "fooaccount"

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)
  cloud-init: 0.7.8-1-g3705bb5-0ubuntu1~16.04.3

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  root@xenial-lxd:/var/log# cat cloud-init.log  | grep landscape
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] stages.py[DEBUG]: Running module 
landscape () with 
frequency once-per-instance
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: start: 
modules-final/config-landscape: running config-landscape with frequency 
once-per-instance
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Writing to 
/var/lib/cloud/instances/xenial-lxd/sem/config_landscape - wb: [420] 24 bytes
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] helpers.py[DEBUG]: Running 
config-landscape using lock ()
  Nov 18 17:40:00 xenial-lxd [CLOUDINIT] handlers.py[DEBUG]: finish: 
modules-final/config-landscape: SUCCESS: config-landscape ran successfully

  [expected result]
  I would have expected landscape-client to get installed and the configuration 
file to be written.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643022/+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 1643020] [NEW] zfs backed lxd fails with missing /dev/zfs

2016-11-18 Thread Joshua Powers
Public bug reported:

[description]
While using a 16.04 (Xenial) lxd cloud image, trying to setup lxd backed by zfs 
fails to create due to a missing /dev/zfs

[cloud-config]
#cloud-config
lxd:
  init:
storage_backend: zfs
storage_pool: lxd

[steps to reproduce]
Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)

lxc init ubuntu:xenial/amd64 xenial
lxc config set xenial user.user-data - < cloud-config.yaml
lxc start xenial

[actual result]
Nov 18 17:27:42 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Running module lxd 
() 
failed#012Traceback (most recent call last):#012  File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 785, in 
_run_modules#012freq=freq)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#012
return self._runners.run(name, functor, args, freq, clear_on_fail)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in run#012
results = functor(*args)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/config/cc_lxd.py", line 104, in 
handle#012util.subp(cmd)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/util.py", line 1832, in subp#012
cmd=args)#012cloudinit.util.ProcessExecutionError: Unexpected error while 
running command.#012Command: ['lxd', 'init', '--auto', '--storage-backend=zfs', 
'--storage-pool=lxd']#012Exit code: 1#012Reason
 : -#012Stdout: ''#012Stderr: 'error: Invalid ZFS pool: /dev/zfs and 
/proc/self/mounts are required.\n'

root@xenial-lxd:~# ls /dev/zfs
ls: cannot access '/dev/zfs': No such file or directory
root@xenial-lxd:~# ls /proc/self/mounts
/proc/self/mounts

[expected result]
I would have expected zfs to be setup with a pool named 'lxd' and cloud-init to 
complete successfully.

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Attachment added: "cloud-init.log"
   
https://bugs.launchpad.net/bugs/1643020/+attachment/4779422/+files/lxd-zfs-cloud-init.log

-- 
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/1643020

Title:
  zfs backed lxd fails with missing /dev/zfs

Status in cloud-init:
  New

Bug description:
  [description]
  While using a 16.04 (Xenial) lxd cloud image, trying to setup lxd backed by 
zfs fails to create due to a missing /dev/zfs

  [cloud-config]
  #cloud-config
  lxd:
init:
  storage_backend: zfs
  storage_pool: lxd

  [steps to reproduce]
  Image used: b9cba741ef62 ubuntu 16.04 LTS amd64 (release) (20161115)

  lxc init ubuntu:xenial/amd64 xenial
  lxc config set xenial user.user-data - < cloud-config.yaml
  lxc start xenial

  [actual result]
  Nov 18 17:27:42 xenial-lxd [CLOUDINIT] util.py[DEBUG]: Running module lxd 
() 
failed#012Traceback (most recent call last):#012  File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 785, in 
_run_modules#012freq=freq)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 70, in run#012
return self._runners.run(name, functor, args, freq, clear_on_fail)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in run#012
results = functor(*args)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/config/cc_lxd.py", line 104, in 
handle#012util.subp(cmd)#012  File 
"/usr/lib/python3/dist-packages/cloudinit/util.py", line 1832, in subp#012
cmd=args)#012cloudinit.util.ProcessExecutionError: Unexpected error while 
running command.#012Command: ['lxd', 'init', '--auto', '--storage-backend=zfs', 
'--storage-pool=lxd']#012Exit code: 1#012Reas
 on: -#012Stdout: ''#012Stderr: 'error: Invalid ZFS pool: /dev/zfs and 
/proc/self/mounts are required.\n'

  root@xenial-lxd:~# ls /dev/zfs
  ls: cannot access '/dev/zfs': No such file or directory
  root@xenial-lxd:~# ls /proc/self/mounts
  /proc/self/mounts

  [expected result]
  I would have expected zfs to be setup with a pool named 'lxd' and cloud-init 
to complete successfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1643020/+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 1636531] [NEW] unittests blkid command fails on slave s390x

2016-10-25 Thread Joshua Powers
Public bug reported:

Running the unittests on our slave s390x system, the blkid command
fails. Running it manually returns the following:

jenkins@s1lp04:~$ blkid -tLABEL=CDROM -odevice
jenkins@s1lp04:~$ echo $?
2
jenkins@s1lp04:~$ lsblk
NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
dasda 94:00  20.6G  0 disk 
|-dasda1  94:10  19.7G  0 part /
`-dasda2  94:20 953.5M  0 part [SWAP]

Full run output:
https://jenkins.ubuntu.com/server/job/cloud-init-ci/nodes=s390x/53/console

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1636531

Title:
  unittests blkid command fails on slave s390x

Status in cloud-init:
  New

Bug description:
  Running the unittests on our slave s390x system, the blkid command
  fails. Running it manually returns the following:

  jenkins@s1lp04:~$ blkid -tLABEL=CDROM -odevice
  jenkins@s1lp04:~$ echo $?
  2
  jenkins@s1lp04:~$ lsblk
  NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  dasda 94:00  20.6G  0 disk 
  |-dasda1  94:10  19.7G  0 part /
  `-dasda2  94:20 953.5M  0 part [SWAP]

  Full run output:
  https://jenkins.ubuntu.com/server/job/cloud-init-ci/nodes=s390x/53/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1636531/+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 1636308] [NEW] unittests: <10% coverage of cc_disk_setup.py

2016-10-24 Thread Joshua Powers
Public bug reported:

The cloudinit/config/cc_disk_setup.py currently has: 441 statements, 389
miss, 9% coverage

I am filing this as this would be a good opportunity for community
contributions, for clean up work to enhance our quality, and want to
capture the work.

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1636308

Title:
  unittests: <10% coverage of cc_disk_setup.py

Status in cloud-init:
  New

Bug description:
  The cloudinit/config/cc_disk_setup.py currently has: 441 statements,
  389 miss, 9% coverage

  I am filing this as this would be a good opportunity for community
  contributions, for clean up work to enhance our quality, and want to
  capture the work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1636308/+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 1636312] [NEW] unittests: <10% coverage of netinfo.py

2016-10-24 Thread Joshua Powers
Public bug reported:

The cloudinit/netinfo.py currently has: 150 statements, 139 miss, 5%
coverage

I am filing this as this would be a good opportunity for community
contributions, for clean up work to enhance our quality, and want to
capture the work.

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1636312

Title:
  unittests: <10% coverage of netinfo.py

Status in cloud-init:
  New

Bug description:
  The cloudinit/netinfo.py currently has: 150 statements, 139 miss, 5%
  coverage

  I am filing this as this would be a good opportunity for community
  contributions, for clean up work to enhance our quality, and want to
  capture the work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1636312/+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 1636311] [NEW] unittests: <10% coverage of cc_set_passwords.py

2016-10-24 Thread Joshua Powers
Public bug reported:

The cloudinit/config/cc_set_passwords.py currently has: 111 statements,
102 miss, 6% coverage

I am filing this as this would be a good opportunity for community
contributions, for clean up work to enhance our quality, and want to
capture the work.

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1636311

Title:
  unittests: <10% coverage of cc_set_passwords.py

Status in cloud-init:
  New

Bug description:
  The cloudinit/config/cc_set_passwords.py currently has: 111
  statements, 102 miss, 6% coverage

  I am filing this as this would be a good opportunity for community
  contributions, for clean up work to enhance our quality, and want to
  capture the work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1636311/+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 1635350] [NEW] bddeb does not work on a system deployed by maas

2016-10-20 Thread Joshua Powers
Public bug reported:

Observed Behavior:

On a system deployed by MAAS I checked out master and then tried to immediately 
build it:
> git clone https://git.launchpad.net/cloud-init
> cd cloud-init
> ./packages/bddeb

I get a number of errors around permission issues around this file:
PermissionError: [Errno 13] Permission denied: 
\'/etc/cloud/cloud.cfg.d/90_dpkg_maas.cfg\'

See: https://paste.ubuntu.com/23354559/

If I run as root however, it build as expected.


Expected Behavior:
Running bddeb works as a non-root user.

** Affects: cloud-init
 Importance: Undecided
 Status: New

-- 
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/1635350

Title:
  bddeb does not work on a system deployed by maas

Status in cloud-init:
  New

Bug description:
  Observed Behavior:

  On a system deployed by MAAS I checked out master and then tried to 
immediately build it:
  > git clone https://git.launchpad.net/cloud-init
  > cd cloud-init
  > ./packages/bddeb

  I get a number of errors around permission issues around this file:
  PermissionError: [Errno 13] Permission denied: 
\'/etc/cloud/cloud.cfg.d/90_dpkg_maas.cfg\'

  See: https://paste.ubuntu.com/23354559/

  If I run as root however, it build as expected.

  
  Expected Behavior:
  Running bddeb works as a non-root user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1635350/+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 1606394] Re: Support for LaunchPad git repos

2016-07-26 Thread Joshua Powers
** Also affects: cloud-init
   Importance: Undecided
   Status: New

-- 
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/1606394

Title:
  Support for LaunchPad git repos

Status in cloud-init:
  New
Status in jenkins-launchpad-plugin:
  New

Bug description:
  LaunchPad supports the use of git as a version control system. The
  plugin (as far as I can tell) does not allow specifying a git based
  repo as it was built around the use of bzr.

  In addition to using git over bzr, some of the changes between the two
  systems' URLs are outlined below:

  Merge Request:
  bzr: 
https://code.launchpad.net/~harlowja/cloud-init/cloud-init-tag-distros/+merge/300840
  git: 
https://code.launchpad.net/~harlowja/cloud-init/+git/cloud-init/+merge/301108

  Proposed Branch:
  bzr: https://code.launchpad.net/~harlowja/cloud-init/cloud-init-tag-distros
  git: 
https://code.launchpad.net/~harlowja/cloud-init/+git/cloud-init/+ref/distro-tags

  Merge Branch:
  bzr: https://code.launchpad.net/~cloud-init-dev/cloud-init/trunk
  git: 
https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master

  
  I am currently trying to determine what the best route would be to add git 
support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1606394/+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