tagging subiquity, removing base-installer
** Package changed: base-installer (Ubuntu) => ubuntu
** Package changed: ubuntu => subiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2096872
Public bug reported:
Installation of 24.04.1 LTS to Asus E200HA has bricked the laptop.
(Laptop will not POST or boot any OS from any media after installation).
Laptop specs: Intel Atom Cherry Trail, 4GB RAM, 32GB eMMC
This laptop had previously taken the following OSes without issue and
was in
** Changed in: maas/3.4
Status: Fix Committed => 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/2089185
Title:
Releasing fails with latest cloud-init on image 20241113
To manage
** Changed in: maas/3.4
Milestone: 3.4.x => 3.4.6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089185
Title:
Releasing fails with latest cloud-init on image 20241113
To manage notifications a
See also: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2083176
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940723
Title:
GRUB (re)installation failing due to stale
grub-{pc,efi}/install
I looked into this a few months ago for slightly different reasons
(juju/maas getting confused and not identifying a disk, due to differing
kernels used for install vs boot), I can confirm I found at the time
that the nvme by-id symlinks change due to backporting of the
NVME_QUIRK_BOGUS_NID quirk.
Note: This issue is more impactful than I initially realised. I was
thinking it was mainly an issue on initial deploy, but if you upgrade
your deployment to 18.2.4 and then reboot a node, the OSDs won't start,
because the ceph-volume tool is needed to activate the OSDs.
** Changed in: cloud-archiv
OK, well we learnt now that only upgrading and not doing a fresh
deployment, and only doing the ceph-mon tests is not enough. Indeed,
let's work on a more concrete/full test plan. I have some strong
thoughts for that so will discuss with you and Utkarsh, etc.
Luciano: In the mean time, can you pri
I suspect the reason this was not picked up in the SRU test, is possibly
related to code from the Squid charm being used in the test instead of
the Reef Charm.
The squid charm merged a "tactical fix" to manually install
python3-packaging in this change:
https://review.opendev.org/c/openstack/charm
I discovered this issue myself (for Reef, 18.2.4) today when running the
zaza integration test for charm-glance-simplestreams-sync against jammy-
bobcat.
According to the SRU, the charm-ceph-osd tests were run, and the package
version was verified. The question is, why did those tests not catch
th
It's not possible to correctly run two mDNS stacks at the same time, as
while multicast udp packets can be received by multiple programs, only
one program will receive unicasted port 5353 mDNS replies, even if both
daemons allow multiple-binding to port 5353.
While actually using that feature is n
See comment #10 and my #11 and #13 responses
Years ago I installed an amdgpu package from an extrnal source and had
forgotten about it.
ldd showed that libwebkit2gtk was referencing libgbm from /opt/*
The proper package is in /lib/x86_64-linux-gnu/
So I used synaptic to remove the manually insta
So now
# ldd /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 | grep libgbm
libgbm.so.1 => /lib/x86_64-linux-gnu/libgbm.so.1 (0x7fd3deade000)
shows that I am using the correct libgbm and all is well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think this is the line you (AND I) want to see
libgbm.so.1 => /opt/amdgpu/lib/x86_64-linux-gnu/libgbm.so.1
(0x7f5edb3a8000)
Thanks. I looked past that.
I had an old amdgpu library that had been locally installed gumming up
the works.
I have removed the old amdgpu packages and am
Lloyd had a mis-configured system when he filed 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/2062916
Title:
evolution has undefined symbol in newest libwebkit2gtk
To manage
Would updating to Ubuntu 23.10 be a likely fix? (I hope this the right
place to ask)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062916
Title:
evolution has undefined symbol in newest libwebkit2
The dpkg --status output is more readable
# dpkg --status libgbm1
Package: libgbm1
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 148
Maintainer: Ubuntu Developers
Architecture: amd64
Multi-Arch: same
Source: mesa
Version: 23.2.1-1ubuntu3.1~22.04.2
Depends: libc6 (>
Viraniac,
Thanks for your interest.
I am not using any proprietary graphics drivers.
# ls -al /lib/x86_64-linux-gnu/libgbm*
lrwxrwxrwx 1 root root15 Jan 24 07:01 /lib/x86_64-linux-gnu/libgbm.so.1 ->
libgbm.so.1.0.0
-rw-r--r-- 1 root root 64720 Jan 24 07:01 /lib/x86_64-linux-gnu/libgbm.so.1.
$ ldd -r $(which gnucash) | tail
undefined symbol: gbm_bo_create_with_modifiers2
(/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37)
undefined symbol: gbm_bo_get_fd_for_plane
(/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37)
So there are two missing symbols. The output for evolution shows the
gnucash also suffers from the same problem
gnucash: symbol lookup error: /lib/x86_64-linux-
gnu/libwebkit2gtk-4.0.so.37: undefined symbol:
gbm_bo_create_with_modifiers2
This gets more critical for me personally. There are alternatives for
handling email. I have no easy replacement for gnucash.
** Package changed: webkit2gtk (Ubuntu) => evolution (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062916
Title:
evolution has undefined symbol in newest libwebkit2gtk
To manage notifica
** Project changed: libwebkitnode => webkit2gtk (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062916
Title:
evolution has undefined symbol in newest libwebkit2gtk
To manage notifications
Closing as 14.04 has been out of support for a while.
** Changed in: maas-images
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508565
Title:
maas uses 3.13 (hwe
Closing as all referenced software versions are EOL.
Issue has not been reported in supported versions, assumed no longer a problem.
** Changed in: maas-images
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
*** This bug is a duplicate of bug 1823281 ***
https://bugs.launchpad.net/bugs/1823281
** This bug has been marked a duplicate of bug 1823281
perf-archive is not shipped in the linux-tools package
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977669
Title:
Metadata broken for SR-IOV external ports
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
** Description changed:
OpenStack Usurri/OVN SR-IOV instances are unable to connect to the
metadata service despite DHCP and normal traffic work.
The 169.254.169.254 metadata route is directed at the DHCP port IP, and
no arp reply is received by the VM for this IP. Diagnosis finds that
Public bug reported:
OpenStack Usurri/OVN SR-IOV instances are unable to connect to the
metadata service despite DHCP and normal traffic work.
The 169.254.169.254 metadata route is directed at the DHCP port IP, and
no arp reply is received by the VM for this IP. Diagnosis finds that the
ARP reply
With regards to the patch here:
https://lists.linuxfoundation.org/pipermail/iommu/2021-October/060115.html
It is mentioned this issue can occur if you are passing through a PCI
device to a virtual machine guest. This patch seems like it never made
it into the kernel. So I am curious if you are usi
Public bug reported:
Processes inside of LXD containers are incorrectly identified as needing
a restart on jammy. The cause is that needrestart does not correctly
parse cgroups v2.
Since needrestart is installed in a default install, this is problematic
as it prompts you to restart and actually r
Where is the discussion happening?
I ran the same benchmarks for my i7-6770HQ 4-core system. This really
needs revising.
While disk space using in /boot is a concern, in this example at least
-10 would use only 8MB (10%) more space and cut the time taken from 2m1s
to 13s.
zstd.0 84M 0m2.150s
zst
Thanks for the information and glad to hear this has already been
addressed. I'm all for cleaning up cruft.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918421
Title:
netplan does not match multip
Unfortunately the patch to netplan.io in PR 202 has not quite fixed the
original issue and actually breaks existing Jammy Pi installs when the
package is upgraded. The version of /etc/netplan/10-rpi-ethernet-
eth0.yaml shipped in the image uses the whitespace-separated driver line
which the maintai
Re-installing from scratch should resolve the issue. I suspect in most
cases if you install with the 21.10 installer (even though it has the
old kernel) as long as you install updates during the install this issue
probably won't hit you. It mostly seems to occur after a reboot and it's
loading data
Most shells (including bash, zsh) have a built-in for kill so it's done
internally. Some shells don't so it executes /bin/kill instead which has
this issue.
One comment noted this was fixed at some point in 2013 in version 3.3.4
but it apparently broke again at some point and is broken at least in
Thanks for the data. I can see you queried 'steven-ubuntu.local' and
that looks like the hostname of the local machine. Can you also query
the hostname of the AFP server you are trying to connect to (using both
getent hosts and avahi-resolve-host-name).
--
You received this bug notification becau
As a side note, it may be time to switch to a new protocol. As even
Apple has dropped support for sharing AFP versions in the last few
releases and is deprecating it's usage. You can use Samba to do SMBFS
including the extra special apple stuff if you need timemachine support
etc on your NAS
--
Y
To assist with this can you get the following outputs from the broken
system:
# Change 'hostname.local' to the hostname expected to work
cat /etc/nsswitch.conf
systemctl status avahi-daemon
journalctl -u avahi-daemon --boot
avahi-resolve-host-name hostname.local
getent hosts hostname.local
*
Subscribing Marc as he seems to be largely maintaining this and made the
original changes and has been keeping the delta. Hopefully he can
provide some insight.
Seems this is a delta to Debian that is being kept intentionally for a
long time, it's frequently in the changelog even in the most recen
Just noticed this today, it's still the same on Ubuntu 20.04. The
default sudoers file ships the admin group having sudo privileges but
the group doesn't exist by default.
While it doesn't have out of the box security implications, I think this
is a security concern as someone could potentially ad
To make life easier, on the problem Ubuntu machine, I installed ssh server:
sudo apt install openssh-server
and left an open ssh connection to it from another RPi.
When the Ubuntu machine display froze, the OS itself was still running, and
from other machine, I unlocked the Ubuntu lockup with
** Description changed:
- Running pflogsumm 1.1.5-1 on Ubuntu 20.04.2 against log messages from
+ Running pflogsumm 1.1.5-1 on Ubuntu 16.04 against log messages from
yesterday throws the following messages:
Use of uninitialized value $domain in string eq at /usr/sbin/pflogsumm line
1546, <
Public bug reported:
Running pflogsumm 1.1.5-1 on Ubuntu 20.04.2 against log messages from
yesterday throws the following messages:
Use of uninitialized value $domain in string eq at /usr/sbin/pflogsumm line
1546, <> line 131435.
Use of uninitialized value $domain in substitution (s///) at
/usr
This looks like a duplicate of this:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931660
Title:
PANIC at zfs_znode.c:339:zfs_znode_
In a related way say you wanted to recover a system from a boot disk,
and copy all the data off to another disk. If you use a sequential file
copy like from tar/cp in verbose mode and watch it, eventaully it will
hang on the file triggering the issue (watch dmesg/kern.log). Once that
happens, move
So to be clear this patch revert fixes the issue being caused new, but,
if the issue already happened on your filesystem it will continue to
occur because the exception is reporting corruption on disk. I don't
currently have a good fix for this other than to move the affected files
to a directory y
Have created a 100% reliable reproducer test case and also determined
the Ubuntu-specific patch 4701-enable-ARC-FILL-LOCKED-flag.patch to fix
Bug #1900889 is likely the cause.
[Test Case]
The important parts are:
- Use encryption
- rsync the zfs git tree
- Use parallel I/O from silversearcher-ag
While trying to setup a reproducer that would excercise chrome or wine
or something I stumbled across the following reproducer that worked
twice in a row in a libvirt VM on my machine today.
The general gist is to
(1) Create a zfs filesystem with "-o encryption=aes-256-gcm -o compression=zstd
-o
34 more user reports on the upstream bug of people hitting it on Ubuntu 5.13.0:
https://github.com/openzfs/zfs/issues/10971
I think this needs some priority. It doesn't seem like it's hitting
upstream, for some reason only really hitting on Ubuntu.
--
You received this bug notification because y
@Colin To be clear this is the same bug I originally hit and opened the
launchpad for, it just doesn't quite match with what most people saw in
the upstream bugs. But it seemed to get fixed anyway for a while, and
has regressed again somehow.
Same exception as from the original description and oth
There is a systemd option that I think will solve this issue.
https://www.freedesktop.org/software/systemd/man/systemd.unit.html#RefuseManualStart=
RefuseManualStart=, RefuseManualStop=
Takes a boolean argument. If true, this unit can only be activated or
deactivated indirectly. In this case, ex
In terms of understanding when this was fixed for what users/versions.
Assuming that MAAS is copying the curtin version from the server, to the
deployed client, which I think is the case, you need to get an updated
Curtin to the MAAS server.
The bug was fix released into curtin 20.1-20-g1304d3ea-0
I traced the call failure. I found the failing code is in
sa.c:1291#sa_build_index()
if (BSWAP_32(sa_hdr_phys->sa_magic) != SA_MAGIC) {
This code prints debug info to /proc/spl/kstat/zfs/dbgmsg, which for me is:
1629791353 sa.c:1293:sa_build_index(): Buffer Header: cb872954 !=
This has re-appeared for me today after upgrading to 5.13.0-14 on
Impish. Same call stack, and same chrome-based applications (Mattermost
was hit first) affected.
Not currently running DKMS, so:
Today:
5.13.0-14-lowlat Tue Aug 24 10:59 still running (zfs module is 2.0.3-8ubuntu6)
Yesterday:
5.
Try the zfs_recover step from Colin's comment above. And then look for
invalid files and try to move them out of the way.
I'm not aware of encrypted pools being specifically implicated (no such
mention in the bug and it doesn't seem like it), having said that, I am
using encryption on the dataset
Seems there is a good chance at least some of the people commenting or
affected by this bug are duplicate of Bug #1839592 - essentially a libc6
bug that meant threads weren't woken up when they should have been.
Fixed by libc6 upgrade to 2.27-3ubuntu1.3 in bionic.
--
You received this bug notific
Hello,
I can confirm that I'm running the fixed version on Bionic but am still
experiencing the same issue when using clamdscan --multiscan --fdpass
with ExcludePath in /etc/clamav/clamd.conf:
dpkg:
ii clamav 0.103.2+dfsg-0ubuntu0.18.04.2
Output:
clamdscan --multiscan --fdpass /
/proc: Exclude
Are you confident that the issue is a new issue? Unfortunately as best I
can tell, the corruption can occur and then will still appear on a fixed
system if it's reading corruption created in the past that unfortunately
scrub doesn't seem to detect.
I've still had no re-occurance here after a few w
Public bug reported:
I was running do-release-upgrade to upgrade my 18 LTS system to 20 LTS
so that I can run a new version of MAAS.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: maas 2.8.5-8600-g.efb54078a-0ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-142.146-generic 4.15.18
U
** Changed in: ubuntu-keyring (Ubuntu)
Importance: Undecided => Critical
** Changed in: ubuntu-keyring (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920640
Updated the following wiki pages:
https://wiki.ubuntu.com/Debug%20Symbol%20Packages
https://wiki.ubuntu.com/DebuggingProgramCrash
With the note:
Note: The GPG key expired on 2021-03-21 and may need updating by either
upgrading the ubuntu-dbgsym-keyring package or re-running the apt-key command.
Just to make the current status clear from what I can gather:
- The GPG key was extended by 1 year to 2022-03-21
- On Ubuntu Bionic (18.04) and newer the GPG key is normally installed
by the ubuntu-dbgsym-keyring package (on 18.04 Bionic onwards). This
package is not yet updated. An update to thi
I got another couple of days out of it without issue - so I think it's
likely fixed.
It seems like this issue looks very similar to the following upstream bug, same
behaviour but a different error, and so I wonder if it was ultimately the same
bug. Looks like this patch from 2.0.3 was pulled int
I have specifically verified that this bug (vlan traffic interruption
during restart when rabbitmq is down) is fixed by the package in bionic-
proposed. Followed my reproduction steps per the Test Case and all
traffic to instances stops on 12.1.1-0ubuntu3 and does not stop on
12.1.1-0ubuntu4
But n
When using DVR-SNAT, a simple neutron-l3-agent gateway restart triggers
this issue.
Reproduction Note: Nodes with an ACTIVE or BACKUP (in the case of L3HA)
router for the network are not affected by this issue, so a small 1-6
node environment may make this difficult to reproduce or only affect
hal
Looking to get this approved so that we can verify it, as needing this
ideally released by the weekend of March 27th for some maintenance
activity. Is something holding back the approval?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's worth noting that, as best I can understand, the patches won't fix
an already broken filesystem. You have to remove all of the affected
files, and it's difficult to know exactly what files are affected. I try
to guess based on which show a ??? mark in "ls -la". But sometimes the
"ls" hangs, et
I hope this helps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918018
Title:
package linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 failed to
install/upgrade: installed linux-image-5.8.0-44-ge
Public bug reported:
Trying to use synaptic to install NVIDIA gpu driver
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
NonfreeKernelMod
E-mailed upstream for assistance:
https://mail.openvswitch.org/pipermail/ovs-discuss/2021-February/050963.html
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916708
Title:
udpif
Public bug reported:
The udpif_revalidator thread crashed in ofpbuf_resize__ on openvswitch
2.9.2-0ubuntu0.18.04.3~cloud0 (on 16.04 from the xenial-queens cloud
archive, backported from the 18.04 release of the same version). Kernel
version was 4.4.0-159-generic.
The issue is suspected to still e
Attaching revised SRU patch for Ubuntu Bionic, no code content changes
but fixed the changelog to list all 3 bug numbers correctly.
** Patch added: "neutron SRU patch for Ubuntu Bionic (new version)"
https://bugs.launchpad.net/neutron/+bug/1869808/+attachment/5464699/+files/lp1869808-bionic.de
Ubuntu SRU Justification
[Impact]
- When there is a RabbitMQ or neutron-api outage, the neutron-
openvswitch-agent undergoes a "resync" process and temporarily blocks
all VM traffic. This always happens for a short time period (maybe <1
second) but in some high scale environments this lasts for m
SRU proposed for Ubuntu Bionic + Cloud Archive (Queens) for the following 3
bugs:
Bug #1869808 reboot neutron-ovs-agent introduces a short interrupt of vlan
traffic
Bug #1887148 Network loop between physical networks with DVR (Fix for fix to
Bug #1869808)
Bug #1871850 [L3] existing router resour
I can confirm 100% this bug is still happening with 2.0.1 from hirsute-
proposed, even with a brand new install, on a different disk (SATA SSD
instead of NVMe Intel Optane 900p SSD), using 2.0.1 inside the installer
and from first boot. I can reproduce it reliably within about 2 hours
just using th
Using 2.0.1 from hirsute-proposed it seems like I'm still hitting this.
Move and replace .config/google-chrome and seems after using it for a
day, shutdown, boot up, same issue again.
Going to see if I can somehow try to reproduce this on a different disk
or in a VM with xfstests or something.
--
This issue seems to have appeared somewhere between zfs-linux
0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16.
When the issue first hit, I had zfs-dkms installed, which was on
0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed
zfs-dkms to go back to the kerne
Accidentally posted the above comment in the wrong bug, sorry, was meant
for https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476 -
where I suspect this bug as having caused a regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
This issue seems to have appeared somewhere between zfs-linux
0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16.
When the issue first hit, I had zfs-dkms installed, which was on
0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed
zfs-dkms to go back to the kerne
Another user report here:
https://github.com/openzfs/zfs/issues/10971
Curiously I found a 2016(??) report of similar here:
https://bbs.archlinux.org/viewtopic.php?id=217204
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I hit this problem again today, but now without zfs-dkms. After
upgrading my kernel from initrd.img-5.8.0-29-generic to 5.8.0-36-generic
my Google Chrome Cache directory is broken again, had to rename it and
then reboot to get out of the problem.
** Changed in: zfs-linux (Ubuntu)
Importance: Un
This issue appears to be documented here:
https://docs.ceph.com/en/latest/releases/nautilus/#instructions
Complete the upgrade by disallowing pre-Nautilus OSDs and enabling all
new Nautilus-only functionality:
# ceph osd require-osd-release nautilus
Important This step is mandatory. Failure to ex
** Attachment added: "blktrace-lp1907262.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+attachment/5442212/+files/blktrace-lp1907262.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I can reproduce this on a Google Cloud n1-standard-16 using 2x Local
NVMe disks. Then partition nvme0n1 and nvne0n2 with only an 8GB
partition, then format directly with ext4 (skip LVM).
In this setup each 'check' takes <1 min so speeds up testing
considerably. Example details - seems pre-emptible
Should mention that Chrome itself always showed "waiting for cache" part
of backing up the story around the cache files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906476
Title:
PANIC at zfs_zno
Public bug reported:
Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
panic in the kernel log which was also hanging Disk I/O for all
Chrome/Electron Apps.
I have narrowed down a few important notes:
- It does not happen with module version 0.8.4-1ubuntu11 built and included
Note: This patch has related regressions in Hirsute due to the version number
containing a space:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1906245
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1905377
Seems the patch is temporarily dropped will need to ensure we don't
totally los
I am experiencing this as well, it worked on 20.04 Focal and is broken
on 20.10 Groovy and 21.04 Hirsute as of today with the latest Hirsute
packages.
I am using GNOME with a Logitech T650 touchpad. If I unplug and replug
the receiver it forgets again. I then have to toggle both natural
scrolling
For clarity my findings so far are that:
- The package upgrade stops pacemaker
- After 30 seconds (customised down from 30min by charm-hacluster), the
stop times out and pretends to have finished, but leaves pacemaker
running (due to SendSIGKILL=no in the .service intentionally set
upstream to p
With regards to Billy's Comment #18, my analysis for that bionic
sosreport is in Comment #8 where I found that specific sosreport didn't
experience this issue - but I found most likely that node was suffering
from the issue occuring on the MySQL nodes it was connected to - and the
service couldn't
** Changed in: charm-hacluster
Status: New => Confirmed
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Invalid
** Summary changed:
- upgrade from 1.1.14-2ubuntu1.8 to 1.1.14-2ubuntu1.9 breaks clusters
+ pacemaker left stopped after unattended-upgrade of pacemaker
(1.1.14-2
For the fix to Bug #1654403 charm-hacluster sets TimeoutStartSec and
TimeoutStopSync for both corosync and pacemaker, to the same value.
system-wide default (xenial, bionic): TimeoutStopSec=90s TimeoutStartSec=90s
corosync package default: system-wide default (no changes)
pacemaker package default
I misread and the systemd unit is native, and it already sets the following
settings:
SendSIGKILL=no
TimeoutStopSec=30min
TimeoutStartSec=60s
The problem is that most of these failures have been experienced on juju
hacluster charm installations, which are overriding these values
$ cat ./systemd/
Analysed the logs for an occurance of this, the problem appears to be
that pacemaker doesn't stop after 1 minute so systemd gives up and just
starts a new instance anyway, noting that all of the existing processes
are left behind.
I am awaiting the extra rotated logs to confirm but from what I can
I reviewed the sosreports and provide some general analysis below.
[sosreport-juju-machine-2-lxc-1-2020-11-10-tayyude]
I don't see any sign in this log of package upgrades or VIP stop/starts,
I suspect this host may be unrelated.
[sosreport-juju-caae6f-19-lxd-6-20201110230352.tar.xz]
This is a
I have verified the package for this specific virtio-balloon issue
discussed in this bug only.
Migrating from 3.1+dfsg-2ubuntu3.2~cloud0
- To the latest released version (3.1+dfsg-2ubuntu3.7~cloud0) fails due to
balloon setup
2020-10-26T07:40:30.157066Z qemu-system-x86_64: get_pci_config_device
There is an indication in the below RHBZ this can actually prevent
openvswitch from working properly as it loses too much CPU time to this
processing in large environments (100s or 1000s of ports)
https://bugzilla.redhat.com/show_bug.cgi?id=1737982
Seems to be a rejected upstream patch here, uncl
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896734
Title:
A privsep daemon spawned by neutron-openvswitch-agent hangs when debug
logging is enabled (large number of registere
I hit this too, after restart to fix it I also lose all my stored
metrics from the last few days. So going to triage this as High.
** Changed in: graphite-carbon (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I think the issue here is that Stein's qemu comes from Disco which was
EOL before Bug #1848497 was fixed and so the change wasn't backported.
While Stein is EOL next month the problem is this makes live migrations
fail which are often wanted during OpenStack upgrades to actually get
through Stein
1 - 100 of 895 matches
Mail list logo
