[Bug 1927868] Re: vRouter not working after update to 16.3.1

2021-07-01 Thread Lev Klimin
I tried L3 agent with neutron==16.3.1, problem was reproduced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about

[Bug 1927868] Re: vRouter not working after update to 16.3.1

2021-07-01 Thread Lev Klimin
Latest build ussuri kolla neutron-l3-agent container is based on neutron==16.3.3.dev45. L3 agent is stuck in "Staring router update" for part of routers. 2021-06-30 14:07:50.863 575 INFO neutron.agent.l3.agent [-] Starting router update for a9cb59da-3058-44ac-a2f7-21add6160e6d, action 3,

[Bug 1927868] Re: vRouter not working after update to 16.3.1

2021-06-29 Thread Lev Klimin
I've same problem on setup. We use kolla-ansible for upgrade tasks, and after upgrade from train to ussuri problem was reproduced. Workaround is downgrade neutron==16.3.2 to neutron==16.0.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1821797] Re: Failed attach cinder volume to instance

2019-03-26 Thread Lev Klimin
Output of nova-api.log 192.168.123.10 "GET /v2.1/servers/2788ffe5-fb54-4c97-8074-24b62cdfb65f HTTP/1.1" status: 200 len: 2042 time: 1.3150780 2019-03-26 21:54:22.370 3564924 ERROR nova.api.openstack.wsgi [req-85d2caa3-ef54-4282-9b61-a4e70e0319b1 088d6b25b302447b808b71f1df29de15

[Bug 1821797] [NEW] Failed attach cinder volume to instance

2019-03-26 Thread Lev Klimin
Public bug reported: There is a error at attaching cinder volume (rbd backend) to instance. Release: Queens # openstack server add volume 2788ffe5-fb54-4c97-8074-24b62cdfb65f bf137dcf-d537-4776-9a49-84a2b6bfccdd --debug ... skip ... GET call to volumev2 for

[Bug 1643558] Re: bnx2x driver crash

2016-12-19 Thread Lev Klimin
I confirm that with kernel 4.9.0-040900-generic #201612111631 this bug is fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643558 Title: bnx2x driver crash To manage notifications about this

[Bug 1643558] Re: bnx2x driver crash

2016-11-28 Thread Lev Klimin
Hi, there are some intersting details about this bug to help make fix. On fresh Ubuntu 16.04 there is no that bug at all. bnx2x driver crash is occur on vxlan tasks, for example # ip link add vxlan0 type vxlan id 42 group 239.1.1.1 dev enp21s0f1 dstport 4789 # ip li set vxlan0 up or using

[Bug 1643558] Re: bnx2x driver crash

2016-11-22 Thread Lev Klimin
** 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/1643558 Title: bnx2x driver crash To manage notifications about this bug go to:

[Bug 1643558] Re: bnx2x driver crash

2016-11-22 Thread Lev Klimin
I don't remember about exact prior kernel versions. Now there is 4.4.0-21-generic, 4.4.0-45-generic, 4.4.0-47-generic kernels, and problem is happing on all of them. 4.9.0-040900rc6-generic kernel dosn't fix a problem (see attach). ** Attachment added: "kernel_version"

[Bug 1643558] Re: bnx2x driver crash

2016-11-22 Thread Lev Klimin
I don't remember about exact prior kernel versions. Now there is 4.4.0-21-generic, 4.4.0-45-generic, 4.4.0-47-generic kernels, and problem is happing on all of them. 4.9.0-040900rc6-generic kernel dosn't fix a problem (see attach). ** Attachment added:

[Bug 1643558] [NEW] bnx2x driver crash

2016-11-21 Thread Lev Klimin
Public bug reported: On server with two NICs on Broadcom, bnx2x driver is crashes on boot. Full crash dump is in attach. # lspci | grep BCM57711 15:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711 10-Gigabit PCIe 15:00.1 Ethernet controller: Broadcom Corporation NetXtreme II