Re: Call to GCE metadata/compute in nocloud buster image

2024-03-22 Thread Ross Vandegrift
On Fri, Mar 22, 2024 at 04:12:57PM +0100, Stephan Müller wrote: > Oh, interesting! Thanks for the quick answer. Do you know if and how I can > control this behavior? cloud-init is trying to figure out if it's running on GCE by checking for the local metadata service. It should fail and move on.

Re: Call to GCE metadata/compute in nocloud buster image

2024-03-22 Thread Stephan Müller
>> Can this be related to the underlying genericcloud image? So far, I was >> unable to find anything with "computeMetadata" in the systemlogs of the VMs. >> I checked the boot log (including cloud-init process) using virsh console >> but also found no hint to computeMetadata > This is from

Re: Call to GCE metadata/compute in nocloud buster image

2024-03-22 Thread Bastian Blank
On Fri, Mar 22, 2024 at 10:03:29AM +0100, Stephan Müller wrote: > Can this be related to the underlying genericcloud image? So far, I was > unable to find anything with "computeMetadata" in the systemlogs of the VMs. > I checked the boot log (including cloud-init process) using virsh console >

Call to GCE metadata/compute in nocloud buster image

2024-03-22 Thread Stephan Müller
Hi, I'm running several Debian Buster GenericCloud images. (Exact image: https://cloud.debian.org/images/cloud/bullseye/20221108-1193/debian-11-genericcloud-amd64-20221108-1193.qcow2) The images run on libvirt "on-premise", i.e. not in a cloud environment. The setup is such, that all outbound