This bug was fixed in the package ubuntu-advantage-tools - 31.2.3~20.04
---
ubuntu-advantage-tools (31.2.3~20.04) focal; urgency=medium
* Backport new upstream release to focal (LP: #2059952)
ubuntu-advantage-tools (31.2.3) noble; urgency=medium
* daemon: wait for
This bug was fixed in the package ubuntu-advantage-tools - 31.2.3~18.04
---
ubuntu-advantage-tools (31.2.3~18.04) bionic; urgency=medium
* Backport new upstream release to bionic (LP: #2059952)
ubuntu-advantage-tools (31.2.3) noble; urgency=medium
* daemon: wait for
This bug was fixed in the package ubuntu-advantage-tools - 31.2.3~22.04
---
ubuntu-advantage-tools (31.2.3~22.04) jammy; urgency=medium
* Backport new upstream release to jammy (LP: #2059952)
ubuntu-advantage-tools (31.2.3) noble; urgency=medium
* daemon: wait for
This bug was fixed in the package ubuntu-advantage-tools - 31.2.3~23.10
---
ubuntu-advantage-tools (31.2.3~23.10) mantic; urgency=medium
* Backport new upstream release to mantic (LP: #2059952)
ubuntu-advantage-tools (31.2.3) noble; urgency=medium
* daemon: wait for
** Tags added: verification-done-mantic
--
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 before cloud-config.service
To manage notifications about this bug go to:
I am adding the test results for Mantic. Those tests confirm that the
daemon doesn't run on Mantic, which makes this release unaffected by
this issue.
** Attachment added: "mantic-test-results.tar.xz"
The versions used for these updates were expecting a mantic update as
well, to have an upgrade path. But we can't release mantic without any
testing whatsoever.
Even if we don't have gcp images for mantic, the right version of cloud-
init is there and available, so we could hit the bug there as
Thanks for this extra verification.
Since xenial is then not affected by this bug, and there is another
upcoming ubuntu-advantage-tools v32 SRU which, among many other changes,
includes this same fix, let's not release v31.2.3~16.04 into xenial.
This avoids an unnecessary update to xenial users,
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
I think the xenial verification at comment #14 was not complete,
because, as we can see in the NOTICES section, the attaching was still
going on, so the output of "pro status" does not yet show if services
were auto-enabled or not, i.e., we don't have the STATUS column in that
output.
** Tags
** Tags added: verification-done-xenial
--
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 before cloud-config.service
To manage notifications about this bug go to:
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
Looks good, but please also include:
- azure run (to at least show it's still working, if you cannot reproduce the
bug there easily)
- what a test failure looks like, according to this plan
+1 to go ahead and update the bug description's [test plan].
--
You received this bug notification
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).
> However, CPC is already aware of this issue and will help us creating
the test plan here.
I understand CPC can hit this bug quite frequently in the affected cloud
images, so releasing this SRU to updates is conditional on an actual
test plan being better described by them, and followed.
**
This bug was fixed in the package ubuntu-advantage-tools - 31.2.3
---
ubuntu-advantage-tools (31.2.3) noble; urgency=medium
* daemon: wait for cloud-init.service to fully activate (LP: #2059952)
-- Lucas Moura Tue, 02 Apr 2024 10:13:32
-0300
** Changed in:
** 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
** Changed in: ubuntu-advantage-tools (Ubuntu)
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/2059952
Title:
pro sometimes runs before cloud-config.service
To
** 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
** 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
** Description changed:
[ Impact ]
- If the user has specified custom setup for the Pro client through cloud-init,
there is a high chance that this setup will be ignored.
+ Currently, the Pro client support a daemon named ubuntu-advantage.service that
+ performs two actions:
- This happened
** Merge proposal linked:
https://code.launchpad.net/~lamoura/ubuntu/+source/ubuntu-advantage-tools/+git/ubuntu-advantage-tools/+merge/463510
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059952
** Description changed:
- We have recently updated the Pro to not strictly run after cloud-
- config.service. If cloud-config.service has not been started when pro
- runs, it can complete before cloud-config.service begins and thus the
- user-specificed pro configuration will be ignored since the
29 matches
Mail list logo
