Comment 22 for bug 1674861

Revision history for this message
jim (fox3551) wrote : Re: [Bug 1674861] Re: Google Compute Engine (GCE) datasource setting to none after update

Hi James,
While I have worked with GCE in the past it's been a while. Perhaps the
email address you want has a '.' in the middle, eg <email address hidden>
(a guy in Australia I believe)

Cheers,
Jim

On Wed, May 10, 2023 at 3:01 PM James Falcon <email address hidden>
wrote:

> Tracked in Github Issues as https://github.com/canonical/cloud-
> init/issues/2835
>
> ** Bug watch added: github.com/canonical/cloud-init/issues #2835
> https://github.com/canonical/cloud-init/issues/2835
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1703141).
> https://bugs.launchpad.net/bugs/1674861
>
> Title:
> Google Compute Engine (GCE) datasource setting to none after update
>
> 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 Yakkety:
> Fix Released
>
> Bug description:
> === 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
> #
>
> **************************************************************************
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1674861/+subscriptions
>
>