### Questing testing ###
[Note that the bug in question was not seen in GCP questing 25.10
images, so this test is to check there are no regressions]
* Created a new questing GCP image with `snapd` installed from `-proposed` in
the image build:
```
ubuntu@cit-questing-snapd-sru:~$ dpkg -s snapd
Hi, I've also encountered this problem. I've attached a patch with a
utf-8 character in a filename which gives the same "buffer overflow"
error.
I believe this is resolved in diffstat 1.68, but I'm experiencing this
with diffstat_1.66-1build1 from Noble. It would be good to get an
updated packag
** Description changed:
Following on from previous similar package update requests @ LP:
#2096657, LP: #2084496, LP: #2073161, LP: #2064580 and LP: #2020762,
this bug is a request to update the google-osconfig-agent package to the
upstream version `20250416.02` @
https://github.com/Googl
[questing] debdiff of 20250328.00-0ubuntu2.dsc vs.
20250501.00-0ubuntu1.dsc
** Patch added: "debdiff for questing"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/2113788/+attachment/5883413/+files/questing-20250328-vs-20250501-dsc.diff
--
You received this bug noti
[questing] debdiff of 20250115.01-0ubuntu2.dsc vs.
20250416.02-0ubuntu1.dsc
** Patch added: "debdiff for questing"
https://bugs.launchpad.net/ubuntu/+source/google-osconfig-agent/+bug/2113875/+attachment/5883415/+files/questing-20250115-vs-20250416-dsc.diff
--
You received this bug notifica
[questing] debdiff of 20250116.00-0ubuntu2.dsc vs.
20250506.01-0ubuntu1.dsc
** Patch added: "debdiff for questing"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2113792/+attachment/5883414/+files/questing-20250116-vs-20250506-dsc.diff
--
You received this bug notificatio
** Changed in: google-osconfig-agent (Ubuntu)
Assignee: (unassigned) => Chloé Smith (kajiya)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2113875
Title:
Please update to 20250416.02
Public bug reported:
Following on from previous similar package update requests @ LP:
#2096657, LP: #2084496, LP: #2073161, LP: #2064580 and LP: #2020762,
this bug is a request to update the google-osconfig-agent package to the
upstream version `20250416.02` @
https://github.com/GoogleCloudPlatfor
Upload is queued in jammy-proposed which fixes a jammy-only debhelper
incompatibility with reloated systemd units/services.
Installs of 25.1.2-0ubuntu0~22.04.2 show systemd units correctly enabled
on jammy on clean install of cloud-init package. This subsequent upload
may resolve some of the conce
** Tags added: regression-update
** Description changed:
+ Does not affect: Noble, Oracular, Questing
+
In cloud-init 25.1.2, changed systemd-related packaging from /lib TO /usr/lib
which was suggested by lintian packaging warnings.[1]
This change though is incompatible with debhelper v
Uploaded proposed fix to Jammy-proposed queue here.
https://launchpadlibrarian.net/798605633/cloud-
init_25.1.2-0ubuntu0~22.04.1_25.1.2-0ubuntu0~22.04.2.diff.gz
This reverts just the specific commit which relocated systemd units from
/lib -> /usr/lib.
This resulting package created now appropriat
Upload queued for Jammy with this revert fix. cloud-init version
25.1.2-0ubuntu0~22.04.2 Should fix enabling all cloud-init systemd units
on Jammy. It is currently up for review at
https://launchpadlibrarian.net/798605633/cloud-
init_25.1.2-0ubuntu0~22.04.1_25.1.2-0ubuntu0~22.04.2.diff.gz
--
You
Related to the comment #21 in this thread. We can see a debhelper
incompatibility with changes in cloud-init from upstream in 25.1.2 that
only affects Jammy.
We are actively working this cloud-init Jammy-only fix here
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2113797 and a
point r
Thank you Michael for filing this bug and improving cloud-init.
It appears debhelper postinstall scripts injected into cloud-init
package builds didn't support a directory change in our packaging and
the resulting binary deb never enabled cloud-init services. We'll back
out that directory change o
*** This bug is a duplicate of bug 2113797 ***
https://bugs.launchpad.net/bugs/2113797
Closing this in favor of customer-filed bug:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2113797
** This bug has been marked a duplicate of bug 2113797
cloud-init 25.1.2 on Jammy not runni
*** This bug is a duplicate of bug 2113797 ***
https://bugs.launchpad.net/bugs/2113797
Public bug reported:
In cloud-init 25.1.2, changed systemd-related packaging from /lib TO /usr/lib
which was suggested by lintian packaging warnings.[1]
This change though is incompatible with debhelper ve
mentioned in the
following MRE:
https://wiki.ubuntu.com/google-guest-agent-Updates
This package is only used on AMD64 and ARM64 but is built for all
available architectures.
[0]: https://github.com/GoogleCloudPlatform/cloud-image-tests
** Affects: google-guest-agent (Ubuntu)
Importance: Undeci
compute-image-packages (Ubuntu)
Importance: Undecided
Assignee: Chloé Smith (kajiya)
Status: New
** Changed in: gce-compute-image-packages (Ubuntu)
Assignee: (unassigned) => Chloé Smith (kajiya)
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Description changed:
Bug
The latest release of gce-compute-packages (a.k.a google-compute-engine)
- drops a config file into /etc/systemd/resolved.conf.d that add a
+ drops a config file into /etc/systemd/resolved.conf.d that adds a
`.local` prefix to the FQDN.
ubuntu@
Public bug reported:
Bug
The latest release of gce-compute-packages (a.k.a google-compute-engine)
drops a config file into /etc/systemd/resolved.conf.d that add a
`.local` prefix to the FQDN.
ubuntu@jammy-lp:~$ hostname -f
jammy-lp.local
[Impact]
This will likely affect users wi
I've also observed that the system crashes now when it never used to do
so. I've had to disable the monitor from the configuration unless I need
a third monitor. Got any more ideas?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Verification on both the Canonical (CPC) side and Google side is
finished. The candidate images passed all our internal (CTF) tests and
all of the Google-owned tests (CIT). We've just been given the final
sign-off from Google and are good to go.
--
You received this bug notification because you a
(Copied from LP: #2106629) Verification on both the Canonical (CPC) side
and Google side is finished. The candidate images passed all our
internal (CTF) tests and all of the Google-owned tests (CIT). We've just
been given the final sign-off from Google and are good to go.
--
You received this bug
Also please see comment #2 for the specific cloud-init valiation
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-
packages/+bug/2106629/comments/2
** Tags removed: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-noble verification-needed-or
Verification on both the Canonical (CPC) side and Google side is
finished. The candidate images passed all our internal (CTF) tests and
all of the Google-owned tests (CIT). We've just been given the final
sign-off from Google and are good to go.
** Tags removed: verification-needed verification-ne
Verification on both the Canonical (CPC) side and Google side is
finished. The candidate images passed all our internal (CTF) tests and
all of the Google-owned tests (CIT). We've just been given the final
sign-off from Google and are good to go.
** Tags removed: verification-needed verification-ne
I have just completed the upgrade during which I simply closed the
erroneous window and allowed the upgrader to proceed. All went well,
upgrade completed successfully.
Messages in the log:
bruce@corunastylis:~$ grep "failed to mark" /var/log/dist-upgrade/main.log
2025-05-17 09:28:42,522 ERROR f
In my case the upgrader certainly appeared seemed able to move forward.
I chose instead to cancel the upgrade and report the error.
So, should I
a) install "ubuntu-desktop" and then retry the upgrade
b) simply retry and continue when that message appears
c) something else
I really don't want to
Nick,
Re my duplicate report #2110755, I installed the regular desktop from a
24.10 ISO last year. As "apt list" says
bruce@corunastylis:~$ apt list | grep ubuntu-desktop-minimal
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
edubuntu-desktop-minimal/oracular 24
Public bug reported:
Upgrading from 24.10 to 25.04 using Software Updater. Received the
message "It was impossible to install a required package".
/var/log/dist-upgrade/main.log ends with
2025-05-15 10:17:06,035 DEBUG Installing linux-sysctl-defaults
2025-05-15 10:17:06,075 DEBUG none of the '['u
Upstream commit landed http://github.com/canonical/cloud-
init/commit/dc6a6817d6ec43a678a377c3b13e50ec0b42d068 removing
deprecation message for the custom fs_label.
We can publish this fix to questing this week and it will be included in
cloud-init official upstream 15.2 which will also be SRU'd b
Fresh deploy of 24.04 to a node via MAAS 3.6 and I'm not seeing cloud-
init 25.2 as available.
Not seeing that version of cloud-init is available for anything below
Ubuntu 25: https://launchpad.net/ubuntu/+source/cloud-init
Is this fixed in other versions of cloud-init?
We're able to reproduce d
None of the on-screen menus for the monitors are auto. There is no auto
setting in fact.
• monitor 1 is set to DP (lower left),
• monitor 2 is set to DP (lower right),
• monitor 3 is set to HDMI1.4 (center top)
It will only dpms off if I turn off monitor 3 (HDMI1.4). My mobo has 3
monitor connect
Olivier,
Thanks for the communication! I think the issue was a prior version of
Ubuntu on the drive. I reformatted the drive and was able to install it.
Stephen
On Wed, Apr 16, 2025, 2:30 AM Olivier Gayot <2107...@bugs.launchpad.net>
wrote:
> Hello,
>
> It is not obvious to me yet that this is an
just wanted to put my 2 pence worth in here, we are also experiencing
the same issue
vmware workstation pro 17.6.3 and ubuntu 24.04.2, meshcentral/meshagent
HOWEVER our workaround is to simply disable the network test and it carries on
like nothing happened,
BUT you don't get any network output
Relevant longs from broken Jammy 24.4.1 versus working Jammy 24.4.0
=== Working Jammy cloud-init 24.4.0 (performs retry after 1 second wait)
2025-04-11 22:41:46,944 - url_helper.py[DEBUG]: Calling
'http://172.0.2.15:5248/MAAS/metadata/2012-03-01/meta-data/instance-id' failed
[6/120s]: request
I'm marking this particular tracking bug as invalid as cloud-init
doesn't typically reflect each individual bugfix from github into
launchpad for fixes included in the upcoming SRU of 15.2. If either I
have misunderstood this issue, or if this particular bug request
warrants more attention and prio
Thank you for filing this bug and improving cloud-init.
I'm confused about the intent of this tracking bug as debdiffs into
stable releases are unnecessary as separate work efforts because cloud-
init adheres to the SRU policy https://wiki.ubuntu.com/CloudinitUpdates
where we SRU latest release of
d in: gce-compute-image-packages (Ubuntu Oracular)
Status: New => In Progress
** Changed in: gce-compute-image-packages (Ubuntu Focal)
Assignee: (unassigned) => Chloé Smith (kajiya)
** Changed in: gce-compute-image-packages (Ubuntu Jammy)
Assignee: (unassigned) => C
** Changed in: gce-compute-image-packages (Ubuntu Focal)
Assignee: (unassigned) => Chloé Smith (kajiya)
** Changed in: gce-compute-image-packages (Ubuntu Jammy)
Assignee: (unassigned) => Chloé Smith (kajiya)
** Changed in: gce-compute-image-packages (Ubuntu Noble)
As
Created with $ debdiff ../gce-compute-image-
packages_20241010.00-0ubuntu1~22.04.0.dsc ../gce-compute-image-
packages_20250328.00-0ubuntu1~22.04.0.dsc >
../jammy-20241010-vs-20250328-dsc.diff
** Patch added: "jammy-20241010-vs-20250328-dsc.diff"
https://bugs.launchpad.net/ubuntu/+source/gce-co
$ debdiff ../gce-compute-image-packages_20241010.00-0ubuntu1~24.04.0.dsc
../gce-compute-image-packages_20250328.00-0ubuntu1~24.04.0.dsc > ../src-
noble-20241010-vs-20250328-dsc.diff [where the build .dsc is from the
source repo]
** Patch added: "debdiff for noble"
https://bugs.launchpad.net/ub
$ debdiff ../gce-compute-image-packages_20241010.00-0ubuntu1~20.04.0.dsc
../gce-compute-image-packages_20250328.00-0ubuntu1~20.04.0.dsc > ../src-
focal-20241010-vs-20250328-dsc.diff [where the build .dsc is from the
source repo]
** Patch added: "debdiff for focal"
https://bugs.launchpad.net/ub
Created with $ debdiff ../gce-compute-image-
packages_20241010.00-0ubuntu1~24.04.0.dsc ../gce-compute-image-
packages_20250328.00-0ubuntu1~24.04.0.dsc >
../noble-20241010-vs-20250328-dsc.diff
** Patch added: "debdiff for noble"
https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packag
Public bug reported:
DPMS off worked fine when I only had two monitors. I recently added a
third monitor to my setup. When locking the screen or timing out, the
monitor turns off as expected via DPMS, but then it wakes up within
seconds. They go back and forth blinking on and off for a while and t
Created via $ debdiff ../gce-compute-image-
packages_20241010.00-0ubuntu1~24.10.0.dsc ../gce-compute-image-
packages_20250328.00-0ubuntu2~24.10.0.dsc > ../src-
oracular-20241010-vs-20250328.00-0ubuntu2-dsc.diff
** Description changed:
In https://bugs.launchpad.net/ubuntu/+source/gce-compute-ima
Created via $ debdiff ../gce-compute-image-
packages_20241010.00-0ubuntu1~24.04.0.dsc ../gce-compute-image-
packages_20250328.00-0ubuntu2~24.04.0.dsc > ../src-
noble-20241010-vs-20250328.00-0ubuntu2-dsc.diff
** Patch added: "debdiff for noble"
https://bugs.launchpad.net/ubuntu/+source/gce-comp
Created via $ debdiff ../gce-compute-image-
packages_20241010.00-0ubuntu1~20.04.0.dsc ../gce-compute-image-
packages_20250328.00-0ubuntu2~20.04.0.dsc > ../src-
focal-20241010-vs-20250328.00-0ubuntu2-dsc.diff
** Patch added: "debdiff for focal"
https://bugs.launchpad.net/ubuntu/+source/gce-comp
Created via $ debdiff ../gce-compute-image-
packages_20241010.00-0ubuntu1~22.04.0.dsc ../gce-compute-image-
packages_20250328.00-0ubuntu2~22.04.0.dsc > ../src-
jammy-20241010-vs-20250328.00-0ubuntu2-dsc.diff
** Patch added: "debdiff for jammy"
https://bugs.launchpad.net/ubuntu/+source/gce-comp
Marked the in-life suites as "Incomplete" in favour of LP: #2106629
** Changed in: gce-compute-image-packages (Ubuntu Focal)
Status: New => Incomplete
** Changed in: gce-compute-image-packages (Ubuntu Noble)
Status: New => Incomplete
** Changed in: gce-compute-image-packages (Ubunt
Confirmed that the proposed changes do indeed fix the issue:
# Created via `gcloud compute instances create current-plucky --image-project
ubuntu-os-cloud-devel --image daily-ubuntu-2504-plucky-amd64-v20250409
--metadata-from-file user-data=hostname.yaml`
ubuntu@current-plucky:~$ hostname
c
`$ debdiff ../gce-compute-image-packages_20250328.00-0ubuntu1.dsc
../gce-compute-image-packages_20250328.00-0ubuntu2.dsc >
../plucky-20250328~ubuntu1-vs-20250328~ubuntu2-dsc.diff` where `gce-
compute-image-packages_20250328.00-0ubuntu2.dsc` is built from MP:
#484106
** Patch added: "debdiff for pl
Created with `$ debdiff ../gce-compute-image-
packages_20241010.00-0ubuntu1~20.04.0.dsc ../gce-compute-image-
packages_20250328.00-0ubuntu1~20.04.0.dsc > ../src-
focal-20241010-vs-20250328-dsc.diff` (MP: #484106)
** Patch added: "debdiff for plucky"
https://bugs.launchpad.net/ubuntu/+source/gc
In the past I've tried to disable audio as Google was suggesting that
was one of the issues. No joy. My computer only has the ports it has. I
believe it was 2xHDMI 1xDP. I'm using the MOBO video (no special card).
I'm not sure what the first item "Configure the monitor (in its own
menus) to not aut
$ debdiff ../gce-compute-image-packages_20241010.00-0ubuntu1~22.04.0.dsc
../gce-compute-image-packages_20250328.00-0ubuntu1~22.04.0.dsc > ../src-
jammy-20241010-vs-20250328-dsc.diff [where the build .dsc is from the
source repo]
** Patch added: "debdiff for jammy"
https://bugs.launchpad.net/ub
$ debdiff ../gce-compute-image-packages_20241010.00-0ubuntu1~24.10.0.dsc
../gce-compute-image-packages_20250328.00-0ubuntu1~24.10.0.dsc > ../src-
oracular-20241010-vs-20250328-dsc.diff [where the build .dsc is from the
source repo]
** Patch removed: "debdiff for oracular"
https://bugs.launchpa
** Attachment removed: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1872415/+attachment/5353037/+files/CurrentDmesg.txt
** Attachment removed: "Dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1872415/+attachment/5353038/+files/Dependencies.
Created with $ debdiff ../gce-compute-image-
packages_20241010.00-0ubuntu1~20.04.0.dsc ../gce-compute-image-
packages_20250328.00-0ubuntu1~20.04.0.dsc >
../focal-20241010-vs-20250328-dsc.diff
** Patch added: "focal-20241010-vs-20250328-dsc.diff"
https://bugs.launchpad.net/ubuntu/+source/gce-co
Created with $ debdiff ../gce-compute-image-
packages_20241010.00-0ubuntu1~24.10.0.dsc ../gce-compute-image-
packages_20250328.00-0ubuntu1~24.10.0.dsc >
../oracular-20241010-vs-20250328-dsc.diff
** Description changed:
FFe
Please except this version for plucky before the release. catr
Apologies or the noise; Google's upstream naming scheme vs. Ubuntu's
confused me again!
** Tags removed: regression-proposed verification-failed
** Tags added: verification-needed verification-needed-focal
verification-needed-jammy verification-needed-noble verification-needed-oracular
--
You r
Public bug reported:
it fatally crashes every time
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.20
ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-18-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.20.11-0ubuntu82.5
Architecture:
** Changed in: google-osconfig-agent (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106193
Title:
[FFe] Please update to 20250328.00
To manage notifications a
Copying catred's comment here for completeness [0]
> This SRU creates a regression in cloud-init behaviour.
Using the following user_data hostname.yaml:
#cloud-config
manage_etc_hosts: true
hostname: cloudinit1
fqdn: cloudinit2.i9n.cloud-init.io
create_hostname_file: true
On an exi
Thank you TimBishop for the request for logs in comment #39. I can
confirm that latest image manifest[1] contains cloud-init v.
24.4.1-0ubuntu0~22.04.2 which should have the expected fix for the
original traceback seen:
TypeError: OauthUrlHelper._exception_cb() missing 1 required
positional ar
** Description changed:
- FFe
+ Apologies, this bug should have been filed in gce-compute-image-packages
+ (you'd have thought after all this time the different naming schemes
+ would have stuck by now!)
- Please except this version for plucky before the release. catred
- provides good det
kages/+bug/2106195/+attachment/5869359/+files/gce-compute-image-packages-20250107.00-vs-20250328.00.dsc.diff
** Changed in: gce-compute-image-packages (Ubuntu)
Assignee: (unassigned) => Chloé Smith (kajiya)
** Tags added: ubuntu-release
** Tags removed: ubuntu-release
** Tags added: patch
*
Public bug reported:
FFe
Please except this version for plucky before the release. catred
provides good detail here [0], but essentially version
20250107.00-0ubuntu1 in plucky affects cloud-init due to newly included
systemd-networkd hooks. A user attempting to set their hostname via
cloud-i
Copying catred's comment here for completeness [0]
> This SRU creates a regression in cloud-init behaviour.
Using the following user_data hostname.yaml:
#cloud-config
manage_etc_hosts: true
hostname: cloudinit1
fqdn: cloudinit2.i9n.cloud-init.io
create_hostname_file: true
On an exi
Public bug reported:
FFe
Please except this version for plucky before the release. catred
provides good detail here [0] in the relevant bug, but essentially
version 20250107.00-0ubuntu1 in plucky affects cloud-init due to newly
included systemd-networkd hooks. A user attempting to set their
For those reading, the regression mentioned by catred in comment #19
does exist but it pertains to the google-osconfig-agent package. I've
copied these details over to LP: #2096657 (comment #21 [0])
This google-guest-agent version proposed does not have any found
regressions, but as we validate th
** Also affects: maas-cert-server
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2105769
Title:
[UBUNTU 24.04] hardwa
test failure (#5926)
- fix: use program name of netcat as installed by upstream, "nc" (#5933)
(#5933) [Andreas K. Hüttel]
- ci: bump canonical/setup-lxd to version v0.1.2 (#5948)
- feat(cc_chef): Allow change of Chef configuration file (#5925)
[Sean Smith]
- docs: fix typo in gener
Almost a year later and this is still a problem. Any update on a
solution?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061964
Title:
Installation of ubuntu 24.04 raid array not detected
To manag
[focal] .dsc diff of google-guest-agent_20241011.01-0ubuntu1~20.04.1.dsc
vs. google-guest-agent_20250116.00-0ubuntu1~20.04.0.dsc
** Patch added:
"gga-20241011.01-0ubuntu1~20.04.1-vs-20250116.00-0ubuntu1~20.04.0.diff"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2096765/+a
[jammy] .dsc diff of google-guest-agent_20241011.01-0ubuntu1~22.04.0.dsc
vs. google-guest-agent_20250116.00-0ubuntu1~22.04.0.dsc
** Patch added:
"gga-20241011.01-0ubuntu1~22.04.0-vs-20250116.00-0ubuntu1~22.04.0.diff"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2096765/+a
[oracular] .dsc diff of google-guest-
agent_20241011.01-0ubuntu1~24.10.0.dsc vs. google-guest-
agent_20250116.00-0ubuntu1~24.10.0.dsc
** Patch added:
"gga-20241011.01-0ubuntu1~24.10.0-vs-20250116.00-0ubuntu1~24.10.0.diff"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/20967
** Patch added: "google-guest-agent-20240111.01-vs-20250116.00.diff"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2096765/+attachment/5857180/+files/google-guest-agent-20240111.01-vs-20250116.00.diff
--
You received this bug notification because you are a member of Ubuntu
[noble] .dsc diff of google-guest-agent_20241011.01-0ubuntu1~24.04.0.dsc
vs. google-guest-agent_20250116.00-0ubuntu1~24.04.0.dsc
** Patch added:
"gga-20241011.01-0ubuntu1~24.04.0-vs-20250116.00-0ubuntu1~24.04.0.diff"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2096765/+a
** Patch removed:
"osconfig-20240926.03-0ubuntu1~20.04.0-vs-20250115.01-0ubuntu1~20.04.0.diff"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2096765/+attachment/5856322/+files/osconfig-20240926.03-0ubuntu1~20.04.0-vs-20250115.01-0ubuntu1~20.04.0.diff
** Patch removed:
"os
[noble] .dsc diff of google-osconfig-agent-20240926.03-0ubuntu1~24.04.0
vs. google-osconfig-agent-20250115.0-0ubuntu1~24.04.0
** Patch added:
"osconfig-20240926.03-0ubuntu1~24.04.0-vs-20250115.01-0ubuntu1~24.04.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/google-osconfig-agent/+bug
[focal] .dsc diff of google-osconfig-agent-20240926.03-0ubuntu1~20.04.0
vs. google-osconfig-agent-20250115.0-0ubuntu1~20.04.0
** Patch added:
"osconfig-20240926.03-0ubuntu1~20.04.0-vs-20250115.01-0ubuntu1~20.04.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/google-osconfig-agent/+bug
[jammy] .dsc diff of google-osconfig-agent-20240926.03-0ubuntu1~22.04.0
vs. google-osconfig-agent-20250115.0-0ubuntu1~22.04.0
** Patch added:
"osconfig-20240926.03-0ubuntu1~22.04.0-vs-20250115.01-0ubuntu1~22.04.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/google-osconfig-agent/+bug
[oracular] .dsc diff of google-osconfig-
agent-20240926.03-0ubuntu1~24.10.0 vs. google-osconfig-
agent-20250115.0-0ubuntu1~24.10.0
** Patch removed:
"osconfig-20240926.03-0ubuntu1~20.04.0-vs-20250115.01-0ubuntu1~20.04.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/google-osconfig-age
I'm attaching complete boot logs (IPMI SoL output) from three boot
attempts. The failed-sb-enabled.txt and failed-sb-disabled.txt logs are
from attempts that failed with Secure Boot enabled and disabled,
respectively, in the firmware settings. (Both are from attempts to
deploy Ubuntu 22.04.) After
[focal] .dsc diff of google-guest-agent_20241011.01-0ubuntu1~20.04.1.dsc
vs. google-guest-agent_20250116.00-0ubuntu1~20.04.0.dsc
** Patch added:
"osconfig-20240926.03-0ubuntu1~20.04.0-vs-20250115.01-0ubuntu1~20.04.0.diff"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/20967
[jammy] .dsc diff of google-guest-agent_20241011.01-0ubuntu1~22.04.0.dsc
vs. google-guest-agent_20250116.00-0ubuntu1~22.04.0.dsc
** Patch added:
"osconfig-20240926.03-0ubuntu1~22.04.0-vs-20250115.01-0ubuntu1~22.04.0.diff"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/20967
[noble] .dsc diff of google-guest-agent_20241011.01-0ubuntu1~24.04.0.dsc
vs. google-guest-agent_20250116.00-0ubuntu1~24.04.0.dsc
** Patch added:
"osconfig-20240926.03-0ubuntu1~24.04.0-vs-20250115.01-0ubuntu1~24.04.0.diff"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/20967
[oracular] .dsc diff of google-guest-
agent_20241011.01-0ubuntu1~24.10.0.dsc vs. google-guest-
agent_20250116.00-0ubuntu1~24.10.0.dsc
** Patch added:
"osconfig-20240926.03-0ubuntu1~24.10.0-vs-20250115.01-0ubuntu1~24.10.0.diff"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/
** Description changed:
+ = SRU =
+
Following on from similar package update requests @ LP: #2084498, LP:
#2073163 and LP: #2040945, this bug is a request to update the google-
guest-agent package to the upstream version `20250116.00` @
https://github.com/GoogleCloudPlatform/guest
[jammy] .dsc diff of gce-compute-image-
packages_20241010.00-0ubuntu1~22.04.0.dsc vs. gce-compute-image-
packages_20250107.00-0ubuntu1~22.04.0.dsc
** Patch added:
"osconfig-20240926.03-0ubuntu1~22.04.0-vs-20250115.01-0ubuntu1~22.04.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/gce-c
[focal] .dsc diff of gce-compute-image-
packages_20241010.00-0ubuntu1~20.04.0.dsc vs. gce-compute-image-
packages_20250107.00-0ubuntu1~20.04.0.dsc
** Patch added:
"osconfig-20240926.03-0ubuntu1~20.04.0-vs-20250115.01-0ubuntu1~20.04.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/gce-c
[noble] .dsc diff of gce-compute-image-
packages_20241010.00-0ubuntu1~24.04.0.dsc vs. gce-compute-image-
packages_20250107.00-0ubuntu1~24.04.0.dsc
** Patch added:
"osconfig-20240926.03-0ubuntu1~24.04.0-vs-20250115.01-0ubuntu1~24.04.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/gce-c
[oracular] .dsc diff of gce-compute-image-
packages_20241010.00-0ubuntu1~24.10.0.dsc vs. gce-compute-image-
packages_20250107.00-0ubuntu1~24.10.0.dsc
** Patch added:
"osconfig-20240926.03-0ubuntu1~24.10.0-vs-20250115.01-0ubuntu1~24.10.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/gc
** Description changed:
+ = SRU =
+
Following on from similar package update requests @ LP: #2084486, LP:
#2073164, LP: #2066314 and LP: #2033061, this bug is a request to update
gce-compute-image-packages to the upstream version `20250107.00` @
https://github.com/GoogleCloudPlatf
[noble] .dsc diff of google-osconfig-agent-20240926.03-0ubuntu1~24.04.0
vs. google-osconfig-agent-20250115.0-0ubuntu1~24.04.0
** Patch added:
"osconfig-20240926.03-0ubuntu1~24.04.0-vs-20250115.01-0ubuntu1~24.04.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/google-osconfig-agent/+bug
[focal] .dsc diff of google-osconfig-agent-20240926.03-0ubuntu1~20.04.0
vs. google-osconfig-agent-20250115.0-0ubuntu1~20.04.0
** Patch added:
"osconfig-20240926.03-0ubuntu1~20.04.0-vs-20250115.01-0ubuntu1~20.04.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/google-osconfig-agent/+bug
[jammy] .dsc diff of google-osconfig-agent-20240926.03-0ubuntu1~22.04.0
vs. google-osconfig-agent-20250115.0-0ubuntu1~22.04.0
** Patch added:
"osconfig-20240926.03-0ubuntu1~22.04.0-vs-20250115.01-0ubuntu1~22.04.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/google-osconfig-agent/+bug
[oracular] .dsc diff of google-osconfig-
agent-20240926.03-0ubuntu1~24.10.0 vs. google-osconfig-
agent-20250115.0-0ubuntu1~24.10.0
** Patch added:
"osconfig-20240926.03-0ubuntu1~24.10.0-vs-20250115.01-0ubuntu1~24.10.0.diff"
https://bugs.launchpad.net/ubuntu/focal/+source/google-osconfig-agent
** Description changed:
+ = SRU =
+
Following on from previous similar package update requests @ LP:
#2084496, LP: #2073161, LP: #2064580 LP: #2020762 and LP: #1996735, this
bug is a request to update the google-osconfig-agent package to the
upstream version `20250115.01` @
http
d in: gce-compute-image-packages (Ubuntu Oracular)
Status: New => In Progress
** Changed in: gce-compute-image-packages (Ubuntu Focal)
Assignee: (unassigned) => Chloé Smith (kajiya)
** Changed in: gce-compute-image-packages (Ubuntu Jammy)
Assignee: (unassigned) => C
1 - 100 of 3250 matches
Mail list logo
