As noted above, we're tracking the fix to hide unnecessary warnings in
ubuntu-advantage-tools over in bug 2074211 and updating this bug along
the way for visibility. I have finished verification and posted logs in
a comment on bug 2074211. Marking verification done for both now.
** Tags removed: v
I've run the test plan for all releases and the fix works as expected.
Logs attached. Marking verification done.
On noble I reproduced by force installing the old version of systemd
affected by bug 2055239. On all other releases, I caused a similar
warning message in a more contrived way by direct
I've run the test plan for each ubuntu release verifying that the bug
occurs on the previous version of pro-client and is fixed on the version
in -proposed. Logs attached. Marking verification done.
** Description changed:
[ Impact ]
If the jobs-status.json file somehow got corrupted on a
We have run the full ubuntu-advantage-tools integration test suite
against the version in -proposed. The results are attached. All expected
tests passed.
Some individual tests required a re-run for various reasons, some due to
temporary backend outages, and some due to small issues in the tests
th
** Description changed:
- [ Impact ]
+ [ Impact ]
When bugs unrelated to ubuntu-pro-client affect the apt-hooks in such a way
that they print warning or error messages, ubuntu-pro-client is percieved to be
at fault. Usually these warnings and errors cannot be fixed by
ubuntu-pro-client and a
Thanks ahasenack!
> the apt-news hook does not log to "apt-news.service.txt"
You are correct, but `pro collect-logs` does collect the status of apt-
news.service and puts it in a file called "apt-news.service.txt". That
is what the test is testing.
> include in the test plan a logrotation scenar
** Description changed:
+ [ Impact ]
+
+ If the jobs-status.json file somehow got corrupted on a pro attached
+ machine, the ua-timer.service would crash when trying to read it. This
+ is not a critical state file, so the fix is to catch the error and
+ delete the file if it is corrupted.
+
+ [
** Information type changed from Private 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/2078614
Title:
pro refresh Failed running command '/snap/bin/canonical-livepatch
config' [exit(1)]
dvantage-tools (Ubuntu Noble)
Status: Invalid => In Progress
** Changed in: ubuntu-advantage-tools (Ubuntu)
Assignee: (unassigned) => Grant Orndorff (orndorffgrant)
** Changed in: ubuntu-advantage-tools (Ubuntu Noble)
Assignee: (unassigned) => Grant Orndorff (orndor
Thanks @enr0n. We had already created a separate bug (bug 2074211) to
represent the case that you describe, so I'll mark this one back to
"Invalid" for ubuntu-advantage-tools.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Invalid
** Changed in: ubuntu-advantage-tools (Ubunt
It sounds like the airgapped config was not yet set up when this test
occurred.
This bug is still valid for lack of network access in general, though.
These commands shouldn't totally fail if they can't reach the network.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Incomplete =
The expected result after a `pro detach` is two things:
1. The machine stops being counted as an active machine according to the Pro
backend (and reflected on the Pro dashboard for users)
2. The machine stops receiving Pro services
If `pro` fails to do either of these things, then we can't really
** Description changed:
+ [ Impact ]
+ When bugs unrelated to ubuntu-pro-client affect the apt-hooks in such a way
that they print warning or error messages, ubuntu-pro-client is percieved to be
at fault. Usually these warnings and errors cannot be fixed by
ubuntu-pro-client and are indicative
** 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:
-
+ - updated help output
+ -
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
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
Some additional context:
A token may have entitlements coming from multiple sources (e.g., shop
subscriptions and trials, direct sales, etc).
If there are multiple sources for a token, we cannot pinpoint exactly if
a single machines would be impacted by not renewing a portion of the
entitlement s
Thanks! I'll forward these suggestions to the team that handles the
backend and notification emails as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073921
Title:
Ubuntu pro should not warn t
That is a great idea hvbakel! Thank you for suggesting it.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs
Hi Nathan, per comment #9
(https://bugs.launchpad.net/ubuntu/+source/update-
manager/+bug/2058133/comments/9) we decided on "invalid" for ubuntu-
advantage-tools for this particular bug.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Invalid
--
You received this bug notific
That systemd issue does appear to be the root cause
** Also affects: systemd (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/2055239
Title:
Warnin
Thank you for confirming!
This is an ongoing issue with the back-end API and is being tracked here
https://github.com/canonical/ubuntu-com-security-api/issues/165
Since there isn't much the `pro` command can do without a functioning
back-end API for the security data, I'll mark this bug as Invali
Marking this as public since there are no private details in the logs.
** Information type changed from Private 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/2073264
Title:
package ubuntu
Hello Gustavo and thanks for submitting this report! Glad to hear you're
trying Ubuntu for your project.
The warnings you've seen:
Warning: The unit file, source configuration file or drop-ins of
apt-news.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: The unit f
Is there an estimate of when the fixed version of fail2ban might land in
nobel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2ban is broken in 24.04 Noble
To manage notification
Thanks for reporting this Novexx!
Unfortunately I can't find anything in the logs.
Does the error look something like this?
Error connecting to notices.json: 503
503 Service Temporarily Unavailable
503 Service Temporarily Unavailable
nginx
The security API that the `pro fix` command relies
Thanks for reporting this Johan!
From looking at the logs, it appears this may have been due to a
temporary outage of Canonical servers.
Can you try again and report back here if it works now?
** Information type changed from Private to Public
** Changed in: ubuntu-advantage-tools (Ubuntu)
Thanks for reporting this Shubham!
From the logs, it looks like the error is coming from canonical-
livepatch. Pasting the formatted stacktrace here:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uaclient/livepatch.py", line 130, in
status
out, _ = system.subp(
** 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
*** This bug is a duplicate of bug 2060769 ***
https://bugs.launchpad.net/bugs/2060769
Thank you for reporting this jibel!
I've reproduced this issue on a lxd-container and the root cause seems
to be bug 2060769 so I'm marking this as a duplicate.
This is fixed upstream and will be released
** Package changed: chromium-browser (Ubuntu) => null-and-void
** Information type changed from Public to Private
** Changed in: null-and-void
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Hi I'm coming back to this again. I hadn't acted before because I didn't
hear any information about my question above.
Is this still important? Should pro-client implement a prompt like that
described in previous comment?
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Triaged => In
I've verified that this error no longer occurs during `ubuntu-bug
ubuntu-advantage-tools` with version 32.2 in -proposed for all Ubuntu
releases. Logs attached. Marking verification done.
** Attachment added: "verify-2065616.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-to
Thanks Allison!
For the rest of the SRU verification: I've performed the test steps
against 32.2 currently in -proposed, for all Ubuntu releases. The test
passed in all cases. Logs attached. Marking verification done.
** Attachment added: "verify-2065573.tar.gz"
https://bugs.launchpad.net/ubu
Hello Davide,
It is currently in -proposed, and scheduled to be released to -updates
early next week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064624
Title:
Warning: W:Unable to read /var/lib
Great! I'm glad the workaround works for you.
In order to try to reproduce and debug the original problem, It may help
to provide a bit more information on the azure instance. Could you share
the "Security type", "Size", and "Source image details" values for this
problematic instance as seen in th
Hello Abdul,
Thank you for taking the time to submit a bug report!
That message means that `cloud-init` was unable to detect what cloud you
are on (more specifically, the `cloud-id` command didn't return a cloud
name).
Can you provide what instance type and image you are using on Azure?
As a w
Public bug reported:
[ Impact ]
The new apparmor profile for esm-cache.service has sub profiles for
subprocesses and some of them were incomplete, resulting in the
following apparmor DENIED messages in the following situations:
On xenial, after a `pro attach`:
2024-05-21 15:22:29,438:WARN
*** This bug is a duplicate of bug 2065192 ***
https://bugs.launchpad.net/bugs/2065192
** This bug has been marked a duplicate of bug 2065192
(ubuntu) pro attach doesn't work !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Wonderful! I'm glad it is working now.
For context: We already have a separate bug for changing pro's reliance
on the `apt list --installed` command: #2060769
Because we have that bug to represent that work, and your problem has
been resolved, I'm going to close this bug.
Thank you!
** Changed
We have also experienced the same issue as reported here:
https://bugs.launchpad.net/maas/+bug/2065820
Would like to see MAAS updated to support this. Our code fix over in the
other ticket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Hello!
Yes it seems your system has https://pypi.org/project/apt-wrapper/
installed which is masking the true "apt".
Renaming /usr/local/bin/apt to something else or otherwise uninstalling
it somehow should allow the real apt commands to work.
Please try this and then try to `pro attach` again.
Do we have to subscribe to Ubuntu Pro to get an update of this package?
But seriously, what will it take to get this package fixed in Ubuntu?
How can we take Ubuntu seriously on the server is such a fundamental
package remains critically broken?
--
You received this bug notification because you
Hello pici-1251,
Thank you for the reply!
Do not uninstall dpkg - it is a critical utility in Ubuntu.
The kernel version should not be a problem.
The problem seems to be that `dpkg-query --listfiles` is running instead
of `apt list --installed`.
The expected output of `apt list --installed` is
Hello pici-1251,
I'm now wondering if we aren't properly receiving your messages. All we
got from your last comment was what looks like a email signature image
but no actual message. Have you been responding to these comments via
email? That usually works but I wonder if something isn't parsing yo
Hi pici-1251,
From your screenshot, it appears that `apt list --installed` is somehow
being redirected to `dpkg-query --listfiles`.
Do you have some alias or alternative `apt` command installed on your
system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks Nobuto!
First reported here: https://github.com/canonical/ubuntu-pro-
client/issues/3060
Fixed upstream and to be released in v32 of ubuntu-pro-client in mid May
(See LP: 2060732 for overall SRU bug)
** Bug watch added: github.com/canonical/ubuntu-pro-client/issues #3060
https://github
It looks like the global need-reload state that Christian investigated
that is being set by a snapd operation was added recently in systemd.
https://github.com/systemd/systemd/commit/a82b8b3dc80619c3275ad8180069289b411206d0
That is likely why we're only seeing this issue in noble.
From reading t
Hello theroblp!
Thank you for the bug report! I'm assigning this bug to the livepatch
snap as this seems to be a bug in the snap package.
It looks like even `snap install canonical-livepatch` is failing.
I'll leave it as "incomplete" for the ubuntu-pro-client (ubuntu-
advantage-tools) for now in
Hello pici-1251!
Thank you for the bug report and sorry for the delay in responding.
Please do not post your Ubuntu Pro token here as I will set this bug to
public for the benefit of others.
It looks like `apt list --installed` is returning an error.
What happens if you run `apt list --installe
Hi Adam!
What version of update-manager do you have? I believe this was fixed in
1:22.04.20 which was SRU'd recently.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Hi sistemascps!
Thank you for the bug report and sorry for the delay in responding. It
looks like a non-UTF-8 character is present in the output of `apt list
--installed`.
The fix will be to replace the usage of `apt list --installed` with
using the python3-apt library to get the list of installe
Upstream have release a new version which fixes Python 3.12+
compatibility. https://github.com/fail2ban/fail2ban/releases/tag/1.1.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055114
Title:
fail2
Duplicate of:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114
** Changed in: fail2ban (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/2063213
Titl
Public bug reported:
fail2ban systemd service fails to start on Ubuntu 24.04 because python
3.12 no longer comes with bundled version of pyasynchat.
```
PYTHONNOUSERSITE=1 /usr/bin/fail2ban-server -xf start
2024-04-23 13:28:10,715 fail2ban.configreader [3819]: WARNING 'allowipv6' not
defined i
Could someone please advise how these issues can float a little higher
before kernel freeze things happen? I tried to get this on the books
quite early by doing a Ubuntu Root on ZFS setup and giving it a test. I
know it's not directly related to the issue, but I tried to raise
awareness of this qui
Also of note, ZFS 2.2.2 is not explicitly compatible with Linux 6.8. ZFS
2.2.3 is explicitly compatible with kernel 6.7, and preliminary support
for 6.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2
The fix is to install the firmware-ast package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751613
Title:
W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module
ast
To manage n
** Bug watch added: github.com/openzfs/zfs/issues #15930
https://github.com/openzfs/zfs/issues/15930
** Also affects: zfs via
https://github.com/openzfs/zfs/issues/15930
Importance: Unknown
Status: Unknown
** Summary changed:
- copy_file_range Operation Not Supported
+ Kernel 6.8
Public bug reported:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling copy_file_range,
breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running R
Thanks for all the investigation and discussion!
Just to close out the ubuntu-pro-client related questions:
ubuntu-pro-client does run daemon-reload in postinst.
and here is a reproducer that doesn't involve ubuntu-pro-client services
```
lxc launch ubuntu-daily:noble test
lxc shell test
# now in
Thank you renanrodrigo!
Marking verification done.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-jammy verification-needed-mantic
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-do
As noted in the Test Plan, an automated test was added to the ubuntu-
advantage-tools package to cover this bug. We ran the full automated
test suite for the SRU of 31.2, including this one, and they all passed.
Logs are attached in LP: #2048921. So I'm marking verification done for
this bug.
The
For the SRU
As noted in the Test Plan, an automated test was added to the ubuntu-
advantage-tools package to cover this bug. We ran the full automated
test suite for the SRU of 31.2, including this one, and they all passed.
Logs are attached in LP: #2048921. So I'm marking verification done for
th
Hello Owen,
Sorry for the delay. The 24.04 repositories are in the middle of a large
transition related to time_t64 and many packages/updates, including this
one, are blocked on other builds because of that. I hope the backlog
will be worked through soon, and I will try to get this update publishe
We have run the full ubuntu-advantage-tools integration (behave) test
suite against the version in -proposed. The results are attached. All
tests passed. You can verify the correct version was used by checking
the output of the first test in each file, which prints the version
number.
I also ran a
I followed the test plan and demonstrated the bug before an upgrade,
then demonstrated that the bug no longer occurs after upgrading to the
version of ubuntu-advantage-tools in -proposed. I'm attaching logs for
all releases and marking verification done.
The autopkgtest failure on mantic ppc64el w
I've tested the fixed version of ubuntu-advantage-tools in -proposed
using the test plan described. I show the bug before the upgrade and
show that it doesn't occur after the upgrade in the logs attached.
The autopkgtest failure on mantic ppc64el looks like a flaky
infrastructure problem and shoul
I've run the test plan for the ubuntu-advantage-tools fix to this bug on
xenial, bionic, focal and jammy. livepatch is not supported on mantic,
so this bug doesn't actually affect mantic. The tests passed and logs
are attached.
The autopkgtest failure on mantic ppc64el looks like a flaky
infrastru
** Description changed:
[ Impact ]
pro status shows livepatch as "disabled" when "canonical-livepatch"
returns an error. This can be misleading. It would be more helpful to
propagate the error message up to the user through pro status; that is
what the fix does.
[ Test Plan ]
Public bug reported:
A regular noble full-upgrade transitioned my laptop to the thunderbird
snap this morning, and I ended up with no profile due to an EPERM
reading ~/.thunderbird during the migration. thunderbird.launcher says
it needs personal-files, but the thunderbird snap doesn't seem to hav
** Description changed:
[ Impact ]
After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1,
an old logrotate conffile named ubuntu-advantage-tools is left behind. The old
file configures the same files as the new conffile: ubuntu-pro-client.
The result is that when logr
** 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:
- rename ubuntu-advantage-t
Hello xypron
Did you upgrade ubuntu-advantage-tools as well? That should remove the
file - if it does not please let us know.
Any system not on -devel will either never have ubuntu-advantage-tools
or it will be required to upgrade to 31.2 of ubuntu-advantage-tools at
the same time as installing u
Thank you nobuto! With that I was able to reproduce the issue.
lxc launch ubuntu-daily:noble test
lxc exec test -- apt update # this one works as expected
lxc exec test -- snap install snapd
lxc exec test -- apt update # this one has the warnings in the bug report
assigning this bug to snapd
** 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:
- rename ubuntu-advantage-t
** Description changed:
+
+ [ Impact ]
+ After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1,
an old logrotate conffile named ubuntu-advantage-tools is left behind. The old
file configures the same files as the new conffile: ubuntu-pro-client.
+ The result is that when
** Changed in: ubuntu-advantage-tools (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/1880546
Title:
80-esm requires lsb_release bu
** Changed in: ubuntu-advantage-tools (Ubuntu)
Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707290
Title:
Removing pack
** Description changed:
+ [Impact]
+
+ This was intended behavior, but is considered unintuitive and
+ undesirable in some situations.
+
+ The issue affects users who want an apt proxy only for ua-related
+ packages, who may find the `apt_http(s)_proxy` variables and expect them
+ to do that. Th
** Description changed:
+ [Impact]
+
+ This bug causes users to see an inaccurate message saying that a reboot
+ is required when that is not true. It doesn't affect the operation of
+ FIPS mode, but it is confusing.
+
+ The bug occurs because of a case we have in our postinst which checks
+ for
** Description changed:
+ [Impact]
+ This bug causes enabling services during a `ua fix` operation to fail.
+ That means that any user that is attached to a UA contract, but needs a
particular service to fix a USN or CVE could run into this bug if they try to
use `ua fix` to fix that USN/CVE.
** Description changed:
[Impact]
This release sports both bug-fixes and new features and we would like to make
sure all of our supported customers have access to these improvements. The
notable ones are:
* A daemon that only runs on GCP
* Currently it ends early based on a defau
Public bug reported:
[Impact]
This release sports both bug-fixes and new features and we would like to make
sure all of our supported customers have access to these improvements. The
notable ones are:
* A daemon that only runs on GCP
* Currently it ends early based on a default config set
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Triaged => 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/1964134
Title:
[FFe] ubuntu-advantage-tools 27.7
To manage notifi
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Fix Committed => 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/1956764
Title:
Proxy should be set up only for ua-related rep
Hi odoncaoa,
Thanks for taking the time to report this bug and make Ubuntu better!
Before discussing the snap related issues you've brought here I want to
clarify my understanding: Are you experiencing any problems related to
the ubuntu-advantage-tools package (which provides the `ua` command lin
It doesn't look like this bug was captured by the normal automation for
the impish SRU of ubuntu-advantage-tools 27.8, but I have performed the
verification and the fix works as expected. Please see the attached log.
** Attachment added: "impish-verification-1968067.txt"
https://bugs.launchpad
We have run the full ubuntu-advantage-tools integration test suite for
jammy against the version in -proposed. The results are attached. All
tests passed.
You can verify the correct version was used by checking the output of
the first test in each file, which prints the version number.
I am marki
I have tested the package in -proposed using the steps in the
description. I first verified the bug occurred on jammy with the current
package and that it no longer occurred after upgrading to the package in
-proposed. Please see the attached log.
Marking verification-done-jammy
** Attachment add
** Project changed: launchpad => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969294
Title:
Ubuntu 22.04 gdm3 freezes with Nvidia GPU
To manage notifications about this bug go to:
https://
Public bug reported:
See this error
https://errors.ubuntu.com/problem/864d1a4d38167a7b009ce993125030b58eb012d5
When upgrading from focal -> impish or from impish -> jammy, a KeyError
will occur in the upgrade_lts_contract.py script from ubuntu-advantage-
tools. This happens because that script ha
Per discussion in chat: The image did not have the ubuntu-advantage-pro
package installed, which is what runs `ua auto-attach` on boot.
Installing that package from ppa:ua-client/stable should resolve this
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thank you Lukasz! Yes, we understand this timing is unideal. We'll try
to avoid such a late release in the future. We will certainly land this
before Beta freeze.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Attaching the jammy integration test results for ua 27.7.
** Attachment added: "ua-27.7-jammy-test-results.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1964134/+attachment/5567175/+files/ua-27.7-jammy-test-results.tar.gz
--
You received this bug notification
Public bug reported:
ubuntu-advantage-tools 27.7 includes several features and bug fixes to
support customer requests and make the `ua` tool more usable. The most
notable features are:
* --format=json for attach,detach,enable,disable
* --attach-config option when attaching for users to pass
** Description changed:
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
- * --format=json for attach,detach,enable,disable
- * --attach-config option w
Public bug reported:
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
* --format=json for attach,detach,enable,disable
* --attach-config option when attaching for
Hello Walter Hachmann, thank you for taking the time to file a bug!
debconf can wait forever if it is expecting some sort of input but not
getting any. That may be what is happening here. A common scenario that
can trigger this is if the config file /etc/ubuntu-
advantage/uaclient.conf is edited a
Hello Gene Sun, thank you for taking the time to file a bug!
The livepatch service is installed as a snap when you run `ua enable
livepatch`. It looks like the `snap` command is failing because the
snapd.socket isn't available.
Can you verify that the snap service is working or not by running a s
1 - 100 of 6691 matches
Mail list logo
