This bug was fixed in the package google-guest-agent -
20220104.00-0ubuntu1
---
google-guest-agent (20220104.00-0ubuntu1) jammy; urgency=medium
* New upstream version 20220104.00. (LP: #1959392)
- Use IP address for calling the metadata server. (#116)
- Debug logging.
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.
** Changed in: google-guest-agent (Ubuntu Hirsute)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
netplan.io (0.103-0ubuntu10) jammy; urgency=medium
* update gbp.conf branch
* Drop d/p/0002-Revert-cli-apply-reload-reconfigure-networkd-instead.patch
This is not needed anymore with systemd v249
* Refresh d/p/0006-netplan-set-make-it-possible-to-unset-a-whole-devtyp.patch
* Add
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: netplan.io (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Title:
This bug was fixed in the package cloud-init -
21.3-1-g6803368d-0ubuntu1~18.04.4
---
cloud-init (21.3-1-g6803368d-0ubuntu1~18.04.4) bionic; urgency=medium
* cherry-pick 9c147e83: Allow disabling of network activation (SC-307)
(#1048) (LP: #1938299)
-- James Falcon Thu, 07
This bug was fixed in the package cloud-init -
21.3-1-g6803368d-0ubuntu1~20.04.4
---
cloud-init (21.3-1-g6803368d-0ubuntu1~20.04.4) focal; urgency=medium
* cherry-pick 9c147e83: Allow disabling of network activation (SC-307)
(#1048) (LP: #1938299)
-- James Falcon Thu, 07
This bug was fixed in the package cloud-init -
21.3-1-g6803368d-0ubuntu1~21.04.4
---
cloud-init (21.3-1-g6803368d-0ubuntu1~21.04.4) hirsute; urgency=medium
* cherry-pick 9c147e83: Allow disabling of network activation (SC-307)
(#1048) (LP: #1938299)
-- James Falcon Thu, 07
** Description changed:
=== Begin SRU Template ===
[Impact]
In PR #919 (81299de), we refactored some of the code used to bring up
networks across distros. Previously, the call to bring up network interfaces
during 'init' stage unintentionally resulted in a no-op such that network
** Description changed:
=== Begin SRU Template ===
[Impact]
In PR #919 (81299de), we refactored some of the code used to bring up
networks across distros. Previously, the call to bring up network interfaces
during 'init' stage unintentionally resulted in a no-op such that network
** Description changed:
=== Begin SRU Template ===
[Impact]
In PR #919 (81299de), we refactored some of the code used to bring up
networks across distros. Previously, the call to bring up network interfaces
during 'init' stage unintentionally resulted in a no-op such that network
From Google internal communication on this bug: "I did a manual test of
this fix and it seems to work as expected. We'll also get signal from
the daily images when they include this change."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: netplan.io (Ubuntu Bionic)
Status: New => Won't Fix
** Changed in: netplan.io (Ubuntu Focal)
Status: New => Won't Fix
** Changed in: netplan.io (Ubuntu Hirsute)
Status: New => Won't Fix
** Changed in: netplan.io (Ubuntu Impish)
Status: New => Won't Fix
Yes indeed only releases later than Impish will support this
functionality in netplan as it depends on some fixes in systemd v249.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Title:
Confirmed that Impish daily image builds on GCP are unblocked and
include the necessary fix to prevent `netplan apply` from being invoked
by cloud-init. This is a stop gap solution until we can publish a
release of google-guest-agent.service which declares a "RequiredBy="
relationship with
Thanks Lukas.
Is the expectation then that only releases later than Impish will
support this functionality?
If that is the case, we will continue with instrumenting a workaroud for
cloud-init to avoid calling `netplan apply` on google to avoid
triggering this symptom until we can ensure
From a netplan POV this has already been changed upstream as part of
https://github.com/canonical/netplan/pull/200
I.e. the "systemctl stop/start systemd-networkd.service" have been
replaced by "networkctl reload/reconfigure" calls instead. Due to an
incompatibility with systemd v247 that change
To clarify the actual root cause here and reflect it back to this
original bug.
google-guest-agent defines a `PartOf=` relationship with systemd-
networkd.service[1]. This relationship means that if systemd-
networkd.service is either stopped, google-guest-agent.service gets
stopped. When
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
Thank you, James, for doing the testing.
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done-bionic verification-done-focal
verification-done-hirsute
--
You received this bug notification because you are a member
Attach file integration_test_results.tar.gz. These tests show the issue
fixed in B, F, and H
** Attachment added: "integration_test_results.tar.gz"
https://bugs.launchpad.net/bugs/1938299/+attachment/5531668/+files/integration_test_results.tar.gz
--
You received this bug notification
Hello Sean, or anyone else affected,
Accepted cloud-init into hirsute-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/21.3-1-g6803368d-0ubuntu1~21.04.4 in a few hours, and then in the
-proposed repository.
Please help us by testing this
I seem to have encountered the same or similar issue in ubuntu
focal/20.04 when using the image ubuntu-minimal-2004-focal-v20210928 on
GCP. Creating a new custom GCP image using this as the base image and
running:
apt-get update
apt-get upgrade -y
created a custom image that exhibited the same
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: google-guest-agent (Ubuntu Hirsute)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu Hirsute)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: google-guest-agent (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: google-guest-agent (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: google-guest-agent (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
This bug was fixed in the package cloud-init - 21.3-1-g6803368d-0ubuntu3
---
cloud-init (21.3-1-g6803368d-0ubuntu3) impish; urgency=medium
* cherry-pick 9c147e83: Allow disabling of network activation (SC-307)
(#1048) (LP: #1938299)
* cherry-pick 612e3908: Add
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ In PR #919 (81299de), we refactored some of the code used to bring up
networks across distros. Previously, the call to bring up network interfaces
during 'init' stage unintentionally resulted in a no-op such that network
Upstream PR with a fix for this behavior on GCP
https://github.com/canonical/cloud-init/pull/1048
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Title:
Unable to SSH Into Instance when
For this google-guest-agent task, the daemon itself should probably be a
bit more resilient in the face of a `netplan apply` which could be
invoked by any admin manipulating network configuration and will
teardown any dhclient connections resulting in a dead google-guest-
agent.service from that
This is the same symptom as a GCP issue raised.
The following commit[1] introduced this change in behavior for cloud-
init by correcting an bug in the behavior of cloud-init which didn't
apply networking changes in cloud-init "init" stage after writing files.
This version of cloud-init 2.3.
** Tags added: impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Title:
Unable to SSH Into Instance when deploying Impish 21.10
To manage notifications about this bug go to:
** Tags removed: rls-ii-incoming
** Also affects: cloud-init (Ubuntu Impish)
Importance: Undecided
Status: Incomplete
** Also affects: google-guest-agent (Ubuntu Impish)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
** Tags added: fr-1631
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Title:
Unable to SSH Into Instance when deploying Impish 21.10
To manage notifications about this bug go to:
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Title:
Unable to SSH Into Instance when deploying Impish 21.10
To manage notifications about this bug go to:
Chad and I investigated this issue together. To summarize, the google-
guest-agent.service appears to be properly enabled with the proper
systemd symlinks, but it is not running on first boot. We can find no
logs anywhere about an attempt to start the service or about any error
with the service.
A note as well, a 2nd reboot of these Hirsute "broken" images will end
up properly activating google-guest-agent across that reboot. So, for
some reason the unit appears installed and enabled but not running.
# after reboot
$ systemctl status google-guest-agent.service
●
I found no Ordering cycle breaks that would imply that the google-guest-
agent got "unloaded" from the primary boot target objectives in
journalctl.
Attached is the journalctl from a machine that was only launched and
rebooted 1. After the reboot you can egrep 'GCE|gpasswd' to see the
operations
Ok, so on working images (v20200719 or earlier), google-guest-
agent.service is running. On 20210720 or later that service is not
included in the systemd boot targets for some reason.
I've checked for system ordering dependency issues which would have
disabled the g-g-a.service on the "broken"
Thanks for this bug Sean Feole and the additional reproducer context
fginther. If either of you have cloud-init collect-logs tar.gz from that
affected system it'd give us a firm grasp on what fell over here. I'll
try reproducing this tomorrow, but I can confirm that launching said
image from the
[Summary]
I believe this problem is related to a change in behavior in cloud-init version
21.2-43-g184c836a-0ubuntu1 due to comparing two different daily impish images
before and after this update.
The problem appears in a gcp account which currently has multple global
sshkeys associated with
44 matches
Mail list logo
