** Branch linked: lp:ubuntu/cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1428495
Title:
Does not enable ssh even with ssh_enabled: True
To manage notifications
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)
--
** Changed in: cloud-init
Status: New = Confirmed
** Changed in: cloud-init
Importance: Undecided = High
** Changed in: cloud-init
Assignee: (unassigned) = Scott Moser (smoser)
** Changed in: cloud-init
Status: Confirmed = In Progress
--
You received this bug
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1428495
Title:
Does not enable ssh even with ssh_enabled: True
To manage notifications about this
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1428495
Title:
Does not enable ssh even with ssh_enabled:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
fwiw, the cloud-config required to enable it is:
#cloud-config
snappy:
ssh_enabled: True
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1428495
Title:
Does not enable ssh
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.
--
You received this bug notification
... 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.
--
You received this bug notification because you
