I reran the Xenial verification process and found that this proposed
package does not change the behavior; that is, with the proposed
package, pro services are still enable on first boot. Upon further
investigation, I found that the version of cloud-init in xenial is
After some further investigation it seems that this bug does not occur
in AWS (since the available pro image does not include the affected
packages) and testing is not possible in Azure due to their image
registration policies. Please let me know if the verification can be
approved with solely
We do not publish GCP pro images for mantic so the bug does occur there,
hence there is no validation for mantic GCP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059952
Title:
pro sometimes runs
Xenial Validation GCP:
$ gcloud compute instances create pro-order-bug --image testing-
ubuntu-1604-xenial-v20240417 --image-project ubuntu-catred --metadata-
from-file=user-data=userdata.yaml --zone us-central1-a
catred@pro-order-bug:~$ apt-cache policy ubuntu-pro-client
ubuntu-pro-client:
Bionic Validation GCP:
$ gcloud compute instances create pro-order-bug --image testing-
ubuntu-1804-bionic-v20240417 --image-project ubuntu-catred --metadata-
from-file=user-data=userdata.yaml --zone us-central1-a
catred@pro-order-bug:~$ apt-cache policy ubuntu-pro-client
ubuntu-pro-client:
Focal Validation GCP:
$ gcloud compute instances create pro-order-bug --image testing-
ubuntu-2004-focal-v20240416 --image-project ubuntu-catred --metadata-
from-file=user-data=userdata.yaml --zone us-central1-a
catred@pro-order-bug:~$ apt-cache policy ubuntu-pro-client
ubuntu-pro-client:
Jammy Validation GCP:
$ gcloud compute instances create pro-order-bug --image testing-
ubuntu-2204-jammy-v20240416 --image-project ubuntu-catred --metadata-
from-file=user-data=userdata.yaml --zone us-central1-a
catred@pro-order-bug:~$ apt-cache policy ubuntu-pro-client
ubuntu-pro-client:
** Description changed:
[ Impact ]
Currently, the Pro client support a daemon named ubuntu-advantage.service that
performs two actions:
* Actively look for Pro licenses on Azure and GCP images to perform an
auto-attach
* Retry auto-attach on Pro images if that command fails on boot
Test plan details:
Build image that pulls pro from -proposed. If necessary, I can expand
on the exact bartender command/changes made. Upload and register the
image with a cloud (GCP will be used for testing since that was where I
first observed the bug and could reliably reproduce).
We also see this bug running do-release-upgrade on GCE base VMs. Prior
to running the upgrade and after running the upgrade, postfix is not
installed:
catred@jammy-to-noble-upgrade-arm64:~$ dpkg --no-pager --list postfix
dpkg-query: no packages found matching postfix
If I create a second SSH
** Changed in: livecd-rootfs (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060558
Title:
AppArmor profile `unconfined_restrictions` missing for
Patch for updating the changelog to cover the added function as well as
the new apparmor directory
** Patch added: "LP2059730.patch"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789/+attachment/5760382/+files/LP2059730.patch
--
You received this bug notification because
Patch for updating the changelog to cover the added function as well as
the new apparmor directory
** Patch added: "LP2059730.patch"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2059730/+attachment/5760381/+files/LP2059730.patch
--
You received this bug notification because
> Why the patch in https://bugs.launchpad.net/ubuntu/+source/google-
guest-agent/+bug/2057965/comments/5 and Impact description order gga
after cloud-final.service but the merged (temporal) cpc_packaging.extra
MRs order gga after cloud-config.service?
cloud-final.service runs after
** Description changed:
[ Impact ]
In certain situations (consistently with ubuntu-pro=31.2 and cloud-
init=23.4.4), cloud-config.service has not completed before google-
startup-scripts.service runs. This can cause startup scripts that rely
on apt to fail, as cloud-init is
** Description changed:
+ [ Impact ]
+
+ In certain situations (consistently with ubuntu-pro=31.2 and cloud-
+ init=23.4.4), cloud-config.service has not completed before google-
+ startup-scripts.service runs. This can cause startup scripts that rely
+ on apt to fail, as cloud-init is
I believe the attached patch should fix this issue.
** Patch added: "0006-order-startup-scripts-after-cloud-final.patch"
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2057965/+attachment/5756329/+files/0006-order-startup-scripts-after-cloud-final.patch
--
You received
We are seeing similar failures across older images (mantic and earlier)
but not in noble, perhaps because noble is using cloud-init 24.1 (which
runs faster due to not waiting on snap seeding). However, even in
noble, we don't see cloud-config.service in the critical chain:
Public bug reported:
New GCP dailies are failing startup-script tests, due to network not
being fully set up when startup scripts are run. The failure can be
reproduced as follows:
Using startup_script.sh:
#!/bin/bash
cp /etc/apt/sources.list /tmp/startup-sources.list
$ gcloud compute
19 matches
Mail list logo
