yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1428495@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init - 0.7.7~bzr1078-0ubuntu1

---------------
cloud-init (0.7.7~bzr1078-0ubuntu1) vivid; urgency=medium

  * New upstream snapshot.
    * run snappy module only on snappy (LP: #1428495)
    * MAAS: adjust timestamp on oauthlib when needed (LP: #1427939)
 -- Scott Moser <smoser@xxxxxxxxxx>   Thu, 05 Mar 2015 15:22:53 -0500

** 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/1428495

Title:
  Does not enable ssh even with ssh_enabled: True

Status in Init scripts for use on cloud images:
  In Progress
Status in cloud-init package in Ubuntu:
  Fix Released

Bug description:
  The latest cloud images from vivid with cloud-init
  0.7.7~bzr1076-0ubuntu1 now stop enabling ssh by default, as they
  create an /etc/ssh/ssh_not_to_be_run stamp file. Aside from the fact
  that there was no warning about it and it's not documented in the
  changelog or documentation or anywhere, re-enabling also does not seem
  to work. I found the new "ssh_enabled" key in
  cloudinit/config/cc_snappy.py, but setting it in my user-data (for
  generating a local seed iso) does not work.

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