[Sts-sponsors] [Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes

2021-01-14 Thread Victor Tapia
** Patch added: "lshw-bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1826737/+attachment/5452916/+files/lshw-bionic.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes

2021-01-14 Thread Victor Tapia
** Patch added: "lshw-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1826737/+attachment/5452915/+files/lshw-focal.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes

2021-01-14 Thread Victor Tapia
** Patch removed: "lshw-groovy.debdiff" https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1826737/+attachment/5452323/+files/lshw-groovy.debdiff ** Patch removed: "lshw-focal.debdiff"

[Sts-sponsors] [Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes

2021-01-12 Thread Victor Tapia
** Patch added: "lshw-focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1826737/+attachment/5452324/+files/lshw-focal.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes

2021-01-12 Thread Victor Tapia
** Patch added: "lshw-groovy.debdiff" https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1826737/+attachment/5452323/+files/lshw-groovy.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1580385] Re: /usr/bin/nmap:11:hascaptures:hascaptures:hascaptures:hascaptures:hascaptures

2019-11-07 Thread Victor Tapia
** Patch added: "eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1580385/+attachment/5303496/+files/eoan.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1580385] Re: /usr/bin/nmap:11:hascaptures:hascaptures:hascaptures:hascaptures:hascaptures

2019-11-07 Thread Victor Tapia
** Patch added: "bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1580385/+attachment/5303499/+files/bionic.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1580385] Re: /usr/bin/nmap:11:hascaptures:hascaptures:hascaptures:hascaptures:hascaptures

2019-11-07 Thread Victor Tapia
** Patch added: "disco.debdiff" https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1580385/+attachment/5303497/+files/disco.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1580385] Re: /usr/bin/nmap:11:hascaptures:hascaptures:hascaptures:hascaptures:hascaptures

2019-11-07 Thread Victor Tapia
** Patch added: "xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/lua-lpeg/+bug/1580385/+attachment/5303500/+files/xenial.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1572908] Re: sssd-ad pam_sss(cron:account): Access denied for user

2019-04-24 Thread Victor Tapia
The fix is included in sssd 1.16.4, currently in debian experimental -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1572908 Title: sssd-ad pam_sss(cron:account): Access denied for user

[Sts-sponsors] [Bug 1572908] Re: sssd-ad pam_sss(cron:account): Access denied for user

2019-04-24 Thread Victor Tapia
** Also affects: sssd (Ubuntu Eoan) Importance: Medium Assignee: Victor Tapia (vtapia) Status: In Progress -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1572908 Title: sssd

[Sts-sponsors] [Bug 1791108] Re: open-iscsi uses domainsearch instead of search for /etc/resolv.conf

2018-10-03 Thread Victor Tapia
#VERIFICATION-BIONIC - Before the update ubuntu@iscsi-bionic:~$ dpkg -l | grep open-iscsi ii open-iscsi2.0.874-5ubuntu2.2 amd64iSCSI initiator tools ubuntu@iscsi-bionic:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc

[Sts-sponsors] [Bug 1791108] Re: open-iscsi uses domainsearch instead of search for /etc/resolv.conf

2018-10-03 Thread Victor Tapia
#VERIFICATION-XENIAL - Before the update ubuntu@iscsi_base:~$ dpkg -l | grep open-iscsi ii open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3.5 amd64iSCSI initiator tools ubuntu@iscsi_base:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc

[Sts-sponsors] [Bug 1791108] Re: open-iscsi uses domainsearch instead of search for /etc/resolv.conf

2018-09-20 Thread Victor Tapia
** Patch removed: "open-iscsi-bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1791108/+attachment/5190084/+files/open-iscsi-bionic.debdiff ** Patch removed: "open-iscsi-cosmic.debdiff"

[Sts-sponsors] [Bug 1791108] Re: open-iscsi uses domainsearch instead of search for /etc/resolv.conf

2018-09-20 Thread Victor Tapia
** Patch added: "open-iscsi-bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1791108/+attachment/5190913/+files/open-iscsi-bionic.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

2018-01-11 Thread Victor Tapia
I was wrong regarding iii) "when corosync is stopped, do not stop pacemaker": Pacemaker can use other applications[1] (e.g. heartbeat) instead of corosync, so this is a property we want to keep. -- You received this bug notification because you are a member of STS Sponsors, which is subscribed

[Sts-sponsors] [Bug 1740892] Re: corosync upgrade on 2018-01-02 caused pacemaker to fail

2018-01-10 Thread Victor Tapia
In my opinion, from the list of desired properties, only the second one is true: i) Corosync can be used on its own, regardless of having pacemaker installed or not. Starting both of them would force to mask pacemaker's unit file under particular scenarios. iii) IIRC, pacemaker requires

[Sts-sponsors] [Bug 1739033] Re: Corosync: Assertion 'sender_node != NULL' failed when bind iface is ready after corosync boots

2017-12-22 Thread Victor Tapia
#VERIFICATION FOR TRUSTY - Packages ii corosync 2.3.3-1ubuntu4 amd64Standards-based cluster framework (daemon and modules) ii libcorosync-common4 2.3.3-1ubuntu4 amd64Standards-based

[Sts-sponsors] [Bug 1739033] Re: Corosync: Assertion 'sender_node != NULL' failed when bind iface is ready after corosync boots

2017-12-22 Thread Victor Tapia
#VERIFICATION FOR XENIAL - Packages ii corosync 2.3.5-3ubuntu2 amd64cluster engine daemon and utilities ii libcorosync-common4:amd642.3.5-3ubuntu2 amd64cluster engine common library -

[Sts-sponsors] [Bug 1739033] Re: Corosync: Assertion 'sender_node != NULL' failed when bind iface is ready after corosync boots

2017-12-21 Thread Victor Tapia
Yes, the fix is already included in zesty+ (2.4.0+) -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1739033 Title: Corosync: Assertion 'sender_node != NULL' failed when bind iface is ready

[Sts-sponsors] [Bug 1739033] Re: Corosync: Assertion 'sender_node != NULL' failed when bind iface is ready after corosync boots

2017-12-20 Thread Victor Tapia
** Patch added: "Trusty patch" https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1739033/+attachment/5025215/+files/fix-lp1739033-trusty.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.

[Sts-sponsors] [Bug 1739033] Re: Corosync: Assertion 'sender_node != NULL' failed when bind iface is ready after corosync boots

2017-12-20 Thread Victor Tapia
** Patch added: "Xenial patch" https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1739033/+attachment/5025216/+files/fix-lp1739033-xenial.debdiff -- You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.