Hello, Paul
Thanks for reaching out and reporting this issue.
The Pro Client seems to be doing what it is supposed to do, so I am adding
Livepatch people for further help.
** Also affects: canonical-livepatch-client
Importance: Undecided
Status: New
** Information type changed from Pri
This bug is reproducible in 25.04 with php8.4 too.
** Changed in: shtool (Ubuntu)
Assignee: (unassigned) => Renan Rodrigo (renanrodrigo)
** Changed in: shtool (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100719
Title:
pwmconfig could suggest sensors-detect when no pwm-capable kernel
modules are found
To manage not
If the new SRU (ubuntu3) carries this patch, then you don't need to touch this
one.
I checked and the new version got accepted into -proposed already, so it
supersedes the previous version there (this SRU).
There is no harm in removing the tag though - this version is not in
-proposed anymore so
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098484
Title:
Pkinit fails with invalid argument
To manage notifications about this bug go to:
https://bugs.launc
Hello, @shadowlmd
I'm trying to reproduce this bug.
I tested this version of postfix with a simple configuration on
different clouds, but I don't have access to Oracle cloud at the moment,
so this may be indeed Oracle-specific.
I see you have postfix version 3.6.4-1ubuntu1.3, and you mentioned
a
Hello, James, thanks for reaching out
Unfortunately I would need more details to help you further:
- What is the context of this bug? Enabling overlayroot where, how?
- Which Ubuntu release are you running?
- What are the versions of the involved packages? Was there some upgrade for
this bug to h
buntu-advantage-tools (Ubuntu)
Assignee: (unassigned) => Renan Rodrigo (renanrodrigo)
** 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.la
** Description changed:
[ Impact ]
- Users running `pro refresh` on a Noble machine will see a warning, saying
that user `_apt` does not have access to the apt-news json.
+ Users running `pro refresh` on a Noble (or later) machine will see a warning,
saying that user `_apt` does not have ac
Hiho @xypron
I have added the missing releases to the landscape resource, and have
confirmed it is now available on plucky, including riscv64 - so after a
`pro refresh` you should see it there. Please let me know if it shows
correctly.
--
You received this bug notification because you are a memb
** Description changed:
+ [ Impact ]
+ See original description for the FTBFS in Plucky.
+
+ The changes that were made to fix this are, as usual, included in the SRUs,
as the Pro Client is shipping the same codebase to all releases.
+ The fix (bumping the C++ standards and changing tests) has t
** Description changed:
- ubuntu-pro-client has an unnecessary dependency on python3-pkg-
- resources, at least grepping the source for pkg_resources doesn't show
- anything. Please remove it.
+ [ Impact ]
+ The Client had an unnecessary dependency on python3-pkg-resources. This was
bringing in m
** Description changed:
- After the most recent upgrade of ubuntu-advantage-tools/ubuntu-pro-
- client (34~22.04), running apt upgrade --simulate (as non-root) prints
- the following:
+ [ Impact ]
+ The Pro Client apt-hook which runs after `apt upgrade` needs root permissions
to write the logs to
** Changed in: ubuntu-pro
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/2070095
Title:
apt_news.py download forced unsandboxed
To manage notifications about this bug g
le livepatch on wsl (GH: #3156)
+ - lxd: allow pro auto-attach to work on a LXD container
+
+ -- Renan Rodrigo Thu, 20 Feb 2025
+ 12:00:14 -0300
+
+ ubuntu-advantage-tools (34.1.3) plucky; urgency=medium
+
+ * apt-hook: set C++ standards version to c++17 for APT 2.9.30 compatibility
+ (LP:
** Description changed:
+ [ Impact ]
+ Due to an implementation detail, the output of `pro help` appears duplicate.
All information is there, but the entries are being added to the output twice
before it's printed.
+ The solution is a tweak to the code to check if an entry was already
considere
** Description changed:
+ [ Impact ]
+
+ Users running `pro refresh` on a Noble machine will see a warning, saying
that user `_apt` does not have access to the apt-news json.
+ This does not affect functionality, but it is undesired for potential
security reasons.
+ This warning is fixed by put
** Summary changed:
- [SRU] ubuntu-advantage-tools (34 -> 35) Xenial, Bionic, Focal, Jammy, Noble
+ [SRU] ubuntu-advantage-tools (34 -> 35) Xenial, Bionic, Focal, Jammy, Noble,
Oracular
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
#1197368) -> ruby-power-assert (transitive)
* ruby-minitest (LP: #894827)
Some have old MIRs, which might need to be refreshed. Or maybe we can
find a a way to drop/avoid the 3 new dependencies from universe?
** Changed in: ruby-test-unit (Ubuntu)
Assignee: Renan Rodrigo (renan
** Also affects: ruby-minitest (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [MIR] ruby-did-you-mean
+ [MIR] ruby3.3 dependencies
** Changed in: ruby-minitest (Ubuntu)
Assignee: (unassigned) => Renan Rodrigo (renanrodrigo)
** Also affects: ruby-test-u
Better late than never, I have set this back to active
The state is "fix committed", as the permanent solution is in the github
repository already
release 35 will close this again
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Fix Released => In Progress
** Changed in: ubuntu-adva
** Merge proposal linked:
https://code.launchpad.net/~renanrodrigo/ubuntu/+source/ubuntu-advantage-tools/+git/ubuntu-advantage-tools/+merge/481542
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098
, but argparse tests fail:
https://launchpadlibrarian.net/776852389/buildlog_ubuntu-plucky-amd64.ubuntu-advantage-tools_34.1.2ubuntu1_BUILDING.txt.gz
** Affects: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided
Assignee: Renan Rodrigo (renanrodrigo)
Status: In Progress
** Ch
** Changed in: ruby-base64 (Ubuntu)
Assignee: Renan Rodrigo (renanrodrigo) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095497
Title:
[MIR] ruby-base64
To man
** Description changed:
+ [Availability]
+ The package ruby-base64 is already in Ubuntu universe.
+ The package ruby-base64 build for the architectures it is designed to work on.
+ It currently builds and works for architectures: amd64 (all)
+ Link to package: https://launchpad.net/ubuntu/+source/
** Merge proposal linked:
https://code.launchpad.net/~renanrodrigo/ubuntu/+source/squid/+git/squid/+merge/481434
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097411
Title:
Merge squid from Deb
This is now 6.13-1 in Debian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097411
Title:
Merge squid from Debian unstable for plucky
To manage notifications about this bug go to:
https://bugs.laun
** Merge proposal linked:
https://code.launchpad.net/~renanrodrigo/ubuntu/+source/pcs/+git/pcs/+merge/481425
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098038
Title:
Merge pcs (again) for pl
** Changed in: squid (Ubuntu Plucky)
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/2097411
Title:
Merge squid from Debian unstable for plucky
To manage notificatio
** Changed in: pcs (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/2098038
Title:
Merge pcs (again) for plucky
To manage notifications about this bug go to:
** Changed in: pcs (Ubuntu)
Assignee: Athos Ribeiro (athos-ribeiro) => Renan Rodrigo (renanrodrigo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098038
Title:
Merge pcs (again) for plu
Hello, wmfinck, thanks for reaching out.
I have looked at the Focal (20.04) crash report you sent, and indeed it does
appear to be the same bug as reported before for Bionic (18.04).
There is still time to get stable release updates (SRUs) for Focal, and
this does look to be a valid bug worth fix
Good to know it works, sorry for the inconvenience
As this is not a bug in the client per se, I am marking it invalid
Please feel free to reach out in case of any problems
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because
Hello, gazoil, thanks for reaching out
Unfortunately we had some instability in the backend servers at this
time. It was resolved, and now everything should be working.
Could you please try to attach again?
If you are attached, running
sudo pro disable livepatch
sudo pro enable livepatch
may be
** Changed in: ruby-json (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178274
Title:
[MIR] ruby-json
To manage notifications about this bug go to:
h
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778959
Title:
error floating point exception
To manage notifications about this bug go to:
https://bugs.launchpad
** Changed in: ruby-did-you-mean (Ubuntu)
Assignee: (unassigned) => Renan Rodrigo (renanrodrigo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556608
Title:
[MIR] ruby-did-you-mean
To man
** Changed in: pcs (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/1178274
Title:
[MIR] ruby-json
To manage notifications about this bug go to:
https://bugs
- ruby-rack-protection, the binary, is built from the ruby-sinatra source
- it's present and installable on plucky
- it has the dependency on ruby-base64, both for the release version and the
proposed version, and now that shows up in both mismatch reports
So I think all is good and this MIR make
** Changed in: ruby-base64 (Ubuntu)
Assignee: (unassigned) => Renan Rodrigo (renanrodrigo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095497
Title:
[MIR] ruby-base64
To man
The reason pointed in bug 1990572 for avoiding the MIR still apply:
- pcs Depends on ruby-json, but also on ruby
- ruby-defaults is 3.3 on devel
- libruby3.3 Provides ruby-json (just like 3.1 and 3.2 really)
I would say the sensible decision here is to patch pcs, removing ruby-json from
the Depen
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070095
Title:
apt_news.py download forced unsandboxed
To manage
Glad to hear that, liuyaqiao!
I am marking this bug closed->invalid for ubuntu-advantage-tools, as the
tool behaves as expected.
Feel free to reach out in case of any doubt or any other issue.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Invalid
--
You received this bug
Yes I have wondered that, in the end livepatch got enabled so at some
point in time the system configuration was ok
uname and os-release are correct - see how lsb-release differs from those.
the immediate solution (which would hopefully make this error go away) is to
set the values in lsb-release
Hello, liuyaqiao
Thanks for reporting this issue.
I am not sure about the Pro support for Kylin, but regardless you should be
able to disable Livepatch and detach the machine. I will bring this to the team
and keep you posted.
--
You received this bug notification because you are a member of Ub
Hello, Martin, thanks for reaching out to us.
Unfortunately, the error you're seeing when trying to install Livepatch is not
caused by the Pro Client.
I will loop the snapd people in so they can help in further debugging.
** Information type changed from Private to Public
** Also affects: snapd
@racb I have set this back to In Progress, as we still want to fix it
"properly" for PP and ship the correct solution to Oracular too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083665
Title:
ub
Well Thanks @vorlon for all clarifications.
After discussion in side channels, we came to the following conclusion:
- a new version, 34.1, was uploaded to Oracular and Oracular only, removing the
dependency line.
I have tested the package without the explicit dependency and everything should
wor
I'm very sorry, I tried to say two things at the same time and it ended
up horrible.
1. We do have setuptools in the build process, and it does *generate*
this code snippet, and that's why we have the dependency.
1. a. This dependency is there because the whole try-importing-and-
falling-back is
Ok, I can remove the dependency, but we still depend on setuptools (which on
its turn depends on python3-pkg-resources).
This triggers a further question, mainly for @vorlon: how will this help with
Oracular?
Please correct me if I'm wrong, but
`apt-rdepends --reverse --state-follow=Installed pyt
The only reference to pkg_resources that we have in the code is seen in
the console scripts generated by setuptools:
```
$ cat /usr/bin/pro
(...)
try:
from importlib.metadata import distribution
except ImportError:
try:
from importlib_metadata import distribution
except Impor
Hello Pierre, thanks for reaching out.
Unfortunately this is a known bug, and it's been there for some months now.
There is nothing we (package maintainers) can do about this - this is a backend
error, and the responsible team is aware and working on it. Progress is being
tracked in:
https://gi
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075337
Title:
[SRU] py3clean fails when using alternate character set
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078614
Title:
pro refresh Failed running command '/snap/bin/canonical-
** Merge proposal unlinked:
https://code.launchpad.net/~renanrodrigo/ubuntu/+source/squid/+git/squid/+merge/472902
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metada
** Description changed:
Apart from the oracular update, which will not require a FFe since there
are no features being introduced here (see the upstream changes section
below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This updat
** Description changed:
Apart from the oracular update, which will not require a FFe since there
are no features being introduced here (see the upstream changes section
below), this bug tracks the following MRE updates for the Squid package:
noble (22.04): Squid 6.10
This updat
** Merge proposal unlinked:
https://code.launchpad.net/~renanrodrigo/ubuntu/+source/squid/+git/squid/+merge/472902
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metada
** Merge proposal linked:
https://code.launchpad.net/~renanrodrigo/ubuntu/+source/squid/+git/squid/+merge/472902
** Changed in: squid (Ubuntu)
Assignee: Athos Ribeiro (athos-ribeiro) => Renan Rodrigo (renanrodrigo)
--
You received this bug notification because you are a member
to capture errors when trying to read this
file and erase it if it is corrupt. The next execution of the timer jobs
will recreate it.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu)
Assignee: (unassigned) =>
Julian is correct - this is not a bug, it is a feature (:
You need root privileges to run apt download / apt changelog.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hello, @musashiii, thanks for reaching out.
Looking at the status file provided, I see the client is attached and
esm-infra, esm-apps and livepatch are enabled.
Could you please elaborate on what is the problem you are facing? It
would be nice to know what commands are you trying to execute, what
The APT News testing for LP: #2069237 all passed, and this is enough to
call verification-done for all releases here.
Just in case, I have executed the CI test using the package from the
archive and checked the failure exists, seeing it pass when using the
package in proposed.
** Description chan
Made small edits to the test case, given that `nala` is not available on
all releases we test on, and we actually want the binary to be different
rather than an alias to reproduce the bug.
After those tweaks, I was able to reproduce the bug when running from
the archive, and to verify that the pro
The Pro Client test suite now contains an integration test that covers
the scenario described in this bug (Pro client's commands run
successfully in a non-utf8 locale).
I have performed the test steps described above for all valid releases,
and was able to see the bug is fixed using the package fr
I removed the mantic-related tag, because this fix already landed there
for the final version and no new SRUs are being done there as it is EOL
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067810
Ti
This bug has been already verified for 32.3.1, and now is being moved to
v32 in the changelogs.
Running the test script provided by Andreas shows that there is no
difference on outputs from the archive version to the proposed version
(no regressions).
I am marking this verification-done for all r
Ok I'm having the very same problem now when upgrading from 22.04 to 24.04.
- The automatic size that the installer chose for my /boot partition is 704M
(no questions asked).
- When upgrading to 22.04 from 20.04 I had to manually remove old kernels. Just
any kernel update on Jammy nowadays makes
Given the wider range of problems represented in the bug, I have changed
the title/description to accomodate any subprocess returning non-utf8.
There is also a new fix plan. I will implement it and we will upload a
33.1 version to proposed fixing this.
** Description changed:
[ Impact ]
If
Updated the title to remove Mantic from the releases list - we are not
releasing there, because we aim for end of July as the date for v33 to
be out and Mantic should be EOL when it happens.
There is a Mantic release candidate in the staging PPA, but no upload to
mantic-proposed is expected.
** S
** Description changed:
+ [ Impact ]
+
+ If `apt` is masked by other helper tools, such as `nala`, as seen in the
+ original description, `apt list --installed` will return data in a
+ different format. This will cause the Pro Client to fail to parse the
+ data, and break.
+
+ The Pro Client sho
** Description changed:
+ [ Impact ]
+
+ If for any reason the user's system has any non-utf8 character as part
+ of the `apt list --installed` command, the Pro Client will fail to parse
+ the return output and break.
+
+ Independent of why this happens, the Pro Client should not be relying on
+
** Description changed:
[ Impact ]
This release brings both bug-fixes and new features for the Pro Client,
and we would like to make sure all of our supported customers have
access to these improvements on all releases.
The most important changes are:
-
+
+ - Some contracts now c
Public bug reported:
[ Impact ]
This release brings both bug-fixes and new features for the Pro Client,
and we would like to make sure all of our supported customers have
access to these improvements on all releases.
The most important changes are:
See the changelog entry below for a full list
Hello, Seth
We have implemented (a couple releases ago, sorry I forgot to update
this here) a better Unexpected APT Error message, which includes the
details returned by apt when the exception happens - so you immediately
see (before looking at logs) a pointer to what happened.
I am closing this
Nice! We have switched to python3-apt recently, and this will be not a
problem anymore in v33.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063032
Title:
Can't enable or disable livepatch.
To manage notific
Hi Marco, thanks for reporting this
The parsing of `apt list --installed` is failing - we are trying to
extract version information using the pattern, and it fails.
The root cause fix will be deployed next release. But to know what is
happening here, could you please append the output of `apt lis
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-advantage-tools (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Hello, Michael, thanks for reporting this bug.
The ubuntu-advantage.log contains tracebacks only related to livepatch,
and the Pro Client is behaving as expected as far as I can see.
I am including Livepatch people in this bug so they can weigh in on what
is happening. I will mark this incomplete
Hello, lokendar, thanks for reporting this bug.
I can see many timeouts in the logs. Those seem to be caused by
instability on our servers - we apologise. Now it should be back to
normal. Could you try enabling/disabling the services (like livepatch)
again?
Also, could you elaborate more on 'noti
Hello, jkwang28, thanks for reporting this bug.
Livepatch seems to be relying on the output of /etc/lsb-release to
verify compatibility on all operations (including disable/status/etc). I
would say editing /etc/lsb-release or /etc/os-release is not something
supported from the Pro side.
I see the
Hello, John, thanks for raising this issue.
I see the tracebacks in the logs are all related to timeouts and
disconnects. We apologise, our servers have been unstable for a while :/
Now everything should be normal again. Could you try to attach / run
status and see if the problem persists?
** In
Hello, Björn, thanks for reaching out and raising this bug.
I see you have tried to disable esm-apps, but during that operation, our
servers had an unexpected timeout :(
Now the service is up again - does this issue still persist? What
happens when you run
`sudo pro disable`
or
`sudo pro enabl
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066304
Title:
update-manager crashed
To manage notifications about
Hello, malperry73, thanks for reporting this bug.
I cannot reproduce it locally - I have no details from the logs on what
exactly did fail. Do you have steps to reproduce this behavior? Can you
see the same on different systems?
The only smell I see in the logs are errors and warnings for other
p
** Also affects: update-manager (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/2066304
Title:
update-manager crashed
To manage notifications abou
Hello, ubtb450, thanks for reporting this bug.
I am under the impression this is a duplicate of something already fixed on the
update-manager side.
I will add them to this bug, and mark incomplete for u-a-t until we get more
information.
** Information type changed from Private to Public
--
Y
** Information type changed from Private to Private Security
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066294
Title:
package ubuntu-
Hello, sahcadmin, thanks for reporting this bug.
It seems there is a problem in querying Livepatch status, so I'll be
tagging the Livepatch team to take a look.
On the Pro Client's side the behavior seems to be correct, but I'll keep
it as incomplete until we have more input.
** Information type
The verification for the main SRU bug
(https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2060732)
was done for 32.2 and no errors were encountered related to this bug.
No need to re-do all automation for 32.3, as explained
in:https://bugs.launchpad.net/ubuntu/+source/ubuntu-a
The verification for the main SRU bug
(https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2060732)
was done for 32.2 and no errors were encountered related to this bug.
No need to re-do all automation for 32.3, as explained
in:https://bugs.launchpad.net/ubuntu/+source/ubuntu-a
The verification for the main SRU bug
(https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2060732)
was done for 32.2 and no errors were encountered related to this bug.
No need to re-do all automation for 32.3, as explained
in:https://bugs.launchpad.net/ubuntu/+source/ubuntu-a
I'm re-marking this as verification-done for all releases, as it was verified
on 32.2 and the new 32.3 version does not affect this.
Further information in:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2067319/comments/1
** Tags removed: verification-needed verification-
I'm re-marking this as verification-done for all releases, as it was verified
on 32.2 and the new 32.3 version does not affect this.
Further information in:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2067319/comments/1
** Tags removed: verification-needed verification-
Context on the cloud-init failures:
Cloud-init's newer version changed the key used in cloud config for the
Pro client from ubuntu_advantage to ubuntu_pro. Because it is a
"breaking" change, this works fine on Focal and Jammy, where both keys
are accepted, but not on Noble.
On Noble, when you use
Updated the description, as Robie asked, with the problems that could occur.
Also outlined the tests to be executed to validate the fix for this bug.
** Description changed:
[ Impact ]
On ubuntu-advantage-tools v32.2, currently in -proposed, we are hitting
apparmor DENIED errors on the a
** Description changed:
[ Impact ]
On ubuntu-advantage-tools v32.2, currently in -proposed, we are hitting
apparmor DENIED errors on the apt update hook which executes esm-
cache.service.
This ONLY happens if the version with the apparmor profiles is installed
on a Focal system w
Public bug reported:
[ Impact ]
On ubuntu-advantage-tools v32.2, currently in -proposed, we are hitting
apparmor DENIED errors on the apt update hook which executes esm-
cache.service.
This ONLY happens if the version with the apparmor profiles is installed
on a Focal system which has been upgra
Hello Nathan, thanks for raising this issue.
tl;dr yes docs are wrong.
The thing it should express is that this endpoint raises no *specific*
exceptions, but at any time unexpected exceptions may happen and will be
raised as UbuntuProError instances.
There is ongoing work to update this on the d
1 - 100 of 180 matches
Mail list logo
