We have run all of the tests specified in the test plan. The result are
attached here
** Attachment added: "test-results-32.3.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2067319/+attachment/5783774/+files/test-results-32.3.tar.xz
** Tags removed:
We have marked the apparmor issue as verification-done:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2067319
Due to that, we are also marking this one as verification-done too
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal
We have run the full ubuntu-advantage-tools integration (behave) test
suite against the version in -proposed. The results are attached.
Some tests are failing, but this is expected:
* Upgrade from Bionic to Focal: Apparmor related issues that will be fixed on
32.3
* cloud-init related tests 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:
- - d/apparmor:introduce new
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"
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060566
Title:
Add
Even though the verification is already done, we intend to only release
this package on April 30
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060566
Title:
Add esm-infra-legacy support for Trusty
I have performed the verification for this proposed changed.
Attached to this comment, are the test results we have obtained when running a
custom script that:
1) Launches a trusty lxd container
2) Install the proposed version of the Pro client
3) Checks that esm-infra-legacy appears on ua
** Description changed:
+ [Impact]
+
+ When users create an airgapped environement, they may create APT mirrors
+ for the ESM services that share a common base URL. For example, in this
+ bug here, the user was mirroring their services one:
+
+
** Description changed:
+ [ Impact ]
+
+ Since we want users to relate to the Pro name when using the client,
+ renaming the collect_logs output from ua_logs to pro_logs is a step on
+ that direction.
+
+ [ Test Plan ]
+
+ This is already covered by the integration tests tied to the next Pro
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:
- d/apparmor:introduce new
** Description changed:
[Impact]
As Trusty is reaching EOL of ESM support, we are now creating a new service
called esm-infra-legacy to extend ESM support for more time.
- Users who are entitled to that service, will need to run both of these
- commands to enable the service in their
** Also affects: ubuntu-advantage-tools (Ubuntu Trusty)
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/2060566
Title:
Add esm-infra-legacy support for
** Description changed:
- As Trusty is reaching EOL of ESM support, we are now creating a new
- service called esm-infra-legacy to extend that support for more time
+ [Impact]
+ As Trusty is reaching EOL of ESM support, we are now creating a new service
called esm-infra-legacy to extend ESM
Public bug reported:
As Trusty is reaching EOL of ESM support, we are now creating a new
service called esm-infra-legacy to extend that support for more time
** Affects: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
** 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
** 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
Public bug reported:
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 instance
Hi Brandon Castillo,
I think that is a good idea and I agree that we can make this error
message better.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We no longer ship the 99-esm file, so we shouldn't be affected by this issue
anymore.
Additionally, I have double checked the new update-motd scripts we deliver and
I can confirm they will not break the system if the user just removes the
packages, since we have a check that prevent invalid
Hi dabbsa, thanks for reporting this.
I could not reproduce this error by running either attach or enable directly.
Just to confirm something, if the error still persist in the machine, can you
please send
us the output of running apt-get update on the system ?
** Changed in:
Hi Filipi,
Can ypu please send us the output of running the command:
$ sudo ua collect-logs
This will generate a a tar file named: ua_logs.tar.gz
With the logs there, we can better understand what happened during the
failure you mentioned
** Changed in: ubuntu-advantage-tools (Ubuntu)
Hi Daevid,
Looking at the dpkg logs, it seems that we are trying to import the yaml
module from an incorrect path:
File "/usr/lib/python3/dist-packages/uaclient/config.py", line 11, in
import yaml
File "/root/.local/lib/python2.7/site-packages/yaml/__init__.py", line 2, in
from error
Hi Eric,
No, the problem here is that the FIPS message you are seeing:
Reboot to FIPS kernel required
Is not being properly removed by our tool. We will fix this in a subsequent
release of UA.
Not that this doesn't cause the lsb_release issue you mentioned at all.
Additionally, the lsb_release
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.
I am marking the
Hi cs-huit, thanks for reporting this issue.
Looking at the logs this seems like a real bug on UA regarding the ua fix
command.
I will make a PR that address this issue.
However, on the meantime, if you want to keep those packages, please
run:
$ ua enable esm-infra
And then run:
$ ua fix
** Description changed:
+ [Impact]
+ When users are upgrading their machines, we run the upgrade_lts_contract
script to ensure that the services that were unable will keep being enable in
the new ubuntu release the users are upgraded too.
+
+ Currently, if the user upgrades directly from Focal
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:
* add support for realtime kernel service on Jammy as a beta service
* update code to use
We have a PR up fixing this issue:
https://github.com/canonical/ubuntu-advantage-client/pull/2028
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968067
Title:
upgrade_lts_contract.py exception on
We have performed the test for release 27.7 using the package that is
proposed
** Attachment added: "ua-test-results-27.7.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1964028/+attachment/5573894/+files/ua-test-results-27.7.tar.xz
** Tags removed:
Just approved the PR robert-ancell
Also, I understand the need to use status.json directly. In the future
we can better discuss on how we can extend `ua status --format json` to
the Desktop needs to simplify that process.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Currently, it seems that software-properties is incorrectly assuming
that both ESM and Livepatch services can be enabled in a Jammy machine.
Those services are not yet available in Jammy and we are attaching an
image showing that the Desktop message is that we had an error
Hi arnoldthebat,
Just to double check, were you attached to an UA subscription before performing
apt upgrade ?
Also, does the problem persist if you run:
apt-get install ubuntu-advantage-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi Gene Sun,
This is a really odd issue and I have never experienced it before. I think the
best path forward is to contact the snapd team and ask for help there, as this
could be a bug on the package:
https://bugs.launchpad.net/ubuntu/+source/snapd
Since this is issue is snapd related, I am
Hello Gene Sun,
It seems there is something wrong if your snapd service.
What is the output of running:
$ systemctl status snapd
And if the service is not running, can you run:
$ systemctl start snapd.service
And double check if snap services is now running as expected ?
--
You received
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960712
Title:
package ubuntu-advantage-tools 27.6~20.04.1 failed to
Hi sahbi, when looking at the DpkgTerminalLog, I found that entry when
the error happened on ubuntu-advantage-tools:
/usr/bin/python3: Permission denied
Was there are any recent modifications on your python environment ?
Our postinst script do need to run python code, so if we cannot run the
We have performed the test using version 27.6 found in the proposed
pocket.
** Attachment added: "sru-release-27.6.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1958556/+attachment/5559186/+files/sru-release-27.6.tar.xz
** Tags removed: verification-needed
Hi Robie,
I think you spotted a gap in our solution, we should be redacting older
logs in the postinst function before we make then world readable. We
should not rely on the logrotate functionality for this. I will remove
that commit from the release and update it accordingly.
--
You received
** Description changed:
[Impact]
The main focus of this release is to allow focal cloud users to enable FIPS
services on their machines. Furthermore, we are also performing some small
fixes in the code:
* Fixing how apt and motd messages are updated after some ua operations
* Disable
Public bug reported:
[Impact]
The main focus of this release is to allow focal cloud users to enable FIPS
services on their machines. Furthermore, we are also performing some small
fixes in the code:
* Fixing how apt and motd messages are updated after some ua operations
* Disable the license
Here is the results of our tests for this issue on release 27.4.2
Note that this issue should only affect LTS releases, which can be verified on
the hirsute and impish tests.
we have also appended the test script we have used to generate those
results
** Attachment added:
Hi phuctruonghoang,
Can you better describe what was the issue that happened with ubuntu-
advantage-tools ?
Also, can you please run:
ua collect-logs
And attach the results here, so after you describe the issue we can
better investigate it.
** Changed in: ubuntu-advantage-tools (Ubuntu)
** 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.
https://bugs.launchpad.net/bugs/1950576
Title:
UA cli / Exception on launch
To manage notifications about
Awesome :)
I will close this bug then, but if anything else comes up, please let us know
** 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.
** Summary changed:
- traceback from postinst on upgrade
+ ubuntu-advantage-tools (27.4.1 -> 27.4.2) Xenial, Bionic, Focal, Hirsute,
Impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951705
** Description changed:
+ [Original bug description]
I noticed this on an upgrade in focal:
Setting up ubuntu-advantage-tools (27.4.1~20.04.1) ...
Installing new version of config file /etc/ubuntu-advantage/uaclient.conf ...
Traceback (most recent call last):
- File "", line 10, in
Hi Albourne, can please run:
ua collect-logs
And append the result here so we can better investigate this issue
** 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
Hi Steve and Oli, we have landed the fix on main we will soon release it.
Thanks for reporting this issue and providing the additional context for it
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are
Hi c-kras, we have invalidated that token for you. You can now go to:
https://ubuntu.com/advantage
And get a new token for you.
Also, please verify if you have other machines using the old token as
well, just so you can update them to the new one
--
You received this bug notification because
Hi Steve, I am also trying to reproduce this issue but so far I am
unable to reproduce it using a clean lxd focal VM with ubuntu-advantage-
tools version 27.3 installed by default. I tried running upgrade with a
machine attached and unattached but still no failure prompts were
generated.
Was
Hi Norbert,
This happens because ubuntu-advantage-tools is a package dependency of
the ubuntu-minimal metapackage. Although it is possible to change that
from a Depends to a Recommends, we will need to have a broader
discussion about it.
I suggest sending the request into this mailing list to
Adding all of the tests results for this SRU
** Attachment added: "sru-verification-27.4.1.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1949634/+attachment/5541258/+files/sru-verification-27.4.1.tar.xz
** Tags removed: verification-needed
Hi c-kras, to invalidate the token please:
1. Run ua detach on the machine
2. Inform us that the machine is detached
Once that is done, we will invalidate the token for you and we will let
you know when a new token will be available for you.
Now, regarding the error you posted, can you confirm
Sorry c-kras, you have accidentally leaked your resource token in this thread.
You will need to invalidate your current token and generate a new one.
Let me know if you need any help with that.
And about the issue, can you send the full error that you see when you
run ua enable
--
You received
Hi freeeflyer,
Can you take a look into /var/lib/ubuntu-advantage/private/machine-
token.json and confirm if there any resourceTokens entry there without a
"type" key ?
One easy way to read that file is by installing the jq package.
You can run the following command:
cat
** 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/1947506
Title:
failed to call "sudo ua attach 'key'" with
Awesome, so let's recreate that machine-id now:
1. Delete the /etc/machine-id file
2. Run systemd-machine-id-setup
Hopefully this will create a machine-id without any special characters on it.
If that is true, you can just attach again and enable esm-infra
--
You received this bug
Fair enough, my mistake. I was running this directly on the interpreter.
But let me try something here, can you run this command without errors:
ua detach
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yeah, that's a really odd problem. I tried using the same machine-id you
provided on a Xenial container but was unable to reproduce any of the
problems here. The enable operation was successful even using the
machine-id with a newline character.
Can you run the following python script and append
Hi Htbaa,
This is weird because I think this type of special character should not be
allowed on the machine-id.
Also, it seems that you are already attached to an UA subscription. To attach
we also use the machine-id so it is weird that attach worked and enable does
not.
Can you attach
Hi guiverc, can you please also append the /var/log/cloud-init.log file
to this bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950230
Title:
cloud-init crashed with NameError in
Hi Htbaa, I think that's exactly the problem we are facing.
Just to be clear, can you confirm if the id in /etc/machine-id is the
one reported in this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
This releases will turn on the metering job by default. The metering job will
report which services are being used to the contract server every 4 hours.
Since we already have the timer mechanism in place, we believe the substantial
risk for this release is
Public bug reported:
[Impact]
This releases will turn on the metering job by default. The metering job will
report which services are being used to the contract server every 4 hours.
Since we already have the timer mechanism in place, we believe the substantial
risk for this release is that
Hello murthagh,
Did you a custom python version installed in your system ? If yes, I
think you can run the upgrade command again specifying the right python
path like this:
env PYTHONPATH=/usr/lib/python3/dist-packages apt upgrade
If that doesn't work, please provide the output of the following
Hello wsbrito1975,
Did you a custom python version installed in your system ? If yes, I
think you can run the upgrade command again specifying the right python
path like this:
env PYTHONPATH=/usr/lib/python3/dist-packages apt upgrade
If that doesn't work, please provide the output of the
Yes, we should raise a more informative exception here for sure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949524
Title:
ua attach and ua status on linux Mint result in tracebacks
To manage
Hi mxmotao, looking at the dpkg log it seems that you are using a custom
cloud-id command, since the path for it is /usr/local/bin/cloud-id while
the cloud-init version is expected to be on /usr/bin/cloud-id
Is that true ? If yes, can you give us more context on what it is doing
?
** Changed in:
Azure bug verified with the following script:
---
import logging
import os
from pycloudlib.azure.cloud import Azure
api = Azure(
tag="test-azure",
client_id=os.getenv("UACLIENT_BEHAVE_AZ_CLIENT_ID"),
AWS Bug verified with the following script:
---
import logging
import os
from pycloudlib.ec2.cloud import EC2
api = EC2(
tag="test-ec2",
access_key_id=os.getenv("UACLIENT_BEHAVE_AWS_ACCESS_KEY_ID"),
Bug verified with the following script:
---
import logging
import os
from pycloudlib.ec2.cloud import EC2
api = EC2(
tag="test-ec2",
access_key_id=os.getenv("UACLIENT_BEHAVE_AWS_ACCESS_KEY_ID"),
Test output:
--- Creating base instance
Distributor ID: Ubuntu
PS: this bug does not affect hirsute and impish because those series are
not entitled to FIPS services.
This can be further verified in the test results
** Attachment added: "1944676-test-results.tar.xz"
Bug verified with the following script:
--
series=$1
name=test-$series
multipass launch --name $name $series
multipass exec $name -- ua version
multipass exec $name -- cloud-init status --wait
multipass exec $name -- sudo ua attach
** Attachment added: "1938207-test-results-extra.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1938207/+attachment/5536058/+files/1938207-test-results-extra.tar.xz
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal
Impish and hirsute tests performed with the following script:
series=$1
name=test-$series
multipass launch --name $name $series
multipass exec $name -- ua version
multipass exec $name -- cloud-init status --wait
multipass exec $name -- sudo /bin/sh -c "printf
** Attachment added: "1938207-test-results.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1938207/+attachment/5536055/+files/1938207-test-results.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have modified the test script to install the package in proposed:
--
import pycloudlib
import os
lxd = pycloudlib.LXDVirtualMachine("vm")
name = 'pycloudlib-vm'
release = "hirsute"
pub_key_path = "lxd-pubkey"
priv_key_path =
Adding test results
** Attachment added: "1940131-test-results.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1940131/+attachment/5536054/+files/1940131-test-results.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bug verified with the following script:
--
series=$1
name=test-$series
UA_TOKEN=
lxc launch ubuntu-daily:$series $name
lxc exec $name -- ua version
lxc exec $name -- cloud-init status --wait
lxc exec $name -- mv /usr/bin/cloud-id /usr/bin/cloud-id.old
I have run all of the manual tests with the proposed package and they
are all working as expected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942929
Title:
[SRU] ubuntu-advantage-tools (27.2.2
Hi Florian, thanks for reporting this bug. This is probably happening
because the machine has the cloud-init package installed but it was not
fully run on the machine (which is not a problem per se).
We have addressed this on our next release of ubuntu-advantage-tools
that should be delivered
Hi Muhammad, just to double check something, when you run:
$ which python3
What is the output of that command ?
** 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
Hi Albert, can you please append here the following file:
/var/log/ubuntu-advantage.log
Also, when you run:
which python3
What is the output that you see ?
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
Hi Seth, although ubuntu-advantage-tools does generate some MOTD
messages, we are not currently generating the message you are describing
here. I think it is better to tag the update-notifier package in this
bug.
However, if you think there is something we can still do on our side,
please let me
** 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 lead to unwanted behavior on those clouds, including
inability to boot to the systems.
Although
** 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
Hi Myroslav, can you please upload /var/log/ubuntu-advantage.log in this
thread so we can better debug what happened here.
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Ronnie, just some questions around this issue:
1) Does the following error happened when running: ua enable cis ?
2) What cloud are you running ua on ?
3) What is the output of: cloud-init status --long
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Incomplete
--
You
Hi slava, there is just one minor problem on the config. The cloud_type
entry is incorrectly place on under ua_config. The config should be:
contract_url: https://contracts.canonical.com
data_dir: /var/lib/ubuntu-advantage
log_file: /var/log/ubuntu-advantage.log
log_level: debug
security_url:
That's weird, the logs show the same error as before.
Can you send me your /etc/ubuntu-advantage/uaclient.conf ? I want to see
if I can reproduce that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi slava, thanks for this issue. I think we will have a more flexible
approach on how we handle that cloud-init check.
If you want to avoid having that trouble on your machine at the moment,
you can add this into /etc/ubuntu-advantage/uaclient.conf
-
settings_overrides:
Hi slava, sorry I edited my question a little bit to gather other
information about the issue. Also, I realized that you have mentioned
you are using Bionic on the bug description, so sorry for that.
But if you can provide the extra information around cloud-init, that
would be great for us to
Hi slava, thanks for reporting this.
I just want to confirm something, is this a Trusty instance ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940131
Title:
sudo ua attach is not working
To
Hi Michael, thanks for the context . I think we can try to manually run
the preinst script of the package to better understand what is failing.
Currently, I can't pinpoint an exact reason for it if you don't have any
of those files.
Also, it seems you are installing an older version of
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Triaged => New
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940128
Title:
RFE: ua enable fips skip additional packages, ease download
1 - 100 of 201 matches
Mail list logo
