[Bug 1906922] Re: Unpredictable behaviour on conflicting flow actions

2020-12-09 Thread Márton Kiss
Frode, this solves the packet loss issue I saw previously. I marked this
field crit, as we don't have a workaround, and would be grate to make it
through the SRU process intro stable branch for UCA/Ussuri/Bionic.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906922

Title:
  Unpredictable behaviour on conflicting flow actions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1906922/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827690] Re: [19.04][stein] barbican-worker is down: Requested revision 1a0c2cdafb38 overlaps with other requested revisions 39cf2e645cba

2020-10-08 Thread Márton Kiss
After additional debug and research I can confirm the issue is the
result of a race-condition situation when multiple barbican-worker units
trying to populate the database with schema data simultaneously and
upgrade the alembic version.

As a result the barbican-worker service will stop because it is trying
to recreate tables already created by other worker units.

I applied the following manual steps as workaround:

1, stop all barbican-workers, stop jujud agent
2, drop db tables
3, clean up alembic db change states if present: rm -rf 
/usr/lib/python3/dist-packages/barbican/model/migration/alembic_migrations/versions/*_db_change.py
 files
4, start barbican-worker on a single unit (populates the db tables to head 
revisions)
5, restart all barbican-workers, start jujud agent

as a result each units must be on the same db revision:
$ juju run --application barbican 'barbican-db-manage current -V | grep 
Revision'
- Stdout: |2
Revision ID: 39cf2e645cba
  UnitId: barbican/0
- Stdout: |2
Revision ID: 39cf2e645cba
  UnitId: barbican/1
- Stdout: |2
Revision ID: 39cf2e645cba
  UnitId: barbican/2

The root cause of the problem is the default implementation of barbican-
worker services, because they are populating the data after service
start, this can lead to the race condition situation.

A proper permanent charm fix should be:
1, As [1] mentions in the Install and configure components / 3. Populate the 
Key Manager service database section, the charm should set the db_auto_create 
to false in the /etc/barbican/barbican.conf file.
2, the leader charm populates the database
3, start the barbican-worker services after the leader finished with db schema 
upgrade.

[1] https://docs.openstack.org/barbican/stein/install/install-
ubuntu.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827690

Title:
  [19.04][stein] barbican-worker is down: Requested revision
  1a0c2cdafb38 overlaps with other requested revisions 39cf2e645cba

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-barbican/+bug/1827690/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795587] Re: Upgrade i40e driver to support 6.01 Firmware - Intel XL710

2018-10-04 Thread Márton Kiss
We are using the 4.15 HWE kernel on Xenial, and the i40e driver is
working, the only problem that the kernel driver version is not matching
the minimum requirement for 6.01 Firmware, what is required for latest
dpdk / sriov features and upgrades.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795587

Title:
  Upgrade i40e driver to support 6.01 Firmware - Intel XL710

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795587/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795587] Re: Upgrade i40e driver to support 6.01 Firmware - Intel XL710

2018-10-02 Thread Márton Kiss
It is rather a feature request than a bug, but affects the
supportability of NIC firmware, and the performance of SRIOV and DPDK.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795587

Title:
  Upgrade i40e driver to support 6.01 Firmware - Intel XL710

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795587/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795587] [NEW] Upgrade i40e driver to support 6.01 Firmware - Intel XL710

2018-10-02 Thread Márton Kiss
Public bug reported:

Intel released the 6.01 Firmware for the Intel XL710 network cards. As
stated in the feature support matrix [1] in the table 9 on page 18, the
minimum kernel driver version for the 6.01 Firmware i40e must be 2.1.26,
the recent driver version is 2.4.10 [2]

The i40 driver version included in the 4.15.0-36 (Bionic, LTS) is
2.1.14-k.

$ uname -a
Linux ubuntu-bionic 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

$ modinfo i40e
filename:   
/lib/modules/4.15.0-36-generic/kernel/drivers/net/ethernet/intel/i40e/i40e.ko
version:2.1.14-k
license:GPL
description:Intel(R) Ethernet Connection XL710 Network Driver

Release notes: [3] [4] [5] [6] [7]

The firmware 6.01 introduce better performance for DPDK and SR-IOV
applications for those cards, and  NFV application workloads would
perform better.


[1] Intel® Ethernet Controller X710/ XXV710/XL710 Feature Support Matrix
https://www.intel.com/content/dam/www/public/us/en/documents/release-notes/xl710-ethernet-controller-feature-matrix.pdf

[2] Intel® Network Adapter Driver for PCIe* 40 Gigabit Ethernet Network 
Connections Under Linux* 
https://downloadcenter.intel.com/download/24411/Intel-Network-Adapter-Driver-for-PCIe-40-Gigabit-Ethernet-Network-Connections-Under-Linux-?product=75021

[3] Intel(R) Network Connections Software Version 23.2 Release Notes
https://downloadmirror.intel.com/24411/eng/readme.txt

[4] Intel(R) Network Connections Software Version 23.1 Release Notes
https://downloadmirror.intel.com/27869/eng/readme.txt

[5] Intel(R) Network Connections Software Version 22.10 Release Notes
https://downloadmirror.intel.com/27547/eng/readme.txt

[6] Intel(R) Network Connections Software Version 22.9 Release Notes
https://downloadmirror.intel.com/27547/eng/readme.txt

[7] Intel(R) Network Connections Software Version 22.6 Release Notes
https://downloadmirror.intel.com/27189/eng/readme.txt

** Affects: linux (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/1795587

Title:
  Upgrade i40e driver to support 6.01 Firmware - Intel XL710

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795587/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766577] [NEW] 4.15.0-15 mdadm: CREATE group disk not found

2018-04-24 Thread Márton Kiss
Public bug reported:

4.15.0-15-generic (buildd@lcy01-amd64-018) producing the following
errors during boot process:

Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... 
mdadm: CREATE group disk not found
mdadm: No devices listed in conf file were found.
done.
Begin: Running /scripts/local-block ... mdadm: CREATE group disk not found
mdadm: No devices listed in conf file were found.
done.
Begin: Running /scripts/local-block ... mdadm: CREATE group disk not found
mdadm: No devices listed in conf file were found.
done.
...
BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) 

It is a Lenovo SR550, and the 4.15.0-13 was booting properly. (Boot log
attached)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "kernel-4.15.0-15.log"
   
https://bugs.launchpad.net/bugs/1766577/+attachment/5126513/+files/kernel-4.15.0-15.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766577

Title:
  4.15.0-15 mdadm: CREATE group disk not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766577/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 924013] Re: VPN DNS only works for IP, not names

2012-03-23 Thread Márton Kiss
I experienced the same issue. After sucessfull OpenVPN connection
/var/run/nm-dns-dnsmasq.conf contains the following:

server=/10.in-addr.arpa/10.1.106.7
server=192.168.0.1
server=192.168.3.2

This 10.in-addr.arpa prefix appears only when "Use this connection only for 
resources on its network" checkbox was turned on at IPV4 routes page of VPN 
configuration window.  Syslog contains the following:
...
Mar 23 09:41:35 shakira dnsmasq[4138]: using nameserver 10.1.106.7#53 for 
domain 10.in-addr.arpa
...

Finally, I found, that the OpenVPN server was not pushing down the
domain suffix. After inserting the proper "dhcp-option DOMAIN" entry
into openvpn server configuration, it started to work.

openvpn server.conf:
...
push "dhcp-option DNS 10.1.106.7"
push "dhcp-option DOMAIN dev.xxx.domain.com"
...

/var/run/nm-dns-dnsmasq.conf:
...
server=/devzone.cloud.xemeti.com/10.1.106.7
...

So I think it is not a client side bug, just a server side configuration
requirement. Affects only users with "Use this connection.." flag turned
on, without dhcp-option DOMAIN push entry.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924013

Title:
  VPN DNS only works for IP, not names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/924013/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 880768] Re: The whole window manager sometimes freezes when switching workspaces or when opening the workspace switcher

2012-01-14 Thread Márton Kiss
Additional info:
I can experience this bug only with an attached external monitor. When I'm 
using the notebook as a standalone primary display the freezing never appears.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880768

Title:
  The whole window manager sometimes freezes when switching workspaces
  or when opening the workspace switcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/880768/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 880768] Re: The whole window manger sometimes freezes when switching workspaces or when opening the workspace switcher

2012-01-06 Thread Márton Kiss
Bilal, I have same problems with a fully updated Oneiric running on a Dell 
notebook:
lspci -vv
...
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller (rev 03)
Subsystem: Dell Device 01d4
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/880768

Title:
  The whole window manger sometimes freezes when switching workspaces or
  when opening the workspace switcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/880768/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs