The 6.8.0 kernel likely has been installed via the linux-generic-
hwe-22.04 package, can you show apt policy for that one, too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085835
Title:
"Predicta
There isn't any "match" settings, we just configure the interfaces by
name, like:
network:
version: 2
ethernets:
eno5:
addresses:
- "10.11.12.1/25"
This fails when the interface is then named eno5np0 after booting with
the 6.8.x kernel. fwiw
** Package changed: horizon (Ubuntu) => horizon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045394
Title:
Installation of openstack-dashboard fails because of command failure
To manage notificat
ah, I missed the latest update, sorry. you could have just retargeted
the bug instead of creating a new one
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807784/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807783/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
Title:
i4
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807782/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807781/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/207
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807780/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807779/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807778/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/580/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807775/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807774/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
Title:
i40e
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807776/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
Title:
i40e
apport information
** Attachment added: "HookError_ubuntu.txt"
https://bugs.launchpad.net/bugs/2077159/+attachment/5807773/+files/HookError_ubuntu.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Tags added: apport-collected jammy uec-images
** Description changed:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN
mode DEFAULT group default qlen 1000
altn
** Changed in: linux-meta-hwe-6.8 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077159
Title:
i40e interfaces renamed after upgrade from hwe-6.5
To manage
This does not seem to work as expected:
user@rtr001:~$ sudo apport-collect 2077159
Please open this authorization page:
(https://launchpad.net/+authorize-token?oauth_token=XXX&allow_permission=DESKTOP_INTEGRATION)
in your browser. Use your browser to authorize
this program to access Launchpad on
Public bug reported:
Server running Ubuntu 22.04.4 LTS
Interface names with linux-image-6.5.0-21-generic 6.5.0-21.21~22.04.1:
3: eno1: mtu 9100 qdisc mq state DOWN mode
DEFAULT group default qlen 1000
altname enp102s0f0
4: eno5: mtu 1500 qdisc mq state DOWN mode
DEFAULT group default qle
The resulting repo is broken after the initial update run, but seems to
become useable after some iteration when no more updates happen.
I tested the same on 22.04 and the issue is happening in the same way
there.
** Summary changed:
- Issue with mirroring 22.04 on a 20.04 host.
+ Issue with mir
Seems that if I let it run long enough, at some point there is
zstd: /*stdout*\: Broken pipe
reading data.tar within
'/afs/.openstack.org/mirror/ubuntu/pool/main/g/gcc-11/lib32go19_11.2.0-19ubuntu1_amd64.deb'
failed: /usr/bin/unzstd exited with code 1
zstd: /*stdout*\: Broken pipe
reading data
Seems to be correct, what netmask would you expect?
** Changed in: sipcalc (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/1332541
Title:
wrong mask
To mana
Public bug reported:
Example:
$ sudo pip install glance-store
Expected result:
Find extra files in /usr/local/etc/glance
Current result:
Extra files are in /usr/etc/glance
** Affects: python3.10 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
*** This bug is a duplicate of bug 1962791 ***
https://bugs.launchpad.net/bugs/1962791
Public bug reported:
Steps to reproduce:
ubuntu@vm1:~$ sudo apt install python3-venv
ubuntu@vm1:~$ python3 -m venv vv
Actual result:
ubuntu@vm1:~$ ls vv/bin
Activate.ps1 activate activate.csh activate
We are using
ProxyPass "/placement" "unix:/var/run/uwsgi/placement-
api.socket|uwsgi://uwsgi-uds-placement-api/" retry=0
If I replace that by
ProxyPass "/placement" "unix:/var/run/uwsgi/placement-
api.socket|uwsgi://uwsgi-uds-placement-api" retry=0
things are working fine again.
--
You receiv
so the culprit seems to be CVE-2021-36160.patch , if I build the focal
version without that patch, the issue is resolved
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-36160
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
Seen with both 2.4.48-3.1ubuntu2 for impish and 2.4.41-4ubuntu3.5 for
focal.
Steps to reproduce:
- Have a request log for your app as in
https://modwsgi.readthedocs.io/en/master/user-guides/debugging-techniques.html#tracking-request-and-response
- App deployed at /app
- curl
This has been fixed upstream in release 1.5.1, why not simply update to
the new upstream version? The patch you attached is
https://review.opendev.org/c/openstack/heat-dashboard/+/694952 , you
should at a minimum show its origin.
--
You received this bug notification because you are a member of U
Likely it is not a duplicate, see my comment in #10 and in the bugzilla.
So if branch-pthread_rwlock_trywrlock-hang-23844.patch is the patch from
the bugzilla, I tested that earlier and it did not solve the issue. The
issue here seems to be with pthread_rwlock_rdlock hanging, see the
tracebacks in
Even with all these patches in, I'm still seeing messages like this with
devstack running on focal, see https://review.opendev.org/704831:
Jun 01 16:23:06.645371 ubuntu-focal-rax-dfw-0016894858
neutron-dhcp-agent[76054]: DEBUG neutron.agent.linux.utils [-] Running command:
['env', 'LC_ALL=C', 'P
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750384
Title:
Cannot Delete Recordset / Zone in ng_dns panels
To m
I agree that this is kind of expected behaviour, but I also think that
it would be good if Neutron could adopt the policy to at least bump the
minor revision number on version number updates, that would make it more
obvious to deployers that special care is needed. It should also be
accompanied by
** Changed in: cloud-archive
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/1750121
Title:
Dynamic routing: adding speaker to agent fails
To manage notif
Neutron released 14.0.4 in the meantime, do you want to include that
update here or will that go into a new bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853319
Title:
[SRU] stein stable relea
See also
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1839592 ,
there seems to also exist another bug in glibc 2.27 that is not fixed by
the patch from https://sourceware.org/bugzilla/show_bug.cgi?id=23844
** Bug watch added: Sourceware.org Bugzilla #23844
https://sourceware.org/b
So as documented in https://github.com/openvswitch/ovs-issues/issues/175
, this really seems to be a bug in glibc and not in openswitch. After
installing libc6 and related pkgs at version 2.29-0ubuntu2 (from disco),
the issue is resolved for us. The single patch from
https://sourceware.org/bugzilla
>From the discussion in https://github.com/openvswitch/ovs-
issues/issues/175 it seems like this may actually be a glibc bug
https://sourceware.org/bugzilla/show_bug.cgi?id=23844 , I'll try to get
some tests done in order to confirm this.
** Bug watch added: github.com/openvswitch/ovs-issues/issue
This is fixed in neutron-lbaas 13.0.1 and 14.0.1 for Rocky and Stein,
respectively, needs new pkgs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847981
Title:
Traceback in _create_loadbalancer_sta
The constraint comes from the "pyasn1-modules" pkg which seems to have
been pre-installed on your system, I cannot find it being installed
during your stack.sh.log, but recent versions of it seem to require
pyasn1>=0.4.6, while the stable/stein reqs cap pyasn1 at 0.4.5. So you
need to check your ma
Seems this is a version mismatch issue, I can reproduce this in a
virtualenv with
python-openstackclient==3.18.0
python-senlinclient==1.7.0
The issue simply seems to be that senlinclient needs to be updated for
stein, 1.7.0 is from rocky or older, if I install 1.9.0 or newer, the
issue goes away.
Public bug reported:
This happens sometimes when installing auditd on Ubuntu 18.04.2, most
installations work successfully, though. Re-running the install also
fixes the issue, but the failure breaks our automation. The log from the
failure looks like this:
# apt install auditd
...
Setting up aud
Public bug reported:
See also https://storyboard.openstack.org/#!/story/2006714, this issue
is seen in neutron-lbaas (v2) on Rocky UCA:
2019-10-14 08:02:16.802 18834 ERROR oslo_messaging.rpc.server Traceback (most
recent call last):
2019-10-14 08:02:16.802 18834 ERROR oslo_messaging.rpc.server
Looking at the apt log, the trigger seems to have been that this was an
upgrade from queens where only the python2 pkgs existed and didn't
install the alternative. So when installing the new package, it also
refused to overwrite the existing old binary with a symlink:
Preparing to unpack
.../pyth
Public bug reported:
The python3-neutron-dynamic-routing pkgs installs it's binary as
/usr/bin/python3-neutron-bgp-dragent while the service defined in
neutron-bgp-dragent tries to execute /usr/bin/neutron-bgp-dragent which
is directly installed only from python-neutron-dynamic-routing. The
correc
Debian bug for this is https://bugs.debian.org/837764, the small fix
should be able to be applied against the Bionic version, too.
** Bug watch added: Debian Bug tracker #837764
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837764
--
You received this bug notification because you are a me
Public bug reported:
The upstream issue for this is https://github.com/pypa/pip/issues/4195 ,
the issue only happens when pip is installed from the Ubuntu python-pip-
whl package, it disappears when replacing it with the same version from
pypi.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package
** Also affects: python-rtslib-fb (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819819
Title:
rtslib_fb.utils.RTSLibError: Cannot set dbroot to
>From the commit message https://github.com/rabbitmq/rabbitmq-
server/pull/1431 "Avoid infinite loop when dropping entries in the GM"
in 3.6.15 sounds interesting, as we do seem to see some kind of infinite
loop here. I don't have an explanation though as to why GM would be
interacting with the man
Forgot to mention: The log in /var/log/rabbitmq/rab...@hostname.log just
stops when the server hangs, no output until after it is being
restarted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783203
We are also seeing this issue after upgrading OpenStack from Pike to
Queens. It only seems to affect our larger setups, it wasn't seen during
testing on our staging setup. The good thing is that I can confirm that
disabling the management plugin seems to avoid the issue. We also have a
core dump, b
** Changed in: designate-dashboard/rocky
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/1750384
Title:
Cannot Delete Recordset / Zone in ng_dns panels
To manag
Added some further notes in
https://bugs.launchpad.net/neutron/+bug/1788185, hopefully someone can
continue from there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789045
Title:
keepalived 1:1.2.
The stable/queens tests in OpenStack run with pike UCA. Since there
seems to be no updated keepalived version in that repo, it means that
they are using 1:1.2.24-1ubuntu0.16.04.1.
I tested things manually a bit and it seems like the neutron test might
be trying to verify the broken behaviour of 1.
stable/pike (16.1.4) is also affected by this.
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765122
Title:
qemu-img execu
If it needs testing in artful in order to get fixes into Pike UCA, then
IMO your process is broken. I think I spent more than enough time on
this, if you insist to prefer keeping to distribute faulty packages, so
be it.
--
You received this bug notification because you are a member of Ubuntu
Bugs
This only seem to happen under load, so it really looks like a race
condition during the restart. Guessing the daemon finishes processing
requests before it terminates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Public bug reported:
We have several machines where unbound was updated tonight by automated
security updates to 1.5.8-1ubuntu1.1. Afterwards there was no unbound
process running, output from systemctl status says:
systemctl status unbound
I did test 2:11.0.0-0ubuntu2~cloud0 and 2:12.0.0-0ubuntu1.1~cloud0 on
Xenial. The packages seem to be identical to those in Artful and Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750121
Tit
@Chris: The test were done successfully, I just missed that tag when
updating yesterday, sorry. Should be ready to release both artful and
bionic, as well as the corresponding UCA updates.
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
You received this bu
** Tags removed: verification-needed verification-needed-artful
verification-pike-needed verification-queens-failed
** Tags added: verification-done verification-done-artful
verification-pike-done verification-queens-done
--
You received this bug notification because you are a member of Ubuntu
I still fail to reproduce this locally. Can you describe the steps that are
needed to setup your CI environment? Do you see the error only in your CI or
also when you follow the steps in [1] manually?
Is this an aio setup or are neutron-api and neutron-bgp-dragent running in
different environmen
@David: Did you also restart neutron-server after upgrading the neutron-
dynamic-routing packages? Omitting that step was the only way I could
reproduce your error during my testing on bionic.
@Corey: Do we need to place that restart into the postinst script to
make it automatic?
--
You received
@David: I have not been able to reproduce the error on xenial with
queens UCA. Your logs look like you are running without the patch
applied. Can you doublecheck that you did install the patched packages?
Can you set "debug=true" in /etc/neutron/bgp_dragent.ini and post logs
from that?
>From my PO
Ah, o.k., well for stable/pike this is actually the only patch from
11.0.0 to 11.0.1, so maybe we can keep your version there, except that
it may be confusing to users.
In 12.0.1 there is only https://review.openstack.org/544866 which I
think may be relevant for upgrades.
Anyway if you build new
@Corey: There are releases 11.0.1 and 12.0.1 containing the patch, so I
don't understand why you cherry-picked it instead of using the new
releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/175012
Sorry for taking to long to respond.
To the original reporter: If you still see this issue, please respond
with the exact steps to reproduce it, including your local.conf file and
a copy of the full output from the failing stack.sh run.
To all others: Even if you are seeing similar errors, the ca
Proposed kernels show the same improved behaviour as the earlier test
kernels.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Running the -proposed kernel on two machines now, will provide the
results in a couple of days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748408
Title:
Servers going OOM after updating kernel f
@Stefan: I haven't reproduced the issue on Artful and I don't have an
environment to do so. The original issue is for the HWE kernel on Xenial
and only for that I can perform verification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
The slow leak will probably be tolerable for the time being, having
those two patches added to the kernel would surely be a pretty valuable
step that I think should be done now. My target still is Xenial with the
hwe kernel, though. If you need to go via Artful to fix that, well, go
ahead.
--
You
The test kernel solves the issue in the same way as my own kernel
earlier, i.e. we still seem to have a very slow running memory leak with
this kernel. I'm also seeing this slow leak when I replace the in-tree
i40e driver by an upstream version (2.3.4), so either it is unrelated or
contained in bot
@dino99: Did you see my previous comment? This also affects 16.04 LTS,
so I doubt that this can be done away with as Invalid so easily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652090
Title:
S
Public bug reported:
Trying to enable the dashboard module in ceph-mrg according to this
guide https://blog.widodh.nl/2017/06/using-the-new-dashboard-in-ceph-
mgr/ I'm seeing an error in the ceph-mgr log during startup:
2018-02-28 11:27:54.507314 7fb635382680 0 ceph version 12.2.2
(cf0baba3
After running for a couple of days, it seems that we are still seeing
the slow memory leak similar to what was noticed in >= 4.14 earlier with
the patched kernel. But it won't be possible for me to bisect at that
rate.
@Joseph: Getting a patched current 4.13 still would be nice, getting
instructio
O.k., confirming that this series of patches fixes the issue:
~/linux$ git log --oneline|head -3
bc6d6fd2f916 i40e: Add programming descriptors to cleaned_count
69949b3bd674 i40e: Fix memory leak related filter programming status
b32038eb34ee UBUNTU: Ubuntu-4.13.0-32.35
Can you build the same thi
Verified on Pike deployment.
** Tags removed: verification-needed verification-needed-artful
verification-pike-needed
** Tags added: verification-done verification-pike-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Reading the thread further, we seem to need two patches, see
https://www.spinics.net/lists/netdev/msg462051.html, so I'm going to add
bc6d6fd2f916a0794ae4c44b28e14e2d172e05e0 into the build, too.
Will try that on top of b32038eb34ee42fd8056f99f88652270f6667996 (tag:
Ubuntu-4.13.0-32.35).
I also
A colleague found that this seems to be a known issue:
https://www.spinics.net/lists/netdev/msg458258.html
and the fix should be
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/drivers/net/ethernet/intel/i40e/i40e_txrx.c?id=2b9478ffc550f17c6cd8c69057234e91150f5972
I will tr
Sorry for the delay, bisecting took longer than planned, but I now have
the result:
6964e53f55837b0c49ed60d36656d2e0ee4fc27b is the first bad commit
commit 6964e53f55837b0c49ed60d36656d2e0ee4fc27b
Author: Jacob Keller
Date: Mon Jun 12 15:38:36 2017 -0700
i40e: fix handling of HW ATR evicti
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748408
Title:
Servers going OOM after updating kernel from 4.10 to 4.13
To manage notifications about this b
Public bug reported:
Starting with ceph release 12.2.2, the ceph-disk tool has been
deprecated and is to be replaced by ceph-volume, see
http://docs.ceph.com/docs/master/ceph-volume/#migrating. So the new
tools needs to be added to ceph-osd packaging.
** Affects: ceph (Ubuntu)
Importance: Un
So here are the first results:
4.11.0-041100-generic #201705041534 - not affected
4.12.0-041200-generic #201707022031 - affected
4.13.0-041300-generic #201709031731 - affected
4.13.16-041316-generic #201711240901 - affected
Results for newer kernels are not so clear, they do not fail as fast as
p
Ok, nevermind the aufs issue, I got that resolved. Should have some
results with mainline kernels in a couple of days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748408
Title:
Servers going OOM
@Joseph: I did test 4.15.2, but some things are failing, in particular
docker because of lacking AUFS support, so I need to build a kernel
myself I guess, which will take a bit.
Also note that I'm seeing this on Xenial machines, didn't test with
Artful. We used to run them with the 4.10 HWE kernel
** Summary changed:
- Servers going OOM
+ Servers going OOM after updating kernel from 4.10 to 4.13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748408
Title:
Servers going OOM after updating ker
Public bug reported:
We are seeing this on multiple servers after upgrading from previous
4.10 series HWE kernels to the new 4.13 HWE series. With the new kernel,
free memory is continously decreasing at a high rate and the servers
start swapping and finally OOMing services within days. With the 4
** Attachment added: "bad-allnodes-4.13.0-33-16G-a.png"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1748408/+attachment/5051741/+files/bad-allnodes-4.13.0-33-16G-a.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Is there a document describing how to build these UCA packages on
xenial? It is failing for me due to wrong boost library versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739002
Title:
[SRU]
** Summary changed:
- Broken eventless 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3
+ Broken eventlet 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17454
I don't agree that this is a duplicate of 1639374, it also affects plain
Ubuntu distro, tested with both 16.04.3 and 17.10. The workaround on
askubuntu.com mentioned above worked for me, but for new users it would
be really good if there was a way to make this work out of the box.
Current user exp
Proposed patch:
https://git.launchpad.net/~j-harbott/ubuntu/+source/neutron/commit/?id=287059e2c3816480d669eabb7b3243c379420aba
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736510
Title:
openvswit
Public bug reported:
During rebooting a node, neutron-openvswitch agent sometimes fails
directly after booting with a message like
2017-12-05 13:33:23.793 1388 ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-]
Tunneling can't be enabled with invalid local_ip '1.2.3.4'. IP
Same here, sample ps auxf output: http://paste.ubuntu.com/26112646/
In the upgrade there was a systemd update at the same time as the other
package update, which seems to be the trigger according to the debian
bug.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
--
You re
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501206
Title:
router:dhcp ports are open resolvers
To manage notificatio
Yes, openstack-dashboard is broken with respect to additional dashboard
packages in Newton or earlier. This was fixed for Ocata, please try with
a newer UCA version whether the issue still exists there. The fix cannot
be backported to Newton without breaking existing installations.
--
You receive
** 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/1709032
Title:
Creating conntrack entry failure with kernel 4.4.0-89
97 matches
Mail list logo
