yahoo-eng-team team mailing list archive

[Miroslav Suchý <1439653@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I have ansible playbook which utilize nova_compute module
  http://docs.ansible.com/nova_compute_module.html
and after that we use wait_for module:
  http://docs.ansible.com/wait_for_module.html
which waits until port 22 is ready. However next task tries to ssh on that VM, but it fails despite SSHD being enabled and running, because cloud-init did not finished deployment of SSH keys.

The workaround is to wait up to 20 seconds, which is quite pity.

Can be cloud-init (or something else in OpenStack) be enhanced that SSHD
will be started after SSH keys are deployed?

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

Title:
  RFE: do not enable ssh service untill ssh keys are on place

Status in Init scripts for use on cloud images:
  New

Bug description:
  I have ansible playbook which utilize nova_compute module
    http://docs.ansible.com/nova_compute_module.html
  and after that we use wait_for module:
    http://docs.ansible.com/wait_for_module.html
  which waits until port 22 is ready. However next task tries to ssh on that VM, but it fails despite SSHD being enabled and running, because cloud-init did not finished deployment of SSH keys.

  The workaround is to wait up to 20 seconds, which is quite pity.

  Can be cloud-init (or something else in OpenStack) be enhanced that
  SSHD will be started after SSH keys are deployed?

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