[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#986717: marked as done (google-compute-engine: Should fail gracefully when installed in non-GCE environment)

Your message dated Thu, 03 Feb 2022 18:03:07 +0000
with message-id <[🔎] E1nFgRn-0007ZX-F3@fasolo.debian.org>
and subject line Bug#1004075: Removed package(s) from unstable
has caused the Debian Bug report #986717,
regarding google-compute-engine: Should fail gracefully when installed in non-GCE environment
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
986717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986717
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: google-compute-engine
Severity: wishlist
X-Debbugs-Cc: jesse@sney.ca

Dear Maintainer,

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. 

sney

-- 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.

--- End Message ---
--- Begin Message --- 
Version: 20190916-1+rm

Dear submitter,

as the package google-compute-image-packages has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1004075

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
Reply to: