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 =>
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"
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"
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
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
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
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
*** 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.
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
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.
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`
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
** 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 ]
** 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
** 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
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
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
** 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
** 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
** 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.
** 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
+
** 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
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
** 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
** 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
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
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"
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
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
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
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,
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.
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
** 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
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
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
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
Thanks for the bug report! I think this is a good idea.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Confirmed
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Hi Daevid,
I'm sorry our package is causing this problem for you.
This appears to be a bug related to the python setup and dependencies on
the machine. Have you done any python development or pip installed
anything recently? If you have, the details might help us figure out
what happened here.
Hello Deysy,
Thank you for taking the time to submit a bug report!
This is appears to be a known bug in 27.2.2, and 27.4.2 should be
available in xenial-updates to fix it.
Please run:
sudo apt update
sudo apt install ubuntu-advantage-tools
If that still doesn't work, please let us know :)
--
Thank you Albourne for the additional information!
I was able to confirm this bug.
We are not specifying the full path to the `canonical-livepatch`
executable every time we call it, so if it is not in your PATH you will
get the error described here.
To reproduce the bug: `sudo env
I've verified that this bug is fixed in all releases by version 27.4.1
currently in -proposed.
I'm attaching the script I used (based on Renan's comment above) and the
output for each release.
** Attachment added: "1950813-ua27.4.1-verification.tar.xz"
I've tested that ubuntu-advantage-tools 27.4.1 from -proposed fixes this
bug on all releases.
I'm attaching the test script I used and the output for each release
here.
Tagging verification-done
** Attachment added: "1930121-ua27.4.1-verification.tar.xz"
Hello Bill Miller,
That's a good question that we probably should document better in our
manpage. I'll add this to the description of this bug as well.
First a clarification: If your machine is not "attached" to a Ubuntu
Advantage subscription, then the metering job does not do anything.
To
Hi freeflyer,
Thanks for taking the time to submit the bug!
Is the resourceToken you copied here exactly as it appears in the
machine-token.json file? I ask because it is surprising that "Token" and
"Type" are capitalized. I believe they should be all lower case like
"token" and "type". You may
Thank you for the additional information fagner128!
The error you posted here is actually slightly different in the details.
The python error is "ImportError: cannot import name 'Type'".
And it looks like you have a non standard python install in
/usr/local/bin/python3 that is taking precedence
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
This appears to be a duplicate of bug 1930121 and will be fixed in the
next release of ubuntu-advantage-tools 27.4, which should be released in
the next couple weeks.
This bug occurs when you have a
Attached are logs for all the manual tests for all series. All are
working as expected.
Marking verification done now.
** Attachment added: "manualtests27.3.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942929/+attachment/5536306/+files/manualtests27.3.tar.xz
We have run the full ubuntu-advantage-tools integration 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.
Next we will
Hello fagner128,
Before we debug farther I just want to make sure we have all the
details: Exactly what command is failing?
And for example, if "apt upgrade" is failing, does the following work?
env PYTHONPATH=/usr/lib/python3/dist-packages apt upgrade
If that doesn't work, please provide the
Sorry I missed this Steve. I've updated the script to enable proposed
instead of use the staging ppa.
** Description changed:
[Impact]
This bug impacts users on AWS or Azure, trying to enable FIPS/FIPS
updates on Focal images. Trying to install a non-cloud-optimized FIPS
kernel may
Steve and Chad: I just finished a manual test of:
1. Disabling ua-messaging.timer
2. In a chroot, upgrade ubuntu-advantage-tools
3. Check if ua-timer.timer was disabled
With the current upload this is unsuccessful, as Steve has predicted.
With our proposed change
Hi Steve,
> Ok, now I see - but that means deb-systemd-helper's auxiliary state will be
> permanently out of sync with the systemd state, I think?
We are purposefully manipulating d-s-h's state here, but it never
becomes out of sync with the systemd state.
> Also, this
> dh_systemd_enable
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
This appears to be a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in ubuntu-advantage-tools in a coming
release.
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
Thank you for the bug report!
This appears to be a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
Thank you for the bug report!
This appears to be a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
** This bug is no longer a duplicate of bug 1938290
package ubuntu-advantage-tools 27.2.2~16.04.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
**
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
This appears to be a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in ubuntu-advantage-tools in a coming
release.
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
** This bug has been marked a duplicate of bug 1930121
package ubuntu-advantage-tools 27.0.2~18.04.1 - ModuleNotFoundError: No
module named 'uaclient'
--
You received this bug notification because you
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
This appears to be a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in ubuntu-advantage-tools in a coming
release.
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
** This bug is no longer a duplicate of bug 1934077
package ubuntu-advantage-tools 27.1~16.04.1 - ModuleNotFoundError: No module
named 'uaclient' - maybe dup 1930121
** This bug has been marked a
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
I'm going to mark this a duplicate of bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in ubuntu-advantage-tools in a coming
*** This bug is a duplicate of bug 1930121 ***
https://bugs.launchpad.net/bugs/1930121
In the absence of more information I'm going to mark this a duplicate of
bug 1930121.
For now, the likely quick fix is to set
PYTHONPATH=/usr/lib/python3/dist-packages
We will release a proper fix in
Thank you Steve, you raise several good points.
1. The excessive nesting.
I agree that it is annoying to read several layers of nested ifs. As an
individual issue, we don't think this is a blocker; however if we decide to
rewrite this function for this SRU for the below reasons, we can use the
Thank you Steve for taking a look.
You are right on all counts.
It appears the code to pre-create log files is unnecessary. If you
consider this a blocker then we can remove it in this release. Otherwise
we will remove it in 27.4
We purposefully kept the purpose of the
** 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:
* more robust error handling when determining the cloud we're on LP: #1940131
Hello Joseph and Paride,
This looks like it might be a variation on bug 1930121
Do you have a non-standard python installation? (not installed via apt)
If so, then the quick fix is hopefully to just set
PYTHONPATH=/usr/lib/python3/dist-packages. To test, try running
I'm marking this invalid for the ubuntu-advantage-tools package since
this bug appears unrelated.
** 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 to Ubuntu.
** 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:
* more robust error handling when determining the cloud we're on LP: #1940131
** 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:
* more robust error handling when determining the cloud we're on LP: #1940131
** Description changed:
+ [Impact]
+
+ If cloud-id fails in a different way from what our postinst currently
+ checks for, then the postinst script will fail, breaking whatever apt
+ process was running.
+
+ We fixed this by changing the line that calls cloud-id to
+
+ cloud_id=$(cloud-id
** 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:
* more robust error handling when determining the cloud we're on LP: #1940131
** 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:
* more robust error handling when determining the cloud we're on LP: #1940131
** 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:
-*
+ * more robust error handling when determining the cloud we're on LP:
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:
*
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The
I have verified the version of ubuntu-advantage-tools in -proposed fixes
this bug. The logs of my tests are attached here.
** Attachment added: "distro-info-version-test.tar.xz"
Please note that this release also fixes #1932028 and #1930741 even
though they don't show up on the Pending SRU Page under Changelog Bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934902
In addition to the integration test logs. Here are manual test logs
verifying the correct versions of distro-info are installed on xenial
and bionic, as described in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
tools/+bug/1932028
** Attachment added:
Thanks for the bug report!
ubuntu-advantage-tools tries to run `cloud-id` if the command is present
during postinst to find a certain edge case and notify the user.
It looks like cloud-id was available, but instance-data.json was
missing, so cloud-id failed. I believe this would occur if
** Description changed:
+ [Impact]
+
+ This bug caused aptdaemon to miss two configuration options that ubuntu-
+ advantage-tools relies on for updating its messaging based on apt state.
+ Apt itself parsed the options despite the syntax mistake, which led to a
+ difference in understanding
1 - 100 of 132 matches
Mail list logo
