Public bug reported:
On several machines running pacemaker with corosync, after the package was
upgraded by unattended-upgrades, the VIPs were gone.
Restarting pacemaker and corosync didn't help, because some processes (lrmd)
remained after the stop.
Manually killing them allowed to restart in a
I could reproduce the panic with a loop of ipset destroys / swaps / restores
and then saves in another. Standard xenial machines consistently panic within a
few minutes max.
With the same loops and the proposed kernel, I got them running overnight
without any issues.
I'll check with Joel and if
** 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/1793753
Title:
kernel panic - null pointer dereference on ipset oper
Public bug reported:
Hi,
We've experienced crashes on machines running iptables using ipsets.
We could get a trace from the console on one of them (attached file
kernel-trace.txt).
On these machines, some ipset commands are automatically run to update the
sets, and/or to dump them (ipset resto
Hi,
It still gives the same behavior.
I ssh'd into the machine and syslog shows the following:
Apr 10 09:00:34 machine-name kernel: [ 78.597093] x86/PAT: ipmi-locate:2583
map pfn expected mapping type uncached-minus for [mem 0xbde1d000-0xbde1dfff],
got write-back
Apr 10 09:00:34 machine-name
Thanks, I could commission and deploy the machine after disabling the BMC
configuration step.
After the machine booted, I manually installed impitool and ran 'ipmitool lan
print' successfully.
After that, I released the machine, and commissioned again with the options
"Skip configuring supporte
Just re-deployed the machine to check that it worked with the same kernel, and
it does:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename: bionic
$ uname -r
4.15.0-96-generic
--
You received this bug noti
Hi,
I just tested on a fresh deployment, upgraded python-django-horizon,
openstack-dashboard, and openstack-dashboard-ubuntu-theme to 2:9.1.2-0ubuntu2.
After:
apt-get install python-django-horizon=2:9.1.2-0ubuntu2
openstack-dashboard=2:9.1.2-0ubuntu2
openstack-dashboard-ubuntu-theme=2:9.1.2-0
Public bug reported:
This is on a xenial host, with ESM updates (all packages up-to-date).
Upgrade from 18.06.1-0ubuntu1.2~16.04.1 to 18.09.7-0ubuntu1~16.04.9+esm1.
Due to dependency changes, the upgrade also installs containerd
1.2.6-0ubuntu1~16.04.6 and runc
1.0.0~rc7+git20190403.029124da-0ubu
** Attachment added: "apt-install-logs.txt"
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1956223/+attachment/5550826/+files/apt-install-logs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
10 matches
Mail list logo