[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

: Rafael David Tinoco (inaddy) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs in Ubuntu. https://bugs.launchpad.net/bugs/1409904 Title: Needed patches for InfiniBand Support: Flow Steering and Offload Support

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

** Changed in: corosync (Ubuntu Trusty) Status: New = Invalid ** Changed in: corosync (Ubuntu Trusty) Assignee: Rafael David Tinoco (inaddy) = (unassigned) ** Changed in: fio (Ubuntu Trusty) Status: New = Invalid ** Changed in: fio (Ubuntu Trusty) Assignee: Rafael David

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

Packages libiverbs and libmlx4 do not break ABI compatibility thus rdepends do not need to be recompiled. The abi_compat field of struct ibv_context is used to determine support of verbs extensions. As a result, support for ABI version 2 is removed (corresponds to kernel releases 2.6.11-2.6.14

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

** Patch added: trusty_libmlx4_1.0.5-1ubuntu2.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/tgt/+bug/1409904/+attachment/4439913/+files/trusty_libmlx4_1.0.5-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

** Patch added: trusty_libibverbs_1.1.7-1ubuntu2.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/tgt/+bug/1409904/+attachment/4439912/+files/trusty_libibverbs_1.1.7-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

libmlx4 does need specific version from libibverbs because it is also being changed to support: - Flow steering control - Offload support thus this version, 1.0.5-1ubuntu2 has to be compiled exactly with libibverbs-dev (= 1.1.7-1ubuntu2) and depends exactly on libibverbs1 (= 1.1.7-1ubuntu2).

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

** Changed in: perftest (Ubuntu Trusty) Status: New = Invalid ** Changed in: perftest (Ubuntu Trusty) Assignee: Rafael David Tinoco (inaddy) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

= In Progress ** Changed in: openmpi (Ubuntu Trusty) Status: In Progress = Invalid ** Changed in: openmpi (Ubuntu Trusty) Assignee: Rafael David Tinoco (inaddy) = (unassigned) ** Changed in: libmlx4 (Ubuntu Trusty) Status: New = In Progress ** Changed in: libibverbs (Ubuntu

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs in Ubuntu. https://bugs.launchpad.net/bugs/1409904 Title: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes To manage notifications about

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

After talking to Chris Arges (arges) and Adam Conrad (infinity): It was clear that if libibverbs fixes (HW enablement) break ABI compatibility then they are not suitable for a Trusty SRU. I'll break those fixes and return all of them to their respective cases since there won't be any ABI being

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

TGT fix: iSER support added ** Patch added: trusty_tgt_1.0.43-0ubuntu5.debdiff https://bugs.launchpad.net/ubuntu/trusty/+source/tgt/+bug/1409904/+attachment/4439195/+files/trusty_tgt_1.0.43-0ubuntu5.debdiff -- You received this bug notification because you are a member of Ubuntu Server

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs in Ubuntu. https://bugs.launchpad.net/bugs/1409904 Title: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes To manage notifications about

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

Hello Sponsors, I'd like to know if it is possible for us to upload fixes for Trusty, Vivid, Utopic since Wily was fixed sometime ago. Thank you. Rafael Tinoco ** Tags removed: cts ** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

** Changed in: fio (Ubuntu) Assignee: (unassigned) = Rafael David Tinoco (inaddy) ** Changed in: fio (Ubuntu Trusty) Assignee: (unassigned) = Rafael David Tinoco (inaddy) ** Changed in: glusterfs (Ubuntu) Assignee: (unassigned) = Rafael David Tinoco (inaddy) ** Changed

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

** Changed in: libmlx4 (Ubuntu Vivid) Assignee: (unassigned) = Rafael David Tinoco (inaddy) ** Changed in: libmlx5 (Ubuntu) Assignee: (unassigned) = Rafael David Tinoco (inaddy) ** Changed in: libmlx5 (Ubuntu Trusty) Assignee: (unassigned) = Rafael David Tinoco (inaddy

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

** Changed in: libmlx5 (Ubuntu) Status: New = Invalid ** Changed in: libmlx5 (Ubuntu) Assignee: Rafael David Tinoco (inaddy) = (unassigned) ** Changed in: libmthca (Ubuntu) Status: New = Invalid ** Changed in: libmthca (Ubuntu) Assignee: Rafael David Tinoco (inaddy

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

** Changed in: libibcm (Ubuntu) Status: New = Invalid ** Changed in: libibcm (Ubuntu) Assignee: Rafael David Tinoco (inaddy) = (unassigned) ** Changed in: libipathverbs (Ubuntu) Status: New = Invalid ** Changed in: libipathverbs (Ubuntu) Assignee: Rafael David Tinoco

[Bug 1490542] [NEW] iSER: Discovery doesn't work on the user defined ports

or Ubuntu. ... It looks like TGT might be suffering problems when being executed on a different port (3261/3262) with iSER (iSCSI over InfiniBand). Investigating... ** Affects: tgt (Ubuntu) Importance: Undecided Assignee: Rafael David Tinoco (inaddy) Status: In Progress

[Bug 1490542] iSER: Discovery doesn't work on user defined ports

Hello Pankaj, Quick e-mail to inform you I’m working on this case: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1490542 and will keep you posted on discoveries. I just set an SR-IOV IB environment up so I could test this. Could

[Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

** Changed in: libnl3 (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (inaddy) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419 Title: nl_cache_ref

[Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

Kamal, As we talked about, I'm making the following PPA available: https://launchpad.net/~inaddy/+archive/ubuntu/lp1312419 It contains Trusty version + commit: >From 3700cc1ad3a3b507848deb401b9d0f41ff7010bb Mon Sep 17 00:00:00 2001 From: Thomas Graf Date: Fri, 1 Feb 2013

[Bug 1409904] LP: #1409904 awaiting verification

Kamal, Pankaj, I’m glad to inform that finally bug LP: #1409904 is being finalised (for Trusty) and its fix is already committed. Next step is for us to “verify” the fix (from -proposed repository) and mark the public bug as “verified”. I have already verified TGT iSER support:

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

Verified TGT iSER support: Linux iserserver.main 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:42:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Linux iserclient.main 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:42:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ### SERVER root@iserserver:~# dd

[Bug 1409904] Re: #1409904 awaiting verification

Hello Pankaj, I’m sorry for not being more clear… There is no way that a SRU is accepted if -proposed package is not verified. TGT iSER support was already verified by me. I still need Kamal to verify libibverbs and libmlx4. Thank you! -- You received this bug notification because you are a

[Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

It looks like that Trusty version also suffers from: root@dixie:~# virsh start maas error: Failed to start domain maas error: internal error: missing IFLA_VF_INFO in netlink response Whenever we try to start a VFIO (or KVM passthrough) SR-IOV based machine. I don't think this happens under

[Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

** Changed in: libnl3 (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1312419 Title: nl_cache_refill; rtnl_neigh_get fail to find

[Bug 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes

In a meeting with Mellanox in Israel I was told that libibverbs and libmlx4 have been verified and proved to work. Changing this to verification done. Thank you. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member

[Bug 1520192] Re: multipath-tools from Precise should have been fixed together with Trusty fixes

This is the debdiff with changes from trusty to precise. Those changes are basically fixing behaviour PER comments showing that. No major (or even minor) version was changed so this is - IMHO - suitable for SRU. This also has been tested - PER PPA with hotfix provided - and proved to work. Thank

[Bug 768471] Re: corosync segfaults on startup joining another node

** Changed in: corosync (Ubuntu) Status: Confirmed => Incomplete ** Changed in: corosync (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu.

[Bug 1530837] [NEW] Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

results in leak of /dev/shm space. Expected results: No leak Additional info: """ ** Affects: corosync (Ubuntu) Importance: Undecided Assignee: Rafael David Tinoco (inaddy) Status: Confirmed ** Changed in: corosync (Ubuntu) Status: New => Confirmed **

[Bug 1520192] [NEW] Precise multipath-tools from precise should have been fixed together with Trusty fixes

) - Correctly write FC timeout attributes to sysfs. ** Affects: multipath-tools (Ubuntu) Importance: Undecided Assignee: Rafael David Tinoco (inaddy) Status: In Progress ** Changed in: multipath-tools (Ubuntu) Status: New => In Progress ** Changed in: multipath-tools (Ubu

[Bug 1520192] Re: Precise multipath-tools from precise should have been fixed together with Trusty fixes

** Description changed: - Somehow precise multipath-tools from precise was NOT fixed with fixes - added into trusty. Since SRU is based on FIXING things (and not - implementing new features) and both have the same major version, and all - changes in between them ARE FIXES, I really would like

[Bug 1490542] Re: iSER: Discovery doesn't work on the user defined ports

** Changed in: tgt (Ubuntu) Assignee: Rafael David Tinoco (inaddy) => (unassigned) ** Changed in: tgt (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu.

Re: [Bug 1312419] Re: nl_cache_refill; rtnl_neigh_get fail to find neighbors in cache

ubuntu/ trusty/main amd64 > Packages > 100 /var/lib/dpkg/status > libnl-route-3-200: > Installed: 3.2.21-1 > Candidate: 3.2.21-1 > Version table: > *** 3.2.21-1 0 > 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 > Packages >

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

https://bugzilla.redhat.com/show_bug.cgi?id=1117911 ** Bug watch added: Red Hat Bugzilla #1117911 https://bugzilla.redhat.com/show_bug.cgi?id=1117911 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu.

[Bug 1520192] Re: multipath-tools from Precise should have been fixed together with Trusty fixes

** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1520192 Title: multipath-tools from Precise should have been fixed together with Trusty fixes To manage

[Bug 1532789] [NEW] Trusty multipath-tools suffering seg faults

Public bug reported: It was brought to my attention that Trusty's multipath-tools is suffering some seg faults. The dumps were sent to me and I'll update this bug's description soon. ** Affects: multipath-tools (Ubuntu) Importance: Undecided Assignee: Rafael David Tinoco (inaddy

[Bug 1520192] Re: multipath-tools from Precise should have been fixed together with Trusty fixes

Please hold this fix since I just discovered the following BUG: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1532789 I'll have to add the fix for the bug above together with this one. I will attach files soon. -- You received this bug notification because you are a member of

[Bug 1532789] Re: Trusty multipath-tools suffering seg faults

Precise being fixed together with: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192 SRU proposal. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu.

[Bug 1532789] Re: Trusty multipath-tools suffering seg faults

** Description changed: - It was brought to my attention that Trusty's multipath-tools is - suffering some seg faults. + It was brought to my knowledge that multipath-tools is facing segfaults: - The dumps were sent to me and I'll update this bug's description soon. + + Core was generated

[Bug 1520192] Re: multipath-tools from Precise should have been fixed together with Trusty fixes

Okay this is ready to be sponsored now. I have added fix for LP: #1532789 together. Mathieu, Could u do these "2" fixes at once ? Thank you Rafael -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu.

[Bug 1520192] Re: multipath-tools from Precise should have been fixed together with Trusty fixes

Adding fix for LP: #1532789 together with this SRU (so this is all done just once). ** Patch removed: "precise_multipath-tools_0.4.9-3ubuntu5.4.debdiff"

[Bug 1532789] Re: Trusty multipath-tools suffering seg faults

Attaching the debdiff for the fix. ** Patch added: "trusty_multipath-tools_0.4.9-3ubuntu7.8.debdiff" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1532789/+attachment/4548193/+files/trusty_multipath-tools_0.4.9-3ubuntu7.8.debdiff ** Description changed: + [Impact] + + *

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

** Changed in: corosync (Ubuntu Trusty) Status: New => Confirmed ** Changed in: corosync (Ubuntu) Status: Confirmed => Fix Released ** Changed in: corosync (Ubuntu Trusty) Assignee: (unassigned) => Rafael David Tinoco (inaddy) ** Changed in: corosync (Ubuntu)

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

Those fixes are already included in corosync v2.3.4: $ git tag --contains cc80c8567d6eec1d136f9e85d2f8dfb957337eef v2.3.4 v2.3.5 $ git tag --contains 384760cb670836dc37e243f594612c6e68f44351 v2.3.4 v2.3.5 $ git tag --contains dfaca4b10a005681230a81e229384b6cd239b4f6 v2.3.4 v2.3.5

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

Waiting for the BUG to be sponsored. Thank you. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/1530837 Title: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

BTW, I provided a public PPA: https://launchpad.net/~inaddy/+archive/ubuntu/lp1530837 If anyone suffering from this is interested in having a hotfix while SRU isn't ready. Thank you -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

Fix for Trusty. ** Patch added: "trusty_corosync_2.3.3-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+attachment/4549322/+files/trusty_corosync_2.3.3-1ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team,

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

** Description changed: + [Impact] + + * corosync has a memory leak problem with multiple calls to corosync -v + * corosync has a memory leak problem by not properly handling signals + + [Test Case] + + * run "corosync -v" multiple times + * some cloud tools do that + + [Regression

[Bug 1533721] Re: Ethtool didn't support link speed 25Gb 56Gb 100Gb 200Gb

After talking to Talat: - What Ubuntu version are you referring to ? [TB]Ubuntu 14.4.4 trusty - Have you tested in newer versions ? [TB] not tested yet, will test it on Xenial and update. - What are the steps to reproduce the problem ? [TB] ethtool See that under "Advertised link

[Bug 1532789] Re: Trusty multipath-tools suffering seg faults

** Changed in: multipath-tools (Ubuntu) Assignee: Rafael David Tinoco (inaddy) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1532789 Title: Tru

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

For Trusty, I have suggested the following SRU: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1532789 And for Precise I have suggested the following SRU (bringing all patches also to precise): https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192 With this

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

** Attachment added: "multipath.conf" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898/+attachment/4552894/+files/multipath.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu.

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

** Attachment added: "iscsi.txt" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898/+attachment/4552895/+files/iscsi.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu.

[Bug 1535898] [NEW] Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

Public bug reported: We have a problem on multipath-tools. Usually after a path removal and a re-scan, the multipathd process dies. I created 2 hosts: iscsi-server iscsi-client With 4 NICs in between them and with a simple multibus multipath. With that I was able to check that there is a

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

I have generated multipath-tools & kpartx packages from upstream code around those commits: 0019-multipath-fix-scsi-timeout-code.patch 0020-multipath-make-tgt_node_name-work-for-iscsi-devices.patch 0021-multipath-cleanup-dev_loss_tmo-issues.patch 0022-Fix-for-setting-0-to-fast_io_fail.patch

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

** Attachment added: "iscsiclient.sh" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898/+attachment/4552892/+files/iscsiclient.sh -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu.

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

This crash is from Trusty using my reproducer. It includes the dump. ** Attachment added: "_sbin_multipathd.0.crash" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898/+attachment/4552896/+files/_sbin_multipathd.0.crash -- You received this bug notification because you

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

** Attachment added: "iscsiserver.sh" https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898/+attachment/4552893/+files/iscsiserver.sh -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu.

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

** Changed in: multipath-tools (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1535898 Title: Trusty & Vivid multipath-tools

[Bug 1520192] Re: multipath-tools from Precise should have been fixed together with Trusty fixes

Mathieu, Please take a look at the following bug: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898 It looks like Trusty debian/patches are suffering a regression. This might have to be fixed together. -- You received this bug notification because you are a member of

[Bug 1532789] Re: Trusty multipath-tools suffering seg faults

Mathieu, Please take a look at the following bug: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898 It looks like Trusty debian/patches are suffering a regression. This might have to be fixed together. -- You received this bug notification because you are a member of

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

Hello Mark, Tks for reviewing my mistake. I believe it is good now. inaddy@lp1530837trusty:~/Codes/bugs/1530837/trusty/corosync-2.3.3$ patch -p1 < ../trusty_corosync_2.3.3-1ubuntu2.debdiff patching file debian/changelog patching file

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

** Patch removed: "trusty_corosync_2.3.3-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+attachment/4549322/+files/trusty_corosync_2.3.3-1ubuntu2.debdiff ** Changed in: corosync (Ubuntu Trusty) Status: Incomplete => In Progress ** Patch added:

[Bug 1862928] [NEW] python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)

python-crypto (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: In Progress ** Changed in: python-crypto (Ubuntu) Status: New => In Progress ** Changed in: python-crypto (Ubuntu) Importance: Undecided => Medium ** Changed in: p

[Bug 1861316] Re: ubuntu 20.04: libnss-winbind:386 should remain

Related bug: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928 As python-crypto needed a rebuild to allow libnss-winbind and winbind to be installable (due to its dependencies). -- You received this bug notification because you are a member of Ubuntu Server, which is

[Bug 1861316] Re: ubuntu 20.04: libnss-winbind:386 should remain

Last MR push: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/samba/+git/samba/+merge/378664/comments/994088 Looks good but depends on fix for: https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/186292 -- You received this bug notification because you are a member of Ubuntu

[Bug 1852122] Re: ocfs2-tools is causing kernel panics in Ubuntu Focal (Ubuntu-5.4.0-9.12)

VERIFICATION: (k)rafaeldtinoco@ocfs2:~$ apt-cache policy linux-image-5.4.0-14-generic linux-image-5.4.0-14-generic: Installed: 5.4.0-14.17 Candidate: 5.4.0-14.17 Version table: *** 5.4.0-14.17 500 500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages

[Bug 1862928] Re: python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)

Yep, I had those as well, thought it was my dev environmnet. But, if you say yours install fine there is no need for a rebuild.. weird.. I'll re- check here, thank you! -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report.

[Bug 1862928] Re: python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)

Ah okay, perhaps your environment is amd64 ? I'm testing this in an i386 environmnet (LXD container) only. Still getting: python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to be installed Depends: python3:amd64 (>= 3.7~) but it is not going to be

[Bug 1862928] Re: python-crypto needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)

I think this relates to having i386 in amd64 installed OSes only currently. Since I'm using a i386 only container, it can't figure out the correct python dependency (asking for amd64). If I build python3-crypto in an i386 container dependencies are correctly figured out. ** Summary changed: -

[Bug 1862770] Re: MySQL autopkgtest regressed in Focal release pocket

*** This bug is a duplicate of bug 1862364 *** https://bugs.launchpad.net/bugs/1862364 Related bugs: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862364 https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1859100 -- You received this bug notification because you are a

[Bug 1862770] Re: MySQL autopkgtest regressed in Focal release pocket

*** This bug is a duplicate of bug 1862364 *** https://bugs.launchpad.net/bugs/1862364 Ah, nm, this is a duplicate =o). -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to mysql-8.0 in Ubuntu. https://bugs.launchpad.net/bugs/1862770

[Bug 1859100] Re: mysql-server FTBFS (focal) because of build tests

I have just uploaded mysql-8.0_8.0.19-0ubuntu3 containing fixes for the 2020 year in mysql tests. I'll flag this as Fix Committed and Fix Released manually as only LP: #1862364 was referred in that changelog. -- You received this bug notification because you are a member of Ubuntu Server, which

[Bug 1859100] Re: mysql-server FTBFS (focal) because of build tests

Related bugs: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862364 https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862770 ** Changed in: mysql-8.0 (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of

[Bug 1862770] Re: MySQL autopkgtest regressed in Focal release pocket

*** This bug is a duplicate of bug 1862364 *** https://bugs.launchpad.net/bugs/1862364 I have just uploaded mysql-8.0_8.0.19-0ubuntu3 containing fixes for the 2020 year in mysql tests. I'll flag this as Fix Committed and Fix Released manually as only LP: #1862364 was referred in that

[Bug 1862364] Re: mysql-8.0 FTBFS (focal) because of hardcoded date in test

I have just uploaded mysql-8.0_8.0.19-0ubuntu3 containing fixes for the 2020 year in mysql tests. Related bugs: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1862770 https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1859100 ** Changed in: mysql-8.0 (Ubuntu) Status:

[Bug 1862928] Re: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)

Steve, Looks like python3-crypto package is not in the i386 archive. Judging by: https://launchpad.net/ubuntu/+source/python-crypto https://launchpad.net/ubuntu/+source/python-crypto/+publishinghistory https://launchpad.net/ubuntu/+source/python-crypto/2.6.1-11ubuntu2

[Bug 1862947] Re: crmsh should be taken back to -main

MERGE: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/378958 PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1862947 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report.

[Bug 1862928] Re: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)

09:43 you see that python3-crypto has per-arch deb files 09:43 I added a comment in the case and subscribed steve 09:43 while your conter-xample of ansi just has one called ..._all.deb 09:43 — rafaeldtinoco checks 09:43 AFAICS python3-crypto contains no arch dependent files 09:44 so it could

[Bug 1862947] [NEW] crmsh should be taken back to -main

. This will likely be enough after some IRC discussions with other Ubuntu developers. ** Affects: crmsh (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Fix Released ** Affects: pacemaker (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco

[Bug 1862947] Re: crmsh should be taken back to -main

$ rmadison crmsh crmsh | 1.2.5+hg1034-1ubuntu3 | trusty | source, all crmsh | 1.2.5+hg1034-1ubuntu4 | trusty-updates | source, all crmsh | 2.2.0-1 | xenial | source, ... crmsh | 3.0.1-3ubuntu1| bionic/universe | source, all crmsh | 3.0.1-3ubuntu1

[Bug 1862928] Re: python-crypto (i386) needs rebuild in Focal (python 3.7 -> python 3.8 dependency refresh)

Thanks Steve!! Package is back to archive, moving on with what needed this. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1862928 Title: python-crypto (i386) needs rebuild in Focal

[Bug 1862947] Re: crmsh should be taken back to -main

Acording to: https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1205019/comments/10 It was proposed to main again by doko. I'll wait full pacemaker migration - and test crmsh installation - to close this bug. -- You received this bug notification because you are a member of Ubuntu Server,

[Bug 1862947] Re: crmsh should be taken back to -main

Correct! I missed that part. Thank you! -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1862947 Title: crmsh should be taken back to -main To manage notifications about this bug go to:

[Bug 1861316] Re: ubuntu 20.04: libnss-winbind:386 should remain

** Changed in: samba (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1861316 Title: ubuntu 20.04: libnss-winbind:386 should remain To manage

[Bug 1861316] Re: ubuntu 20.04: libnss-winbind:386 should remain

I just pushed the merge and uploaded source code. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1861316 Title: ubuntu 20.04: libnss-winbind:386 should remain To manage notifications

[Bug 1864404] Re: fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) after nodes are rebooted

ents (Ubuntu Focal) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1864404 Title: fence_scsi cannot open /var/run/cluster/fence_scsi.

[Bug 1864404] Re: fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) after nodes are rebooted

I was able to confirm that, in Ubuntu Focal, during fence_scsi initialization: (k)rafaeldtinoco@clufocal01:~$ crm configure show node 1: clufocal01 node 2: clufocal02 node 3: clufocal03 primitive fence_clufocal stonith:fence_scsi \ params pcmk_host_list="clufocal01 clufocal02 clufocal03"

[Bug 1864404] Re: fence_scsi cannot open /var/run/cluster/fence_scsi.key (does not exist) after nodes are rebooted

Yes, I have just confirmed that in Bionic, the fence_scsi fails to create the /var/run/cluster by itself: rafaeldtinoco@clubionic01:~$ crm configure crm(live)configure# primitive fence_clufocal stonith:fence_scsi \ > params pcmk_host_list="10.250.98.10 10.250.98.11 10.250.98.12"

[Bug 1864142] Re: Package: sbd (debian: 1.4.1-3, ubuntu: 1.4.0-18-g5e3283c-1ubuntu1) needs merge

This bug was fixed in the package sbd - 1.4.1-3 Sponsored for Rafael David Tinoco (rafaeldtinoco) --- sbd (1.4.1-3) unstable; urgency=medium * debian/control: cleanup Build-Depends -- Valentin Vidic Sat, 11 Jan 2020 11:48:05 +0100 sbd (1.4.1-2) unstable; urgency=medium

[Bug 1854362] Re: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid, targetcli-fb

## ## SUMMARY (please correct me if I'm wrong) ## python-rtslib-fb- lib: object API for managing Linux LIO kernel target python-configshell-fb - lib: framework for building CLI-based apps MIR #1) ceph-iscsi - LIO gateways for Ceph (logic and CLI tools)

[Bug 1864861] Re: Sync ruby-defaults 1:2.7~0 (main) from Debian experimental (main)

This bug was fixed in the package ruby-defaults - 1:2.7~0 Sponsored for Lucas Kanashiro (lucaskanashiro) --- ruby-defaults (1:2.7~0) experimental; urgency=medium [ Antonio Terceiro ] * Make Ruby 2.7 the default and drop Ruby 2.5 * debian/tests/control: add test-name pkg-config

[Bug 1613423] Re: Mitaka + Trusty (kernel 3.13) not using apparmor capability by default, when it does, live migration doesn't work (/tmp/memfd-XXX can't be created)

QEMU BUG: https://bugs.launchpad.net/qemu/+bug/1626972 ** Changed in: libvirt (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1613423

[Bug 1613423] Re: Mitaka + Trusty (kernel 3.13) not using apparmor capability by default, when it does, live migration doesn't work (/tmp/memfd-XXX can't be created)

Preferred way for this fix was: commit 0d34fbabc13891da41582b0823867dc5733fffef Author: Rafael David Tinoco Date: Mon Oct 24 15:35:03 2016 vhost: migration blocker only if shared log is used Commit 31190ed7 added a migration blocker in vhost_dev_init() to check if memfd would

[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1

** No longer affects: pacemaker (Ubuntu) ** No longer affects: pacemaker (Ubuntu Bionic) ** Description changed: + OBS: I have split this bug into 2 bugs: + - fence-agents (this) and pacemaker (LP: #1866119) + SRU: fence-agents [Impact]  * fence_scsi is not currently

[Bug 1866119] [NEW] [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1

Public bug reported: OBS: This bug was originally into LP: #1865523 but it was split. SRU: pacemaker [Impact] * fence_scsi is not currently working in a share disk environment * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't be able to start the fencing agents

[Bug 1865523] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1

** Description changed: + SRU: fence-agents + + [Impact] + + * fence_scsi is not currently working in a share disk environment + + * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't + be able to start the fencing agents OR, in worst case scenarios, the + fence_scsi

[Bug 1866119] Re: [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1

** Description changed: + OBS: This bug was originally into LP: #1865523 but it was split. + + SRU: pacemaker + + [Impact] + + * fence_scsi is not currently working in a share disk environment + + * all clusters relying in fence_scsi and/or fence_scsi + watchdog won't + be able to

[Bug 1865523] [NEW] [bionic] fence_scsi not working properly with 1.1.18-2ubuntu1.1

cluster.bionic. 4.0 Peripheral device type: disk PR generation=0x0, there is NO reservation held ** Affects: pacemaker (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Changed in: pacemaker (Ubuntu) Status: New =&

<    1   2   3   4   5   6   7   >