** Changed in: cloud-init
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/1456277
Title:
cloud-init searches for
Attach file ec2-sru-20.2.45.txt.
** Attachment added: "ec2-sru-20.2.45.txt"
https://bugs.launchpad.net/bugs/1881018/+attachment/5383085/+files/ec2-sru-20.2.45.txt
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/158
Title:
document manual_cache_clean better
To manage notifications about
We are now adding all of the tests that were performed using the package in
proposed.
There is only one test that is not passing:
Attached FIPS upgrade across LTS releases
On this test we enable FIPS on xenial and then upgrade the machine to bionic.
The reason that it is failing is because we
** Attachment added: "ua-27.1-proposed.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1929597/+attachment/5504896/+files/ua-27.1-proposed.tar.xz
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy
Hi Chris, the i386 build is expected to fail on focal.
Is there a way for us to officially ignore those tests for i386 on focal ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929597
Title:
[SRU]
This test failure is expected on all releases after Focal, since we dropped
32-bit i386 support on those releases. Therefore, we are not producing the
binary package for i386 on these releases.
Because of that, we believe that we can ignore those tests and treat them not
as a regression.
Hi Joseph, looking at the logs it seems that the `cloud-id` command
failed. That command is actually provided by `cloud-init`. What is the
output of running:
$ cloud-init status --long
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.
To perform the verification I have used the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-dev
function generate_motd_message() {
message=$1
I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.
To perform the verification I have used the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-dev
function generate_motd_message() {
message=$1
I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.
To perform the verification I have used the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-dev
function generate_motd_message() {
message=$1
Hi Lukasz, those instructions were created before the package was
uploaded into ṕroposed. In the script I have used to test this bug, I
have used the proposed package.
But if needed, I can update the instructions to use the proposed
packages instead
--
You received this bug notification because
Hi Lukasz, those instructions were created before the package was
uploaded into ṕroposed. In the script I have used to test this bug, I
have used the proposed package.
But if needed, I can update the instructions to use the proposed
packages instead
--
You received this bug notification because
Hi Brian, do you have any suggestions about what could be done here ? It
seems that the problem occurred on both the /etc/os-release file and the
lsb_release command.
I don't think there is anything else we can do on that situation right ?
--
You received this bug notification because you are a
We use the distro information all over the code, for example, to perform
the check if a package is from a security pocket or if it is an ESM
package.
We also use the distro to correctly select the ESM messages we will
deliver to the user
--
You received this bug notification because you are a
** 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/1928416
Title:
Error when attaching UA ESM key
To manage notifications
Hi Phoenix, can you provide the error that you faced when enabling livepatch ?
This will probably be found on /var/log/ubuntu-advantage.log
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
=> Fix Committed
** 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/1927329
Hi Alex, I think this error is happening because cloud-init has not
fully run. I think rebooting the machines would be enough to handle that
issue.
But if you don't want to do that, you can restart cloud-init manually by
running:
DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force
cloud-init
SRU template verification
[Impact]
On a system without updates to be installed, not showing any message in motd
feels that something went wrong in the backend. Also, currently we are printing
unwanted white spaces in that scenario, which is not a good user experience
here.
[Test case]
To
Hi Ulrik, thanks for reporting this problem.
How are you creating the machines in the serves ? I just want to
understand the process you are using to reproduce the issue here and
find a fix for it.
Also, when can you also say the apt version that was being used when you
upgraded
Thank you for raising this. The change was made intentionally to reduce
noise to users when there wasn't anything to act upon. We're always
keeping an eye out for improving things and will keep this open as we
discuss ways we can make things better.
--
You received this bug notification because
https://code.launchpad.net/~lamoura/update-notifier/+git/update-
notifier/+merge/402163
** Changed in: update-notifier (Ubuntu)
Status: Confirmed => In Progress
** Changed in: update-notifier (Ubuntu)
Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)
-
Hi Domas, thanks for reporting this issue. Can I ask you which AMI id
did you use to launch the image and get this traceback ? I am unable to
reproduce it using this AMI:
ami-05b0f906c5f1814e7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Looking at the logs, I am seeing two distinct errors. One is livepatch
issue that we have:
Failed running command '/snap/bin/canonical-livepatch config remote-
server=https://livepatch.canonical.com' [exit(1)]. Message: 2021/05/04
15:18:29 error executing config: Livepatchd error: Couldn't setup
Hi Rakesh, thanks for reporting this problem. Can you please attach the content
of
/var/log/ubuntu-advantage.log file here so we can better understand how can we
tackle this issue ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
in: update-notifier (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/1926990
Title:
update-notifier should not alert us
Thank you for this Rakesh and just to be sure can you install any other
snap in your system ? Or you are only seeing that snap error when trying
to run ua attach ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
update-notifier-common does not depend on lsb-release and both
apt_check.py and apt-cdrom-check both utilize lsb_release.
The Ubuntu Error Tracker has been receiving reports about a problem regarding
update-notifier. This problem was most recently seen with
I can confirm that the xenial, bionic, focal and hirsute packages are
working as expected.
To perform the verification I have used the following script:
--
#!/bin/sh
set -x
series=xenial
name=$series-dev
function generate_motd_message() {
message=$1
Also, regarding the autopkgtest failures we are seeing, they seem related to
this update-manager bug:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1929865
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: update-notifier (Ubuntu Xenial)
Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)
** Changed in: update-notifier (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Albuquerque Medeiros de Moura (lamoura)
** Changed in: update-notifier (Ubuntu
[Impact]
Because update-notifier does not explicit have the `lsb-release` package as a
dependency, users may install the package and rely on `apt-cdrom-check` to
work, but it will fail, since it runs
the `lsb_release -sr` command on it.
[Test case]
To reproduce the issue:
1. Launch a xenial
** Description changed:
[Impact]
When users are running an ESM distro and looking at the MOTD they may be
surprised by an alert generated by update-notifier that both esm-infra and
esm-apps could be enabled in the machine to receive future updates. However,
esm-apps will not bring much to
Hi bigsicret, thanks for reporting that. We will definitely take a look
on it.
However, this bug reporting is leaking your private token.
Please, contact customer services to invalidate that token and get a new one
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
[Impact]
- This release includes bug-fixes and we would like to
- make sure all of our supported customers have access to these
- improvements. The notable ones are:
+ This release provides fixes to numerous issues encountered and reported by
users against the recent
Hi Hafeez, just to confirm, does your system have this path:
/etc/apt/sources.list.d/ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932182
Title:
Error when attaching UA
To manage notifications
Hi Rakesh, looking at the logs maybe snapd is not working as expected.
Can you please provide the output of:
systemctl status snapd.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928416
** Description changed:
[Impact]
When users are looking at MOTD messages, they might find the text confusing,
since we don't explicitly say that the security updates count are taking into
consideration both standard security pockets and ESM pockets.
[Test Case]
1. Launch the a xenial
Public bug reported:
[Impact]
When users are looking at MOTD messages, they might find the text confusing,
since we don't explicitly say that the security updates count are taking into
consideration both standard security pockets and ESM pockets.
[Test Case]
1. Launch the a xenial container
2.
** Description changed:
[Impact]
When users are looking at MOTD messages, they might find the text confusing,
since we don't explicitly say that the security updates count are taking into
consideration both standard security pockets and ESM pockets.
[Test Case]
1. Launch the a xenial
** Attachment added: "awspro-xenial-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493378/+files/awspro-xenial-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "awsgeneric-xenial-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493379/+files/awsgeneric-xenial-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "azurepro-xenial-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493382/+files/azurepro-xenial-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "azurepro-bionic-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493383/+files/azurepro-bionic-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "azuregeneric-focal-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493387/+files/azuregeneric-focal-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "azurepro-focal-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493384/+files/azurepro-focal-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "gcpgeneric-xenial-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493388/+files/gcpgeneric-xenial-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "azuregeneric-xenial-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493385/+files/azuregeneric-xenial-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "azuregeneric-bionic-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493386/+files/azuregeneric-bionic-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "awsgeneric-focal-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493381/+files/awsgeneric-focal-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "awsgeneric-bionic-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493380/+files/awsgeneric-bionic-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "gcpgeneric-bionic-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493390/+files/gcpgeneric-bionic-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "gcpgeneric-focal-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493391/+files/gcpgeneric-focal-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am now attaching the results of running all the clouds(Azure, AWS,
GCP) integration tests for this SRU of uaclient.
We have used the package uploaded in this PPA to perform the tests:
https://launchpad.net/~ua-client/+archive/ubuntu/staging/
This package should have all the same features as
** Attachment added: "awspro-bionic-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493377/+files/awspro-bionic-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "gcppro-bionic-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493392/+files/gcppro-bionic-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "gcppro-focal-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493417/+files/gcppro-focal-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "gcppro-xenial-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493415/+files/gcppro-xenial-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "gcppro-bionic-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493416/+files/gcppro-bionic-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Adding the manual for upgrading trusty to xenial, where xenial will have
the new package version that is sitting on the proposed pocket.
Also, this tests is using the first approach to fix the trusty to xenial
upgrade issue regarding the status of esm-infra:
** Attachment removed: "gcppro-bionic-out"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+attachment/5493392/+files/gcppro-bionic-out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attaching integration test run output on bionic. Note that this was
using the ua-client/staging ppa which is the functional equivalent of
the proposed release.
There is two failures in this log which we have verified is due to a
special case because using the same staging ppa that we are testing
Adding vm tests for bionic.
Those tests were executed using the package on this PPA:
https://launchpad.net/~ua-client/+archive/ubuntu/staging/
** Attachment added: "vm-bionic-out"
** Changed in: update-notifier (Ubuntu Xenial)
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/1924766
Title:
upd
** Changed in: update-notifier (Ubuntu Xenial)
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/1883315
Title:
Showing
I have tested this package for released xenial, bionic, focal and
hirsute with the following script:
--
#!/bin/sh
set -x
series=hirsute
name=$series-dev
function generate_motd_message() {
message=$1
echo "---"
Public bug reported:
When running /usr/lib/update-notifier/apt-check on a ESM machine, we
could alert the user about the existence of both esm-infra and esm-apps
if the system unauthenticated source file for both services. Therefore,
we would display a message like that in the system:
We have added the verification for Bionic and Focal using the package he have
uploaded in the staging ppa:
https://launchpad.net/~ua-client/+archive/ubuntu/staging
It should contain the same features as the package that is now uploaded
to proposed
** Tags removed: verification-needed-bionic
** Description changed:
- When running /usr/lib/update-notifier/apt-check on a ESM machine, we
- could alert the user about the existence of both esm-infra and esm-apps
- if the system unauthenticated source file for both services. Therefore,
- we would display a message like that in the system:
Hello Alex, thanks for reporting this bug. If you still have that
machine running, can you run:
ua enable livepatch
And verify if the command works. I have one hypothesis here, but if that
enable fails as well, then it cannot be what I am thinking.
--
You received this bug notification because
Also, can you please provide the livepatch logs by running:
sudo snap logs canonical-livepatch.canonical-livepatchd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927029
Title:
ua attach command
This test failure is expected on all releases after Focal, since we dropped
32-bit i386 support on those releases. Therefore, we are not producing the
binary package for i386 on these releases.
Because of that, we believe that we can ignore those tests and treat them not
as a regression.
By reusing the same script in this launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1924766
I can confirm that the xenial, bionic, focal and hirsute proposed
packages are working as expected
** Tags removed: verification-needed verification-needed-bionic
By reusing the same script in this launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1924766
I can confirm that the xenial, bionic, focal and hirsute proposed
packages are working as expected
** Tags removed: verification-needed verification-needed-bionic
Hi Robie, I just realized that I forgot to change the tag when I posted
my test process :(
This is the reason why this package is not on the -updates pocket yet,
right ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915547
Title:
Users are prompted by ucf on upgrade from Trusty to
I will further increase this SRU bug with information that is lacking on
from the original bug proposal:
[Impact]
During an upgrade from trusty to xenial, users will be prompted to make a
decision regarding the diff on unattended-upgrades. This is not a good user
experience, specially because
Thank you for this review Robie, we have now updated the package to only
ship two md5sum. The latest version of 50unattended-upgrades of Trusty
and Xenial.
I have already updated the MR with those changes and I Bryce is
reviewing that changes before uploading the new package.
--
You received
Also, please provide the userdata that you are using to configure cloud-
init too. I forgot to mention that on my last comment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917036
Title:
Some of
Hi Kalpesh, thank you for reporting this issue. Can you please provide
the cloud-init logs for the instance that is failing ? Those logs would
be cloud-init.log and cloud-init-output.log
After providing that, you can change the status of this bug to new
again.
** Changed in: cloud-init (Ubuntu)
Thanks for the review Robie,
I have tested the package on the proposed pocket by using this script:
#!/bin/sh
set -x
series=trusty
name=$series-upgrade
multipass delete $name
multipass purge
multipass launch $series --name $name
multipass exec $name -- sudo sh -c "cat
For this SRU bug I have created the following test script:
---
#!/bin/sh
set -x
series=hirsute
name=$series-dev
function update-notifier-ua-not-installed () {
# Expects this output
# x packages can be updated.
# x of these updates are security
[Impact]
when users are getting the message update-notifier message through apt-check
they may find inconsistent behavior regarding ESM products. This is misleading
since we will say to the users that they don't have ESM Infra, but they do have
ESM infra packages that can be installed. This is
Public bug reported:
[Impact]
When ESM Apps goes into production we want to be able to advertise it to our
users through MOTD.
Currently, update-notifier apt-check does not take into consideration the
exclusive packages of ESM Apps, which is a problem.
[Test case]
To reproduce the issue, you
Public bug reported:
== Begin SRU Template ==
[Impact]
When upgrading from trusty to xenial, we are prompted about config changes on
50unattended-upgrades with the following diff:
--- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08 19:21:39
+++
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 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 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
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:
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 Michael, looking at this issue, it seems that the problem is being
caused by by the preinst script. When inspecing the preinst script in
the package, I have found this:
--
#!/bin/sh
set -e
# Automatically added by dh_installdeb/11.1.6ubuntu2
dpkg-maintscript-helper rm_conffile
** 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
** 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
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:
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
** Also affects: ubuntu-advantage-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ubuntu-advantage-tools (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: ubuntu-advantage-tools (Ubuntu Focal)
Importance: Undecided
Status:
This issue should be resolved now that package 27.2.2 is out.
Let us know if that issue still persists
** Changed in: ubuntu-advantage-tools (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** 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/1938207
Title:
ubuntu-advantage-tools.postinst and cloud-id are not robust
** 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/1938137
Title:
doesnt let me enable esm or any tools of advantage
1 - 100 of 197 matches
Mail list logo
