This bug was fixed in the package cloud-init -
0.7.8-67-gc9c9197-0ubuntu1

---------------
cloud-init (0.7.8-67-gc9c9197-0ubuntu1) zesty; urgency=medium

  * debian/cherry-pick: add utility for cherry picking commits from upstream
    into patches in debian/patches.
  * New upstream snapshot.
    - mounts: use mount -a again to accomplish mounts (LP: #1647708)
    - CloudSigma: Fix bug where datasource was not loaded in local search. (LP: 
#1648380)
    - when adding a user, strip whitespace from group list (LP: #1354694)
    - fix decoding of utf-8 chars in yaml test
    - Replace usage of sys_netdev_info with read_sys_net (LP: #1625766)
    - fix problems found in python2.6 test.

 -- Scott Moser <smo...@ubuntu.com>  Sun, 11 Dec 2016 21:22:57 -0500

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1648380

Title:
  cloud-init fails to find CloudSigma datasource with cloud-init
  0.7.8-1-g3705bb5-0ubuntu1

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  [SRU justification]
  Without this fix, images built with cloud-init 0.7.8-1-g3705bb5-0ubuntu1  and 
later will not correctly boot and become unreachable

  [Impact]
  Some cloud images built with this version of cloud-init may become unusable

  [Fix]
  Reinstate the second element of the datasources list as a tuple instead of a 
string.

  [Test Case]
  This test must be done on CloudSigma to complete correctly :

  Build cloud image with only the CloudSigma datasource using cloud-init 
version 0.7.8-1-g3705bb5-0ubuntu1 or later
  Launch an instance with this image
  The instance will boot but will not be accessible through ssh

  With this fix,the instance will complete its boot sequence and be
  accessible through ssh

  [Regression]
  None expected, the second element was a tuple in previous versions of the 
CloudSigma datasource

  [Description of the problem]
  The issue materialized itself on cloud instances launched with such images 
that became unreachable through SSH with the following message:

  "Connection closed by {IP} port 22"

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

_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to