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 confirmed the golang-github-docker-go-connections regression in
Hirsute and I filed another SRU bug to fix it:
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-
connections/+bug/1930891
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
After further discussion within the team we decided that using
ubuntu0.21.04.1 is the best option here. There is the unlikely but
possible case where -3 is removed from impish-proposed and Impish gets
released with -2.
** Attachment added: "debdiff3"
Thanks for taking another look on this Utkarsh!
We append ubuntu0.XX.YY.1 to the version string when we have the same
version in 2 releases but in this case this version was released only in
Hirsute, Impish was not released yet :)
I'll be uploading the last debdiff I attached.
--
You received
There you go, the attached debdiff has some DEP-3 headers in the added
patch.
** Attachment added: "debdiff2"
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+attachment/5502460/+files/debdiff2
--
You received this bug notification because you are
I tried to just import the patch added by the Debian maintainer with no
changes but I think it is better to add some DEP-3 headers as you
mentioned. Checking the upstream bug tracker I noticed I filed this very
same bug some months ago :) but no replies so far:
The attached debdiff adds the patch to skip the tests as mentioned in
the description and fixes the FTBFS.
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/golang-github-docker-go-connections/+bug/1930891/+attachment/5502458/+files/debdiff
** Description changed:
+
Public bug reported:
golang-github-docker-go-connections is FTBFS in Hirsute because a couple
of tests rely on an expired certificate. This failure is blocking the
runc migration.
The Debian maintainer fixed it in the next revision but it did not make
into Hirsute. The simple fix is to backport
** 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
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.
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
** 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
Thanks for the testing Colin!
FYI I already uploaded the fix to Impish (development release) and as
soon it lands in the release pocket I can start the SRUs. At the moment
it is blocked by one regression:
https://people.canonical.com/~ubuntu-archive/proposed-
Thanks for the patches Sergio. The changes LGTM, the patch was provided
by upstream (more like a workaround for the stable release) and they
said it'd be safe.
A small thing I'd fix in the changelog of both packages is to align the
text better. Instead of:
* Fix FTBFS with OpenLDAP 2.5. (LP:
The maintainer will be uploading a fixed version (0.1.2-1) to Debian. We
will need to sync it when it gets available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929613
Title:
Unblock version
The description of this bug was updated after the renaming of the binary
packages happened. Now we have src:fence-agents providing the following
binary packages in Impish:
- fence-agents (transitional package)
- fence-agents-common
- fence-agents-base
- fence-agents-extra
If I got everything
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,
There is still an issue with non-amd64 architectures. I filed a bug
upstream to start a discussion:
https://github.com/bdrung/bdebstrap/issues/2
** Bug watch added: github.com/bdrung/bdebstrap/issues #2
https://github.com/bdrung/bdebstrap/issues/2
--
You received this bug notification
** 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
Thanks for the review Andreas! Package uploaded:
$ dput ubuntu ../bdebstrap_0.1.1-2ubuntu1_source.changes
Checking signature on .changes
gpg: ../bdebstrap_0.1.1-2ubuntu1_source.changes: Valid signature from
F823A2729883C97C
Checking signature on .dsc
gpg: ../bdebstrap_0.1.1-2ubuntu1.dsc: Valid
The attached debdiff fixes the regression.
autopkgtest is happy now:
autopkgtest [17:59:38]: summary
unittest PASS
examples PASS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/bdebstrap/+bug/1929613/+attachment/5500320/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929613
Title:
Public bug reported:
bdebstrap/0.1.1-2 is blocked in impish-proposed because of a missing
autopkgtest dependency on debian-archive-keyring.
I submitted a PR to upstream to fix this and it was already merged:
https://github.com/bdrung/bdebstrap/commit/91c4ac2a3b67e835eb628f11680bb9df17bf1e2f
Thanks for taking the time to file this bug.
Your analysis seems right and there is nothing we can do as Ubuntu,
upstream decided to remove that option and we cannot support it without
upstream. What you need to do is to avoid the usage of the
NO_AUTO_CREATE_USER sql_mode option if you want to
Thanks for the heads-up Graham. Our team will be taking a look at it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912390
Title:
[Patch] TLS/DTLS: inconsistent allowed_uses behaviour when in
Thanks for the heads-up Graham. Our team will be taking a look at it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912389
Title:
[Patch] SIGSEGV: crash when certificate contains extension longer
This bug is still here in Ubuntu 20.04. Is there anything I could do to
help to add the patch and fix the bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/461354
Title:
finger doesn't support
** 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
[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
** Changed in: runc (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: runc (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: runc (Ubuntu Groovy)
Assignee: (unassigned) => Lucas Kanashiro (lucas
21-05-05T00:48:31.826412096Z" level=error msg="get state for
f90f054966ab6b78304797d420a1f948c85e5b6e425037417f8966c08cd9a0f1"
error="context deadline exceeded: unknown"
```
This version of runc triggered the problem:
```
runc (1.0.0~rc93-0ubuntu1~20.04.1) foc
** Description changed:
+ [Impact]
+
+ Users cannot check the runc version running 'runc --version'. This is
+ not a big deal but it would land along with LP #1927219 which is an
+ important fix.
+
+ [Test Plan]
+
+ Check if 'runc --version' returns the runc version.
+
+ [Where problems could
** Also affects: runc (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Focal)
** Also affects: runc (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: runc (Ubuntu Groovy)
Thanks for taking the time to file this bug.
This is a known issue and I already addressed it in my PPA where I am
preparing the next version to be uploaded to the archive:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/container-
stack/+packages
Therefore, this will be fixed soon across
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.
@Colin I updated my PPA with version 1.0-rc95 which also contains the
fix for CVE-2021-30465. Could you test this new version and make sure
your regression is fixed?
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30465
--
You received this bug notification because you are a
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
*** This bug is a duplicate of bug 1928635 ***
https://bugs.launchpad.net/bugs/1928635
Thank you for taking the time to file a bug report.
After checking the logs the only thing relevant to your problem was this
part of the apt log:
Setting up mysql-server-8.0 (8.0.25-0ubuntu0.20.04.1) ...
Thank you for taking the time to file a bug report.
After checking the logs the only thing relevant to your problem was this
part of the apt log:
Setting up mysql-server-8.0 (8.0.25-0ubuntu0.20.04.1) ...
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 8278
Error:
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
ubuntu-advantage-tools does not provide only a way to enable ESM, it
also provides a bunch of other services (from the project README):
"The Ubuntu Advantage client provides users with a simple mechanism to
view,
Thank you for taking the time to file a bug report.
I created a Bionic container to test the upgrade of mysql version
5.7.21-1ubuntu1 to 5.7.34-0ubuntu0.18.04.1 and it worked as expected:
root@mysql-test:~# apt list --upgradable
Listing... Done
mysql-server-5.7/bionic-updates,bionic-security
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
** Description changed:
[Impact]
- This feature allows the use of other mechanisms to deal with failures.
+ This feature allows the use of other mechanisms to deal with failures
instead of fencing nodes (usually reboot a machine), and let for
instance MS SQL server handle some failures
** Description changed:
+ [Impact]
+
+ This feature allows the use of other mechanisms to deal with failures.
+ instead of fencing nodes (usually reboot a machine), and let for
+ instance MS SQL server handle some failures by itself. We can consider
+ this SRU as part of a "hardware enablement"
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
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
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.
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
=> 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
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
Thanks for raising this issue. The VERSION file is not missing but we
are not using the upstream Makefile to build the source, that's why the
version is not set.
I fixed this issue and uploaded the fix to my PPA (it might take some
minutes to get it published), now if you update the runc package
I updated the runc package to version 1.0-rc94 and it is available in
this PPA for testing:
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/container-stack
Let me know if this indeed fix your issue. If yes, I'll update runc in
the development release (a.k.a. impish) and then start the SRU
I just noticed you filed a new bug here:
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1927982
I replied to the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857404
Title:
Thank you for taking the time to file a bug report.
The error in the log is the following:
Setting up mysql-server-8.0 (8.0.23-0ubuntu0.20.04.1) ...
update-alternatives: error: alternative path /etc/mysql/mysql.cnf doesn't exist
[1mdpkg:[0m error processing package mysql-server-8.0
Thank you for taking the time to file a bug report and try to make
Ubuntu better.
The configuration process did hang in this part of the postinst script:
# We switched over to modules-load.d logic, so we have to take
# care of this in postinst now.
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
This bug is present in Debian as well and Ubuntu currently does not make any
changes to the Debian package. Therefore, this bug would be best fixed
directly in Debian, and then Ubuntu will pick up the fix
Thanks for the investigation! It seems that a bunch of regressions were
found in 1.0.0~rc93 as we can see in the 1.0.0~rc94 release notes:
"This release fixes several regressions found in v1.0.0-rc93. We
recommend users update as soon as possible."
@Tanmay, you did not provide some useful information. What are you
trying to achieve? What did you do? Did you change any default settings?
Without these kind of info we cannot distinguish this from a local
config issue or a real bug. Moreover, this should be reported as a
separate bug since this
Also please keep in mind that the usage of pcs is still not fully
supported by the Ubuntu community, we still recommend crmsh:
https://ubuntu.com/server/docs/ubuntu-ha-introduction
If you want to prepare a package to apply the upstream patch Paride
linked I'll be happy to review/sponsor it. For
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)
-
Thanks for the review Dan! Some comments below:
- I'll make sure the Server team is subscribed to this package.
- Regarding the CVE-2019-10153 fix, it is mentioned in the changelog:
$ cat debian/changelog | grep -B2 -A4 CVE-2019-10153
fence-agents (4.3.3-2) unstable; urgency=high
*
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
FWIW I submitted a pacemaker merge proposal which add changes to
recommend fence-agents-supported. Since pacemaker is already in main the
fence-agents-supported package will need to be pulled in.
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/pacemaker/+git/pacemaker/+merge/402284
--
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
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
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
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
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.
** 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:
** Also affects: libvirt via
https://gitlab.com/libvirt/libvirt/-/issues/160
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692458
Title:
[21.10
** Changed in: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided => Low
** 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.
Public bug reported:
[Availability]
fence-agents is present in the Ubuntu archive since Precise, it builds
fine and tests pass in all supported architectures. It was promoted in
Precise:
https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/897492
In Trusty it was demoted, not sure about
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:
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"
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 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-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.
** 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.
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
** 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.
** 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: "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.
** 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-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-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: "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: "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: "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: "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: "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: "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: "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: "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: "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.
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
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
701 - 800 of 3415 matches
Mail list logo
