[SSSD] [sssd PR#475][comment] AD: Use the right sdap_domain for the forest root

URL: https://github.com/SSSD/sssd/pull/475 Title: #475: AD: Use the right sdap_domain for the forest root lslebodn commented: """ I ran ad test suite and it cause crashes with direct AD domain. Nobody was able to authenticate. ``` sh# gdb /usr/libexec/sssd/sssd_be coredump GNU gdb (GDB) Red

[SSSD] [sssd PR#498][synchronized] DESKPROFILE: Do not require CAP_DAC_OVERRIDE

URL: https://github.com/SSSD/sssd/pull/498 Author: fidencio Title: #498: DESKPROFILE: Do not require CAP_DAC_OVERRIDE Action: synchronized To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/498/head:pr498 git checkout pr498 From

[SSSD] [sssd PR#498][comment] DESKPROFILE: Do not require CAP_DAC_OVERRIDE

URL: https://github.com/SSSD/sssd/pull/498 Title: #498: DESKPROFILE: Do not require CAP_DAC_OVERRIDE fidencio commented: """ Patch set has been updated! """ See the full comment at https://github.com/SSSD/sssd/pull/498#issuecomment-363520010 ___

[SSSD] [sssd PR#475][+Changes requested] AD: Use the right sdap_domain for the forest root

URL: https://github.com/SSSD/sssd/pull/475 Title: #475: AD: Use the right sdap_domain for the forest root Label: +Changes requested ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to

[SSSD] [sssd PR#507][synchronized] SELINUX: Check if SELinux is managed in selinux_child

URL: https://github.com/SSSD/sssd/pull/507 Author: mzidek-rh Title: #507: SELINUX: Check if SELinux is managed in selinux_child Action: synchronized To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/507/head:pr507 git checkout pr507 From

[SSSD] [sssd PR#507][comment] SELINUX: Check if SELinux is managed in selinux_child

URL: https://github.com/SSSD/sssd/pull/507 Title: #507: SELINUX: Check if SELinux is managed in selinux_child mzidek-rh commented: """ Here is some summary of the changes in the new version. After offline discussion with Lukas, these changes were done: - the function sss_is_selinux_managed

[SSSD] [sssd PR#498][-Changes requested] DESKPROFILE: Do not require CAP_DAC_OVERRIDE

URL: https://github.com/SSSD/sssd/pull/498 Title: #498: DESKPROFILE: Do not require CAP_DAC_OVERRIDE Label: -Changes requested ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to

[SSSD] [sssd PR#502][+Pushed] BUILD: Add missing libs found by -Wl,-z,defs

URL: https://github.com/SSSD/sssd/pull/502 Title: #502: BUILD: Add missing libs found by -Wl,-z,defs Label: +Pushed ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to

[SSSD] [sssd PR#502][comment] BUILD: Add missing libs found by -Wl,-z,defs

URL: https://github.com/SSSD/sssd/pull/502 Title: #502: BUILD: Add missing libs found by -Wl,-z,defs lslebodn commented: """ master: * b61304a9f0f6bcc099cb855bc5bde13c4024da1a * 7ad9f9c7c8b40e74647de455e454894a257bc0de """ See the full comment at

[SSSD] [sssd PR#507][synchronized] SELINUX: Check if SELinux is managed in selinux_child

URL: https://github.com/SSSD/sssd/pull/507 Author: mzidek-rh Title: #507: SELINUX: Check if SELinux is managed in selinux_child Action: synchronized To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/507/head:pr507 git checkout pr507 From

[SSSD] [sssd PR#507][comment] SELINUX: Check if SELinux is managed in selinux_child

URL: https://github.com/SSSD/sssd/pull/507 Title: #507: SELINUX: Check if SELinux is managed in selinux_child mzidek-rh commented: """ '!a' -> 'a == NULL' nitpick mentioned by @fidencio was fixed. Otherwise it is the same patch. """ See the full comment at

[SSSD] [sssd PR#502][closed] BUILD: Add missing libs found by -Wl,-z,defs

URL: https://github.com/SSSD/sssd/pull/502 Author: lslebodn Title: #502: BUILD: Add missing libs found by -Wl,-z,defs Action: closed To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/502/head:pr502 git checkout pr502

[SSSD] Re: SSSD Virtual Test Suite

On 11/13/2017 11:16 AM, Pavel Březina wrote: Hello, It took me a lot longer than I expected but here it is at last. This is my set of scripts that use vagrant and Ansible to automatically provision virtual environment that I use to develop and test SSSD. To create this environment you only

[SSSD] Re: Some performance ideas related to running sssd on cluster nodes

On Tue, Feb 06, 2018 at 09:55:00AM +0100, Pavel Březina wrote: > On 02/05/2018 03:38 PM, Jakub Hrozek wrote: > > Hi, > > > > I was helping analyze poor performance and server-side load spikes in an > > environment where cluster nodes running sssd were all booted up at the > > same time. > > > >

[SSSD] Re: Is this sort of test failure expected on a RHEL7.3+ environment?

On Mon, Feb 05, 2018 at 04:54:26PM +0100, Sumit Bose wrote: > On Sat, Feb 03, 2018 at 07:13:35AM -0800, Richard Sharpe wrote: > > On Sat, Feb 3, 2018 at 3:08 AM, Sumit Bose wrote: > > > On Fri, Feb 02, 2018 at 07:04:50PM -0800, Richard Sharpe wrote: > > >> Hi folks, > > >> > >

[SSSD] [sssd PR#438][comment] krb5_child: Distinguish between expired & disabled AD user

URL: https://github.com/SSSD/sssd/pull/438 Title: #438: krb5_child: Distinguish between expired & disabled AD user sumit-bose commented: """ Thank you for the rebase. I guess we can add further usage of the new code path when needed. CI passed http://vm/logs/job/83/57/summary.html, the

[SSSD] [sssd PR#438][+Accepted] krb5_child: Distinguish between expired & disabled AD user

URL: https://github.com/SSSD/sssd/pull/438 Title: #438: krb5_child: Distinguish between expired & disabled AD user Label: +Accepted ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to

[SSSD] [sssd PR#507][comment] SELINUX: Check if SELinux is managed in selinux_child

URL: https://github.com/SSSD/sssd/pull/507 Title: #507: SELINUX: Check if SELinux is managed in selinux_child jhrozek commented: """ I rebuilt the repo and restarted the jobs. The IDs are 2293818, 2293819, 2293820 and 2293821. """ See the full comment at

[SSSD] [sssd PR#510][comment] MAN: Explain how does auto_private_groups affect subdomains

URL: https://github.com/SSSD/sssd/pull/510 Title: #510: MAN: Explain how does auto_private_groups affect subdomains jhrozek commented: """ ok to test """ See the full comment at https://github.com/SSSD/sssd/pull/510#issuecomment-363580617 ___

[SSSD] [sssd PR#508][comment] Fix/suppress few gcc8 warnings

URL: https://github.com/SSSD/sssd/pull/508 Title: #508: Fix/suppress few gcc8 warnings fidencio commented: """ Many warnings have been updated a few days ago with those changes: https://github.com/coreutils/gnulib/blob/master/m4/manywarnings.m4 I'd prefer to have PR #378 updated, reviewed and

[SSSD] [sssd PR#507][comment] SELINUX: Check if SELinux is managed in selinux_child

URL: https://github.com/SSSD/sssd/pull/507 Title: #507: SELINUX: Check if SELinux is managed in selinux_child jhrozek commented: """ btw I also ran downstream tests with the original revision of the patch. I'm not sure if they would still help since the patch respun, nonetheless: -

[SSSD] [sssd PR#475][comment] AD: Use the right sdap_domain for the forest root

URL: https://github.com/SSSD/sssd/pull/475 Title: #475: AD: Use the right sdap_domain for the forest root jhrozek commented: """ Nevermind, I can reproduce that locally. Thank you for catching the bug. """ See the full comment at https://github.com/SSSD/sssd/pull/475#issuecomment-363574781

[SSSD] [sssd PR#475][comment] AD: Use the right sdap_domain for the forest root

URL: https://github.com/SSSD/sssd/pull/475 Title: #475: AD: Use the right sdap_domain for the forest root jhrozek commented: """ Is there any way you could send me more details how to reproduce the error? It is enough to send me a link to a downstream test if that's how you reproduced the

[SSSD] [sssd PR#475][+Changes requested] AD: Use the right sdap_domain for the forest root

URL: https://github.com/SSSD/sssd/pull/475 Title: #475: AD: Use the right sdap_domain for the forest root Label: +Changes requested ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to

[SSSD] [sssd PR#475][-Changes requested] AD: Use the right sdap_domain for the forest root

URL: https://github.com/SSSD/sssd/pull/475 Title: #475: AD: Use the right sdap_domain for the forest root Label: -Changes requested ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to

[SSSD] [sssd PR#507][comment] SELINUX: Check if SELinux is managed in selinux_child

URL: https://github.com/SSSD/sssd/pull/507 Title: #507: SELINUX: Check if SELinux is managed in selinux_child lslebodn commented: """ I did some testing on bare metal with disabled selinux and missing packages selinux-policy*. It fixed few issues but I have few comments. """ See the full

[SSSD] Re: Some performance ideas related to running sssd on cluster nodes

On 02/05/2018 03:38 PM, Jakub Hrozek wrote: Hi, I was helping analyze poor performance and server-side load spikes in an environment where cluster nodes running sssd were all booted up at the same time. It turned out that this meant cache entries were expiring at the same time and also the

[SSSD] [sssd PR#507][comment] SELINUX: Check if SELinux is managed in selinux_child

URL: https://github.com/SSSD/sssd/pull/507 Title: #507: SELINUX: Check if SELinux is managed in selinux_child fidencio commented: """ CI: http://vm-031.${abc}/logs/job/83/56/summary.html """ See the full comment at https://github.com/SSSD/sssd/pull/507#issuecomment-363423925

[SSSD] Re: Is this sort of test failure expected on a RHEL7.3+ environment?

On (06/02/18 10:47), Sumit Bose wrote: >On Mon, Feb 05, 2018 at 04:54:26PM +0100, Sumit Bose wrote: >> On Sat, Feb 03, 2018 at 07:13:35AM -0800, Richard Sharpe wrote: >> > On Sat, Feb 3, 2018 at 3:08 AM, Sumit Bose wrote: >> > > On Fri, Feb 02, 2018 at 07:04:50PM -0800, Richard