| 2017-03-22 00:51:49 |
Fernando J. Cordeiro |
bug |
|
|
added bug |
| 2017-03-22 14:09:32 |
Jon Grimm |
bug |
|
|
added subscriber Jon Grimm |
| 2017-03-22 14:23:23 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2017-03-22 14:23:23 |
Scott Moser |
cloud-init: status |
New |
Incomplete |
|
| 2017-03-22 15:22:24 |
Fernando J. Cordeiro |
attachment added |
|
bug#1674861-collected.zip https://bugs.launchpad.net/cloud-init/+bug/1674861/+attachment/4842372/+files/bug%231674861-collected.zip |
|
| 2017-03-22 15:24:17 |
Fernando J. Cordeiro |
cloud-init: status |
Incomplete |
Confirmed |
|
| 2017-03-23 19:35:42 |
Scott Moser |
summary |
Cloud-init datasource setting to none after update |
GCE Cloud-init datasource setting to none after update |
|
| 2017-03-23 19:37:08 |
Scott Moser |
summary |
GCE Cloud-init datasource setting to none after update |
Google Compute Engine (gce) datasource setting to none after update |
|
| 2017-03-23 19:37:17 |
Scott Moser |
summary |
Google Compute Engine (gce) datasource setting to none after update |
Google Compute Engine (GCE) datasource setting to none after update |
|
| 2017-03-27 16:56:16 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/321094 |
|
| 2017-03-27 17:42:17 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu) |
|
| 2017-03-27 18:45:24 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
In Progress |
|
| 2017-03-27 18:45:26 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Medium |
|
| 2017-03-28 16:25:27 |
Scott Moser |
cloud-init: status |
Confirmed |
Fix Committed |
|
| 2017-03-28 23:44:38 |
John Kirkham |
bug |
|
|
added subscriber John Kirkham |
| 2017-03-31 11:51:03 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
In Progress |
Fix Released |
|
| 2017-04-03 14:34:50 |
Scott Moser |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-04-03 14:34:50 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Yakkety) |
|
| 2017-04-03 14:34:50 |
Scott Moser |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-04-03 14:34:50 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Xenial) |
|
| 2017-04-03 14:34:58 |
Scott Moser |
cloud-init (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2017-04-03 14:35:01 |
Scott Moser |
cloud-init (Ubuntu Yakkety): status |
New |
Confirmed |
|
| 2017-04-03 14:35:03 |
Scott Moser |
cloud-init (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2017-04-03 14:35:05 |
Scott Moser |
cloud-init (Ubuntu Yakkety): importance |
Undecided |
Medium |
|
| 2017-04-04 17:42:14 |
Scott Moser |
description |
The following message appears after login in my Google Cloud VPS:
**************************************************************************
# A new feature in cloud-init identified possible datasources for #
# this system as: #
# ['None'] #
# However, the datasource used was: GCE #
# #
# In the future, cloud-init will only attempt to use datasources that #
# are identified or specifically configured. #
# For more information see #
# https://bugs.launchpad.net/bugs/1669675 #
# #
# If you are seeing this message, please file a bug against #
# cloud-init at #
# https://bugs.launchpad.net/cloud-init/+filebug?field.tags=dsid #
# Make sure to include the cloud provider your instance is #
# running on. #
# #
# After you have filed a bug, you can disable this warning by launching #
# your instance with the cloud-config below, or putting that content #
# into /etc/cloud/cloud.cfg.d/99-warnings.cfg #
# #
# #cloud-config #
# warnings: #
# dsid_missing_source: off #
************************************************************************** |
=== Begin SRU Template ===
[Impact]
When running on a Google Compute (GCE),
instances may show a warning on ssh login or in the cloud-init.log file.
This was by design, as we wanted to find places where ds-identify was
not working correctly.
This seems to only occur on older instances. The original reporter
cannot re-create it on a new instance. The reason for the behavior
change is that the new instances have different smbios information.
Presumably this is because the mechanism for launching the new
instances has been changed to include 'Google Compute' in the Product
Name where previously only 'Google' appeard.
[Test Case]
Note, you'd have to have an old instance to actually see this.
So this is not really easy to test the fix.
The test for no regression is easier:
1. Launch an instance on a GCE.
2. enable proposed, upgrade
3. rm -Rf /var/lib/cloud /var/log/cloud*
4. reboot
5. ssh back in, expect to see no warning.
[Regression Potential]
Very low. the change was just to consider an a dmi product serial
number with 'GoogleCloud-*' as a indication that we are running on
Google Compute. That would seem a very low false-positive rate.
[Other Info]
=== End SRU Template ===
The following message appears after login in my Google Cloud VPS:
**************************************************************************
# A new feature in cloud-init identified possible datasources for #
# this system as: #
# ['None'] #
# However, the datasource used was: GCE #
# #
# In the future, cloud-init will only attempt to use datasources that #
# are identified or specifically configured. #
# For more information see #
# https://bugs.launchpad.net/bugs/1669675 #
# #
# If you are seeing this message, please file a bug against #
# cloud-init at #
# https://bugs.launchpad.net/cloud-init/+filebug?field.tags=dsid #
# Make sure to include the cloud provider your instance is #
# running on. #
# #
# After you have filed a bug, you can disable this warning by launching #
# your instance with the cloud-config below, or putting that content #
# into /etc/cloud/cloud.cfg.d/99-warnings.cfg #
# #
# #cloud-config #
# warnings: #
# dsid_missing_source: off #
************************************************************************** |
|
| 2017-04-10 22:25:35 |
Brian Murray |
cloud-init (Ubuntu Yakkety): status |
Confirmed |
Fix Committed |
|
| 2017-04-10 22:25:37 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-04-10 22:25:39 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2017-04-10 22:25:44 |
Brian Murray |
tags |
dsid |
dsid verification-needed |
|
| 2017-04-10 22:47:51 |
Brian Murray |
cloud-init (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2017-04-14 19:01:06 |
Scott Moser |
tags |
dsid verification-needed |
dsid verification-done-xenial verification-done-yakkety |
|
| 2017-04-20 19:33:34 |
Launchpad Janitor |
cloud-init (Ubuntu Yakkety): status |
Fix Committed |
Fix Released |
|
| 2017-04-20 19:35:04 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-04-20 19:35:54 |
Launchpad Janitor |
cloud-init (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-09-23 02:30:13 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2017-09-29 17:29:35 |
Francis Ginther |
tags |
dsid verification-done-xenial verification-done-yakkety |
dsid id-58d1e989e9aad3138d26e398 verification-done-xenial verification-done-yakkety |
|
| 2018-02-16 15:21:36 |
John Kirkham |
removed subscriber John Kirkham |
|
|
|
| 2023-05-10 21:51:26 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2835 |
|
