cloud-sdk-bookworm debian repo wrong Label?

[dkanov]

Hello, 

I've noticed that the Label, Origin and Description of the cloud-sdk-bookworm Debian repo have changed to "cloud-sdk-bullseye". Can be viewed here: https://packages.cloud.google.com/apt/dists/cloud-sdk-bookworm/Release. They seem to be correct for packages.cloud.google.com/apt/dists/cloud-sdk-bullseye/Release. I only noticed it because an automated build which uses the cloud-sdk:466.0.0-slim Docker image has started failing on "apt update" with:

E: Repository 'https://packages.cloud.google.com/apt cloud-sdk-bookworm InRelease' changed its 'Origin' value from 'cloud-sdk-bookworm' to 'cloud-sdk-bullseye'
E: Repository 'https://packages.cloud.google.com/apt cloud-sdk-bookworm InRelease' changed its 'Label' value from 'cloud-sdk-bookworm' to 'cloud-sdk-bullseye'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Is that intentional or an oversight? 

Thanks!

[klesti]

Hello,

We've stumbled upon the same issue. Unfortunately, we can't reproduce the issue consistently.

There was also a new 467.0.0 release: https://groups.google.com/g/google-cloud-sdk-announce/c/t66jOU9Om5w

However, there's no mention of this issue in the release notes and the label/origin mismatch still persists: https://packages.cloud.google.com/apt/dists/cloud-sdk-bookworm/Release 

Looking forward to an explanation / further details.

[Szczytf]

Hi,

I have came across the same problem last week. Yesterday it seemed to be working fine, but this morning it failed again. I am not sure but something is fishy with the label changes.

As for the info for others how I temporary "fixed it" - not without consequences. We are using docket image google/cloud-sdk from docket hub. I am renaming the entry in the /etc/apt/sources.list.d/google-cloud-sdk.list file entries cloud-sdk-bookworm to cloud-sdk-bullseye as follows:

sed 's/cloud-sdk-bookworm/cloud-sdk-bullseye/g' /etc/apt/sources.list.d/google-cloud-sdk.list > /etc/apt/sources.list.d/google-cloud-sdk.list.2 & sleep 5 & mv /etc/apt/sources.list.d/google-cloud-sdk.list.2 /etc/apt/sources.list.d/google-cloud-sdk.list || true

As you can see there is some weird bits with sleep and true at the end. Thats because my script has interim issues with errors saying that mv cannot be done as file doesnt exists. I have put sleep 1 initially which made it less frequent, later tested with 5 seconds. Still occasionally error occurs. I have forced success to the script to let it continue but its dodgy as.

So as you can see it gives me a bit of a headache - this needs to be resolved. Any neater temporary solutions are most welcome.

Thank you!

Regards,
Franek

[Szczytf]

On the side note - there is another potential issue with the legacy keyring. Probably others get the same warning message:

https://packages.cloud.google.com/apt/dists/cloud-sdk-bookworm/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details

I have fixed it with this:

cd /etc/apt
sudo cp trusted.gpg trusted.gpg.d

Its apparently not the best option - for docket image is good enough for me. More info at:

ubuntu - W: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION ...

[dkanov]

My quick fix was to add "--allow-releaseinfo-change-origin --allow-releaseinfo-change-label" to the failing apt commands.

[Szczytf]

Thanks Dkanov, that is way neater than mine. And it works too. Cheers

[lawrencenelson]

Hi all,

Welcome to the Google Cloud Community!

This issue was known previously and was supposed to be fixed. It seems the problem has resurfaced, potentially due to the new 467.0.0 update, although I have yet to confirm this with the engineering team.

Thank you, @dkanov, for providing the details of the issue and the temporary workaround.

[lawrencenelson]

Hi @dkanov @klesti @Szczytf 

I spoke with the engineering team and this should now be fixed. Kindly try again on your end. Thank you.

[dkanov]

Hi,

Thanks for the reply!

Just checked with 468.0.0 and the apt-get update no longer fails so it seems the issue has been fixed. However, the labels in this file packages.cloud.google.com/apt/dists/cloud-sdk-bookworm/Release still look wrong. That's a really minor thing though so probably not worth fixing.

[joe-mse]

This actually is still an issue for anyone using unattended-upgrades to update from google-cloud-sdk. I have had to go and manually edit the 50unattended-upgrades file on several Debian 12 systems and replace "origin=cloud-sdk,codename=cloud-sdk,label=cloud-sdk"; with "origin=cloud-sdk-bullseye,codename=cloud-sdk-bookworm,label=cloud-sdk-bullseye";. Undoubtedly, I will forget to check this when it is fixed and will start wondering why my automatic updates are broken. Please can we have the page that dkanov referenced above fixed?

Thanks,

Joe

[joe-mse]

This actually is an issue for anyone using unattended-upgrades to update from google-cloud-sdk. I have had to go and manually edit the 50unattended-upgrades file on several Debian 12 systems and replace "origin=cloud-sdk,codename=cloud-sdk,label=cloud-sdk"; with "origin=cloud-sdk-bullseye,codename=cloud-sdk-bookworm,label=cloud-sdk-bullseye";. Undoubtedly, I will forget to check this when it is fixed and will start wondering why my automatic updates are broken. Please can we have the page that dkanov referenced above fixed?

Thanks,

Joe