Just to add some info on guest agent here:
the guest agent does not set up the primary interface
there should be no race between guest agent and cloud-init for the
primary interface
the guest agent does not start any dhclient process for primary
interface, and should not care if any dhclient pro
I've never heard of the 'empty python3-google-compute-engine
transitional package'; for upstream packaging, we use "Conflicts:
python3-google-compute-engine" and this will cause the top level package
(called google-compute-engine upstream, I think called gce-compute-
image-packages in Ubuntu) to be
Please also apply this change to the google-guest-agent package
** Also affects: google-guest-agent (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
*** This bug is a duplicate of bug 1900897 ***
https://bugs.launchpad.net/bugs/1900897
** Also affects: google-guest-agent (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
Upstream's build parameters;
override_dh_auto_build:
dh_auto_build -O--buildsystem=golang -- -ldflags="-s -w -X
main.version=$(VERSION)-$(RELEASE)" -mod=readonly
- Strip the binary
- Set main.version
** Affects: google-osconfig-agent (Ubuntu)
Importance: Unde
It's a complicated situation, but I'll try to highlight some of the
reasons.
First, there is the complexity of existing files. We will only copy the
file if no file already exists because it may exist from the previous,
python guest which automatically generated this file. There are also the
.temp
Systemd provides that functionality itself, internally. We don't want to
use UCF or mark this as a config file. We want to copy the file once on
installation iff it doesn't exist. It is otherwise an 'example' file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
The way that this file is managed has changed as part of this
replacement, and many customers have automatic updates enabled. We chose
not to mark this file as a config file, as we don't want that dialog to
appear. We only ever copy the file into place if it doesn't already
exist, and after that, i
I have looked at this package on a testing image in GCE. The instance
configs file has been shipped differently in this package vs ours - here
you are shipping it as /etc/defaults/instance_configs.cfg, we ship to
/usr/share/google-guest-agent/instance_configs.cfg
There are two problems with this c
