Bug#986717: google-compute-engine: Should fail gracefully when installed in non-GCE environment
If the google-compute-engine package is installed on a system not part of the google cloud, the included services are started by the postinst script, and apt hangs indefinitely (presumably because the services can't contact the google infrastructure). The only way to recover at that point is to kill the associated python3 processes from a different tty. Removing the package has an almost identical result, with systemctl hanging instead.
Sometimes people make mistakes. It's entirely reasonable to imagine someone moving a service from google to a different cloud provider, and trying to mimic their environment as closely as possible with a 'dpkg --get-selections' or so, and accidentally ending up in this state.
It should be possible to install this package in error and not have to kill postinst subprocesses manually in order to recover.
Behavior is present in the buster (20190124-3) and sid/testing (20190916-1) versions of google-compute-engine.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages google-compute-engine depends on:
pn google-compute-engine-oslogin <none>
pn python3-google-compute-engine <none>
google-compute-engine recommends no packages.
google-compute-engine suggests no packages.