| 2017-01-30 16:52:02 |
Scott Moser |
bug |
|
|
added bug |
| 2017-01-30 16:52:08 |
Scott Moser |
cloud-init: status |
New |
Confirmed |
|
| 2017-01-30 16:52:13 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2017-01-30 16:52:19 |
Scott Moser |
cloud-init: status |
Confirmed |
In Progress |
|
| 2017-01-30 16:52:22 |
Scott Moser |
cloud-init: assignee |
|
Scott Moser (smoser) |
|
| 2017-01-31 16:51:24 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/316033 |
|
| 2017-02-03 17:15:59 |
John Leach |
bug |
|
|
added subscriber John Leach |
| 2017-02-23 21:58:55 |
Scott Moser |
description |
Many cloud providers mimic the EC2 Metadata service [1] in order to provide
a level of EC2 compatibility for images. This is quite useful and allows
image portability.
Because this is a network based metadata service, cloud-init opportunistically
poll an IPv4 link local address (http://169.254.169.254) to determine if there
is metadata available. That can have negative side affects such as timeouts.
AWS has recently begun providing a way for instances to determine if they
are running on EC2 [2].
Cloud-init will change its behavior to only attempt to find the EC2 metadata
service only if it has determined itself to be running on EC2 or another
known cloud provider which provides an EC2 metadata service.
--
[1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
[2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html |
Many cloud providers mimic the EC2 Metadata service [1] in order to
provide a level of EC2 compatibility for images. This is quite useful and
allows image portability.
Because this is a network based metadata service, cloud-init
opportunistically poll an IPv4 link local address (http://169.254.169.254)
to determine if there is metadata available. That can have negative side
affects such as timeouts.
AWS has recently begun providing a way for instances to determine if they
are running on EC2 [2].
Cloud-init will change its behavior to attempt to find the EC2 metadata
service only if it has determined itself to be running on EC2 or another
known cloud provider which provides an EC2 metadata service.
For more information, please see:
https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html
--
[1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
[2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html |
|
| 2017-03-03 02:28:33 |
Scott Moser |
tags |
|
dsid |
|
| 2017-03-03 02:30:10 |
Scott Moser |
cloud-init: status |
In Progress |
Fix Committed |
|
| 2017-03-03 05:31:56 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu) |
|
| 2017-03-03 05:32:05 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
Fix Released |
|
| 2017-03-03 05:32:08 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-03-03 05:32:18 |
Scott Moser |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-03-03 05:32:18 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Yakkety) |
|
| 2017-03-03 05:32:18 |
Scott Moser |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-03-03 05:32:18 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Xenial) |
|
| 2017-03-03 05:32:33 |
Scott Moser |
cloud-init (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2017-03-03 05:32:35 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2017-03-03 05:32:38 |
Scott Moser |
cloud-init (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2017-03-03 05:32:40 |
Scott Moser |
cloud-init (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
| 2017-03-03 05:42:08 |
Scott Moser |
description |
Many cloud providers mimic the EC2 Metadata service [1] in order to
provide a level of EC2 compatibility for images. This is quite useful and
allows image portability.
Because this is a network based metadata service, cloud-init
opportunistically poll an IPv4 link local address (http://169.254.169.254)
to determine if there is metadata available. That can have negative side
affects such as timeouts.
AWS has recently begun providing a way for instances to determine if they
are running on EC2 [2].
Cloud-init will change its behavior to attempt to find the EC2 metadata
service only if it has determined itself to be running on EC2 or another
known cloud provider which provides an EC2 metadata service.
For more information, please see:
https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html
--
[1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
[2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html |
=== Begin SRU Template ===
[Impact]
Opportunistic polling of the Ec2 Metadata service, which lives at
169.254.169.254 can be problematic for numerous reasons including timeouts.
In this first phase of SRU, the code that has been added will be set to
a warn-only mode.
In 16.04, if cloud-init finds it is using a EC2 Metadata Service but
not running on Amazon AWS, it will warn the user.
In 16.10, it will warn the user and sleep 10 seconds to increase the
likelyhood of being noticed.
[Test Case]
TBD
[Regression Potential]
There is real regression potential here. That is why we have announced
this fairly widely and also are putting this into place with warnings
only first.
After some time is passed, further SRUs will put more strict behavior
in place.
[Other Info]
We've announced this fairly widely on mailing lists
https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html
=== End SRU Template ===
Many cloud providers mimic the EC2 Metadata service [1] in order to
provide a level of EC2 compatibility for images. This is quite useful and
allows image portability.
Because this is a network based metadata service, cloud-init
opportunistically poll an IPv4 link local address (http://169.254.169.254)
to determine if there is metadata available. That can have negative side
affects such as timeouts.
AWS has recently begun providing a way for instances to determine if they
are running on EC2 [2].
Cloud-init will change its behavior to attempt to find the EC2 metadata
service only if it has determined itself to be running on EC2 or another
known cloud provider which provides an EC2 metadata service.
For more information, please see:
https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html
--
[1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
[2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html |
|
| 2017-03-03 06:43:34 |
Scott Moser |
description |
=== Begin SRU Template ===
[Impact]
Opportunistic polling of the Ec2 Metadata service, which lives at
169.254.169.254 can be problematic for numerous reasons including timeouts.
In this first phase of SRU, the code that has been added will be set to
a warn-only mode.
In 16.04, if cloud-init finds it is using a EC2 Metadata Service but
not running on Amazon AWS, it will warn the user.
In 16.10, it will warn the user and sleep 10 seconds to increase the
likelyhood of being noticed.
[Test Case]
TBD
[Regression Potential]
There is real regression potential here. That is why we have announced
this fairly widely and also are putting this into place with warnings
only first.
After some time is passed, further SRUs will put more strict behavior
in place.
[Other Info]
We've announced this fairly widely on mailing lists
https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html
=== End SRU Template ===
Many cloud providers mimic the EC2 Metadata service [1] in order to
provide a level of EC2 compatibility for images. This is quite useful and
allows image portability.
Because this is a network based metadata service, cloud-init
opportunistically poll an IPv4 link local address (http://169.254.169.254)
to determine if there is metadata available. That can have negative side
affects such as timeouts.
AWS has recently begun providing a way for instances to determine if they
are running on EC2 [2].
Cloud-init will change its behavior to attempt to find the EC2 metadata
service only if it has determined itself to be running on EC2 or another
known cloud provider which provides an EC2 metadata service.
For more information, please see:
https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html
--
[1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
[2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html |
=== Begin SRU Template ===
[Impact]
Opportunistic polling of the Ec2 Metadata service, which lives at
169.254.169.254 can be problematic for numerous reasons including timeouts.
In this first phase of SRU, the code that has been added will be set to
a warn-only mode.
In 16.04, if cloud-init finds it is using a EC2 Metadata Service but
not running on Amazon AWS, it will warn the user.
In 16.10, it will warn the user and sleep 10 seconds to increase the
likelyhood of being noticed.
[Test Case]
a.) check warnings are seen on openstack configured to use ec2
- launch instance on openstack (it will use OpenStack MD)
- enable proposed upgrade
- rm -Rf /var/lib/cloud /var/log/cloud-init*
- dpkg-reconfigure cloud-init
# select 'Ec2' and 'None' only
- sudo reboot
- ssh in. you should see a warning.
The warning instructs you to silence the warning by putting
the following in /etc/cloud/cloud.cfg.d/99-ec2-datasource.cfg. Do that.
| datasource:
| Ec2:
| strict_id: false
- rm -Rf /var/lib/cloud/ /var/log/cloud*
- reboot
- ssh in. you should not see a warning.
[Regression Potential]
There is real regression potential here. That is why we have announced
this fairly widely and also are putting this into place with warnings
only first.
After some time is passed, further SRUs will put more strict behavior
in place.
[Other Info]
We've announced this fairly widely on mailing lists
https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html
=== End SRU Template ===
Many cloud providers mimic the EC2 Metadata service [1] in order to
provide a level of EC2 compatibility for images. This is quite useful and
allows image portability.
Because this is a network based metadata service, cloud-init
opportunistically poll an IPv4 link local address (http://169.254.169.254)
to determine if there is metadata available. That can have negative side
affects such as timeouts.
AWS has recently begun providing a way for instances to determine if they
are running on EC2 [2].
Cloud-init will change its behavior to attempt to find the EC2 metadata
service only if it has determined itself to be running on EC2 or another
known cloud provider which provides an EC2 metadata service.
For more information, please see:
https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039697.html
--
[1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html
[2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/identify_ec2_instances.html |
|
| 2017-03-07 23:25:38 |
Chris Halse Rogers |
cloud-init (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2017-03-07 23:25:42 |
Chris Halse Rogers |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-03-07 23:25:48 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
| 2017-03-07 23:25:55 |
Chris Halse Rogers |
tags |
dsid |
dsid verification-needed |
|
| 2017-03-07 23:34:01 |
Chris Halse Rogers |
cloud-init (Ubuntu Yakkety): status |
Confirmed |
Fix Committed |
|
| 2017-03-08 22:57:19 |
Scott Moser |
tags |
dsid verification-needed |
dsid verification-done-xenial verification-done-yakkety |
|
| 2017-03-16 16:18:49 |
Launchpad Janitor |
cloud-init (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-03-16 16:19:14 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-03-16 16:19:33 |
Launchpad Janitor |
cloud-init (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-05-02 08:20:42 |
Vladimir Pouzanov |
bug |
|
|
added subscriber Vladimir Pouzanov |
| 2017-09-22 20:49:19 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2023-05-10 20:06:24 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2795 |
|
