Does not enable ssh even with ssh_enabled: True

Bug #1428495 reported by Martin Pitt
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
High
Scott Moser
cloud-init (Ubuntu)
Fix Released
High
Unassigned

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.

Related branches

Martin Pitt (pitti)
tags: added: regression-release
Changed in cloud-init (Ubuntu):
importance: Undecided → High
tags: added: vivid
description: updated
Revision history for this message
Martin Pitt (pitti) wrote :

Also, creating /etc/ssh/sshd_not_to_be_run is a really awkward, nonstandard, and hard to discover way of disabling ssh. You should rather do "update-rc.d ssh disable", which works under any init system and is the canonical way of enabling/disabling services.

Revision history for this message
Martin Pitt (pitti) wrote :

... with that, manually starting it with "systemctl start ssh" will do the right thing, and the administrator can use the standard commands (like systemctl enable ssh) to reactivate it again, instead of digging why it's enabled but doesn't work.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cloud-init (Ubuntu):
status: New → Confirmed
Revision history for this message
Scott Moser (smoser) wrote :

fwiw, the cloud-config required to enable it is:
 #cloud-config
  snappy:
    ssh_enabled: True

Scott Moser (smoser)
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Scott Moser (smoser)
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Thu, 05 Mar 2015 15:22:53 -0500

Changed in cloud-init (Ubuntu):
status: Confirmed → Fix Released
Scott Moser (smoser)
Changed in cloud-init:
status: In Progress → Fix Committed
tags: added: cloud-images
Revision history for this message
Scott Moser (smoser) wrote :

This is fixed in cloud-init 0.7.7

Changed in cloud-init:
status: Fix Committed → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.