yahoo-eng-team team mailing list archive

[Mike Hommey <mh@xxxxxxxxxxxx>]

Public bug reported:

STR:
- Take the Ubuntu Precise EC2 AMI and prepare an instance out of it.
- On that instance, set user-data to something that is not a cloud-config, not mime-encoded and not a few bytes.[1][2]
- Start the instance

Expected result:
- The instance is reachable by ssh.

Actual result:
- It's not reachable. Console output ends with "__init__.py[WARNING]: Unhandled non-multipart userdata (...)"
- /var/log/cloud-init.log shows that a boot leading to a reachable instance has logs messages about cloud-init-cfg, but a boot leading to an unreachable instance doesn't.

1. In my case "foo=bar" doesn't cause the problem, but "name=glandium-builders" does.
2. Note in my case I've been stopping and restarting an instance with different values for user-data, so it might actually not happen on the first boot, I don't know for sure, as the initial user-data for my instance was empty, and I already spent too much time tracking this problem.

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

Title:
  cloud-init-cfg doesn't run when user-data is not a cloud-config

Status in Init scripts for use on cloud images:
  New

Bug description:
  STR:
  - Take the Ubuntu Precise EC2 AMI and prepare an instance out of it.
  - On that instance, set user-data to something that is not a cloud-config, not mime-encoded and not a few bytes.[1][2]
  - Start the instance

  Expected result:
  - The instance is reachable by ssh.

  Actual result:
  - It's not reachable. Console output ends with "__init__.py[WARNING]: Unhandled non-multipart userdata (...)"
  - /var/log/cloud-init.log shows that a boot leading to a reachable instance has logs messages about cloud-init-cfg, but a boot leading to an unreachable instance doesn't.

  1. In my case "foo=bar" doesn't cause the problem, but "name=glandium-builders" does.
  2. Note in my case I've been stopping and restarting an instance with different values for user-data, so it might actually not happen on the first boot, I don't know for sure, as the initial user-data for my instance was empty, and I already spent too much time tracking this problem.

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