** 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
The package in bionic-proposed indeed fix the issue:
root@corosync-verification:~# dpkg -l | grep corosync
ii corosync 2.4.3-0ubuntu1.3amd64
cluster engine daemon and utilities
ii libcorosync-common4:amd64 2.4.3-0ubuntu1.3
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.
Public bug reported:
[Availability]
The package is already available in Jammy, in universe for now. It
currently builds in all supported architectures:
https://launchpad.net/ubuntu/+source/ruby3.0
[Rationale]
We will be transitioning from ruby2.7 to ruby3.0 in Jammy and this will
be the
I uploaded version 1.8.7+dfsg1-3 to Debian with the needed fix but
forgot to mention this bug in the changelog to automatically close it
when it is sync'ed. Once this version lands in Jammy when can close this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is confusing Robert, is your target system running Debian Bullseye?
There is no Debian release called Bullet. Do you have any custom
configuration in the server or client side? Please provide more
information, for instance detailed steps, so we can attempt to reproduce
it.
--
You received
According to the Debian bug, ssl-cert/1.1.1 contains the fix and it is
already available in jammy (release pocket), so I am marking this as fix
released.
** Changed in: ssl-cert (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Changed in: apache2 (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/1927742
Title:
dolphin in focal can't delete webdav directories running on focal's
Thank you for taking the time to file a bug report.
From the logs we can see that in the set up process of the apache
package it tried to enabled a module and then it failed because of a
"Too many levels of symbolic links: '/etc/apache2/sites-
enabled/000-default.conf'". Could you please provide
Thank you for taking the time to file a bug report.
@guiverc is right, this seems to me a local configuration issue.
In the logs I see you first installed mariadb and then after you
installed mysql, both are not co-installable, please make sure you do
not have them installed. Moreover, in the
** Changed in: thin-provisioning-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/1950028
Title:
FTBFS against g++ 11
To manage notifications about this
** 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
I believe this specific section [1] of the SRU page can guide you
through what you need to move forward. Here is an example of a SRU bug
[2].
[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
[2] https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1948598
--
You received this
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
I am not sure if I understood your point here Simon, at the moment
Impish and Jammy have the same ruby2.7 version. Are you saying the ruby-
mysql2 build worked fine in one and failed in the other?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
For Jammy this should be fixed in the short term since we will be
transitioning to ruby3.0 and I believe we will not need this workaround
applied to ruby2.7. However, this might be an issue in Impish if we need
to SRU any ruby package which builds an extension.
--
You received this bug
@dann, the patch you mentioned is really needed to fix the issue
reported in LP #1943049. Without this patch we will not be able to
launch/build any Impish based (or greater Ubuntu version) container in
any of the supported Ubuntu releases (this is because of the glibc
version we are using).
The
Thanks for the patch Simon! I'd change a bit your proposed solution
here, I'd add g++-10 [ppc64el] to Recommends instead of gcc-10 [ppc64el]
to Depends. Let's use g++-10 to follow what doko did in the Build-
Depends, I am not sure but maybe we can find an extension which requires
a C++ compiler
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:
Could you please provide any logs for us to inspect? Also the content of
/proc/cmdline if possible?
Another thing you could do here is to test it with Hirsute or Impish to
see if you get the same problem. In Focal, we have cloud-initramfs-
tools/0.45ubuntu1 and in the latest releases we have
Thanks for the instructions on how to reproduce your case. I did run
containers in Focal and Impish in the way that you described and I
confirm that the behavior is different between them. In Focal after
bootstrapping and starting the container the lxc-console works as
expected:
ubuntu@focal:~$
Based on the comment above I believe this is a bug in the nvidia-docker
stack (coming from a third party PPA) and not in docker itself. I am
marking this bug as Invalid.
** Changed in: docker.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
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"),
After a quick look I noticed the test did not run because of an issue
with the symlink created, I blindly copied and pasted the commands you
provided. After fixing it, I am able to run the tests but it failed in
my VM because there is not enough disk space to run it. I'll be
allocating a VM with
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
Hi Ian,
Thanks for the bug report. However, I was not able to reproduce the
failure with the steps that you provided. I did the following in a Focal
VM with proposed enabled and docker.io/20.10.7-0ubuntu5~20.04.1
installed:
ubuntu@focal:~$ dpkg -l docker.io
** 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 =
Verification:
= Hirsute =
ubuntu@hirsute:~$ dpkg -l | grep docker.io
ii docker.io 20.10.7-0ubuntu5~21.04.1
amd64Linux container runtime
ubuntu@hirsute:~$ sudo docker run -it --rm ubuntu:impish
= Bionic =
# runc
ubuntu@bionic:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.6 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.6 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
= Focal =
# runc
ubuntu@focal:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
= Hirsute =
# runc
ubuntu@hirsute:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="21.04 (Hirsute Hippo)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 21.04"
VERSION_ID="21.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
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
Now there is no regression reported in any of the proposed-migration
pages. All the packages needing changes to support the libcontainer API
changes in runc built fine which I think it is enough validation for the
SRUs here (we have links for all the builds in launchpad, let me know if
I need to
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
The regressions are gone and now this is ready to land. The Test Plan
section indicates this would need to build in Hirsute and here you go:
https://launchpad.net/ubuntu/+source/golang-github-docker-go-
connections/0.4.0-2ubuntu0.21.04.1/+build/21685532
** Tags removed: verification-needed
I also needed to upload a new docker.io version targeting Bionic to fix
the autopkgtest failure. To let the debootstrap command work we need to
remove the debian-archive-keyring dependency from the basic-smoke test.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thank you for the review Sergio, opengcs was already uploaded to bionic-
unapproved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938908
Title:
Backport the container stack in Impish
To manage
** Changed in: containerd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: containerd (Ubuntu Impish)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
opengcs also needs to be patched in Bionic to support the new runc
version. Debdiff applying the same patch used in other releases is
attached.
** Patch added: "opengcs-bionic.debdiff"
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
From the logs the only thing that I got was:
Configurando apache2 (2.4.46-4ubuntu1.3) ...
info: Executing deferred 'a2enconf javascript-common' for package
javascript-common
ERROR: Conf javascript-common does not
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
From the logs is not possible to determine the root cause of your issue,
the only thing we got is:
dpkg: erro ao processar o pacote libapache2-mod-wsgi-py3 (--configure):
o subprocesso instalado, do pacote
Thanks for taking the time to file this bug and trying to make Ubuntu
better.
Good investigation work, it seems your analysis is correct, and the fix
was acknowledge by upstream. However, to incorporate this in Focal we
would need a set of steps to reproduce the bug and show to the SRU team
that
As Sergio, I was not able to reproduce the failure locally in my Focal
system. From the comments in the upstream bug it seems this is not
reliably reproducible, however, to land this fix in Focal and/or Bionic
we would need a set of steps that lead us to the bug.
@Stéphane/@Marek could you
Since this bug is affecting only Xenial and it reached end of standard
support I will be marking it as Won't Fix. Moreover, the importance is
set to Low.
** Changed in: nfs-utils (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member
Thanks Sergio. I applied all the fixes and already uploaded all the
packages. Waiting for the SRU team to review and approve them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938908
Title:
Thanks for reviewing all debdiffs Sergio. I'll will be fixing the
"Author" DEP-3 header in all patches, I was reusing them and did not
notice it.
For buildah, I missed part of the API changes, now the attached debdiff
fixed it as well.
** Attachment added:
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
For golang-github-containers-storage regression in Focal I needed to
apply some very small changes to the upstream patch to backport it and
fix the build issue (the codebase is a bit different). Debdiff is
attached.
** Patch added: "golang-github-containers-storage-focal.debdiff"
To fix the opengcs regression in Focal I was able to reuse the patch
applied in Impish and proposed here in this bug to also be applied in
Hirsute. Debdiff attached.
** Patch added: "opengcs-focal.debdiff"
I was able to use basically the same patch used in Impish to fix the
golang-github-containers-buildah build failure in Hirsute, just needed
to do some refresh. Debdiff is attached.
** Patch added: "golang-github-containers-buildah.debdiff"
For golang-github-containers-common in Hirsute, I was able to backport
an upstream patch to fix the build. However, it depends on golang-
github-containers-storage version that I attached in the debdiff above
** Patch added: "golang-github-containers-common.debdiff"
The attached debdiff fixed the API incompatibility in golang-github-
containers-storage in Hirsute.
** Patch added: "golang-github-containers-storage-hirsute.debdiff"
For opengcs in Hirsute, the patch used in Impish applied cleanly.
Debdiff attached.
** Patch added: "opengcs-hirsute.debdiff"
https://bugs.launchpad.net/ubuntu/hirsute/+source/golang-github-containers-buildah/+bug/1938908/+attachment/5533318/+files/opengcs-hirsute.debdiff
--
You received
The following packages regressed because of a libcontainer API change in
runc:
# Hirsute
- opengcs
- golang-github-containers-storage
- golang-github-containers-common
- golang-github-containers-buildah
# Focal
- opengcs
- golang-github-containers-storage
I'll be adding tasks for each of
golang-github-docker-go-connections is also blocking runc in Hirsute but
the fix is sitting in proposed for a while but should be fixed once the
new version of golang-github-containers-images disabling LTO is
accepted. More info here:
Sorry, the debdiff above is incorrect. The golang-github-containers-
image package in hirsute was uploaded disabling LTO here:
https://bugs.launchpad.net/ubuntu/bionic/+source/golang-github-
containers-image/+bug/1938908/comments/28
Once this is accepted, we will be able to land this update
This is hitting us again while backporting the container stack:
https://bugs.launchpad.net/ubuntu/bionic/+source/golang-github-
containers-image/+bug/1938908
I'll disable LTO to make it build fine on the failing architectures.
Debdiff attached.
** Patch added:
Thanks for the review Sergio, package uploaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938908
Title:
Backport the container stack in Impish
To manage notifications about this bug go to:
The attached debdiff should fix the issue pointed above.
** Patch added: "golang-github-containers-image.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/golang-github-containers-image/+bug/1938908/+attachment/5533309/+files/golang-github-containers-image.debdiff
--
You received
There is a golang-github-containers-image/5.10.3-1ubuntu1 regression in
hirsute which is not directly caused by docker.io but it is blocking it.
The tests are failing only on arm64, ppc64el and s390x due to LTO. The
simple fix here is disabling LTO in this package.
** Also affects:
** Changed in: cluster-glue (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946850
Title:
Merge cluster-glue from Deb
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946834
Title:
Merge multipath-tools f
** Changed in: containerd (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946851
Title:
Merge containerd from Debian unsta
** Changed in: fence-agents (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946858
Title:
Merge fence-agents from Deb
** Changed in: resource-agents (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946897
Title:
Merge resource-agents f
** Changed in: keepalived (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946863
Title:
Merge keepalived from Debian unsta
** Changed in: pacemaker (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946885
Title:
Merge pacemaker from Debian unsta
** Changed in: runc (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946899
Title:
Merge runc from Debian unstable for 22
** Changed in: sg3-utils (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946900
Title:
Merge sg3-utils from Debian unsta
I did backport containerd version 1.5.5-0ubuntu3 from Impish containing
also the security fix. It is already in the unapproved queue of bionic,
focal and hirsute.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Thomas,
Thanks for all the testing. The version you are using does not contain
the fix, if you check the changelog of version 20.10.7-0ubuntu1~21.04.2
you will see that this is a security fixes (coming from the security
pocket). This happened because an important CVE came up and we needed to
This is still an issue in Impish and upstream seems dead, there is no
commit in their master branch since Feb 2019.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887850
Title:
broken with current
This bug was fixed in the package ruby-fauxhai - 7.5.0-1
---
ruby-fauxhai (7.5.0-1) unstable; urgency=medium
* New upstream release (Closes: #995346).
-- Lucas Kanashiro Wed, 06 Oct 2021 16:58:36
-0300
** Also affects: ruby-fauxhai (Ubuntu)
Importance: Undecided
This was fixed in Debian in ruby-fauxhai. The issue here is a version
mismatch between ruby-chef-utils and ruby-fauxhai, updating ruby-fauxhai
to version 7.5.0-1 will solve it. To make sure ruby-chef-utils would
build fine I uploaded both of them to this PPA:
docker.io with the security fixes applied is already uploaded to bionic,
focal and hirsute unapproved queues, we need the SRU team to accept
them. The containerd package still needs to be updated, I'll be
backporting version 1.5.5-0ubuntu3 from Impish which already contains
the security fix.
Since this is affecting only Xenial and it reached the end of standard
support I am unsubscribing ubuntu-server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792298
Title:
keepalived: MISC
Thanks for taking the time to file this bug and try to make Ubuntu
better.
Could you please also share the logs? Are you running this on bare metal
or for instance in a public cloud provider?
I've found some issues on the web regarding multicast and vmac under
certain circumstances if you can
We are currently facing the same problems with Linux Virtual Machines
running Ubuntu 18.04 and 20.04, both LTS releases.
Upon examining the Event Viewer on one of the Hosts machines, there's a
critical error message:
Event ID: 18602
Source: Hyper-V-Worker
has encountered a fatal error and a
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880443
Title:
targetcli fails iscsi setup after upgrade from 18.04 to 20.04
To manage notifications about this
Since this seems to not be a blocker anymore I am lowering the
importance to low.
** Changed in: ruby-ferret (Ubuntu)
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843804
A workaround was applied to ruby2.7 which is now using gcc-10 to build
only in ppc64el. Due to that, I am setting the priority of this bug to
low.
** Changed in: ruby2.7 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The fixes are ongoing. In impish, docker.io and containerd are stuck in
-proposed because of a snapd bug which impacts their DEP-8 tests, the
snapd team is working to fix it. In the other releases, I am working to
backport the fixes to all of them, you can track the status in this bug:
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
Because Ubuntu Trusty reached End of Standard Support I am unsubscribing
ubuntu-server from 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/1356113
Title:
PHP5 session clean cron job causes
401 - 500 of 3389 matches
Mail list logo
