This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
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/1638931
Title:
enable AliYun datasource by default
Status in cloud-init:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
Fix Released
Status in cloud-init source package in Zesty:
Fix Released
Bug description:
=== Begin SRU Template ===
[Impact]
Ubuntu cloud-images do not identify the Aliyun cloud platform.
Until this change was put in place, they would fail to boot and consume
user-data or metadata there.
With the change in place, an official Ubuntu image from
http://cloud-images.ubuntu.com will work properly on Aliyun.
[Test Case]
The ideal test case is:
a.) download a cloud image, update its cloud-init
The tool 'get-proposed-cloudimg' [1] can be used to do this.
[1] https://git.launchpad.net/~smoser/cloud-init/+git/sru-
info/tree/bin/get-proposed-cloudimg
b.) publish that image to Aliyun cloud
c.) boot an instance from that image.
d.) verify function by ssh in verifying /run/cloud-init/result.json shows
that aliyun datasource was used.
Ideally post /var/log/cloud-init.log as an attachment to this bug.
[Regression Potential]
Generally small chance for regression, but a regression would most likely
be seen as an attempt to hit the metadata service at the well known end point
http://100.100.100.200.
This should be fairly well confined as attempts to use the Aliyun datasource
are gated by '_is_aliyun_' which does verifies that the dmi product name is
"Alibaba Cloud ECS"
[Other Info]
Upstream commit at
https://git.launchpad.net/cloud-init/commit/?id=4a60af5495
=== End SRU Template ===
As discussed at [1], the addition of AliYun datasource did not enable it by
default.
This is because it has no definitive check before polling the network for
data.
Lawrence suggested he has a solution for this:
| in our cloud platform, an instance vm could use an asm
| instructions `cpuid` (with eax setted to 0x40000100 ), it will
| returned our platform id keyword "AliYun" into register ebx and ecx,
| and if vm is not running on our environment, the value is others. so I
| guess this is a method to identify our platform ?
--
[1]
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/309614
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1638931/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
