[389-devel] Build failed in Jenkins: 389-ds-base #1208

2017-03-13 Thread jenkins 
See 

Changes:

[William Brown] Ticket 49165 pw_verify did not handle external auth

--
Started by an SCM change
Building remotely on F25 (Fedora25 fedora Fedora fedora25) in workspace 

Wiping out workspace first.
Cloning the remote Git repository
Cloning repository http://pagure.io/389-ds-base.git
 > git init  # 
 > timeout=10
Fetching upstream changes from http://pagure.io/389-ds-base.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > http://pagure.io/389-ds-base.git +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url http://pagure.io/389-ds-base.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
 > git config remote.origin.url http://pagure.io/389-ds-base.git # timeout=10
Fetching upstream changes from http://pagure.io/389-ds-base.git
 > git -c core.askpass=true fetch --tags --progress 
 > http://pagure.io/389-ds-base.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 8dbfff1ff4152afb018490886a612c448ea2a1b0 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 8dbfff1ff4152afb018490886a612c448ea2a1b0
 > git rev-list 3038411c2b0e61a30fa47875ffb617736135c6c3 # timeout=10
[389-ds-base] $ /bin/sh -e /tmp/hudson1516686220889945925.sh

Running configure...
CFLAGS= -Wall CXXFLAGS= -Wall ./configure --with-tmpfiles-d=/etc/tmpfiles.d 
--with-openldap --enable-autobind --enable-gcc-security --with-selinux 
--with-systemdsystemunitdir=/lib/systemd/system 
--with-systemdsystemconfdir=/etc/systemd/system --enable-debug
Build log is 
https://jenkins.fedorainfracloud.org/job/389-ds-base/ws/build.1208.txt
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:29: installing './compile'
configure.ac:25: installing './config.guess'
configure.ac:25: installing './config.sub'
configure.ac:14: installing './install-sh'
configure.ac:14: installing './missing'
Makefile.am: installing './depcomp'
parallel-tests: installing './test-driver'
autoreconf: Leaving directory `.'

Running make...
Build log is 
https://jenkins.fedorainfracloud.org/job/389-ds-base/ws/build.1208.txt

Checking for warnings...
Build https://jenkins.fedorainfracloud.org/job/389-ds-base/1208/ failed
There are build warnings
Warning log is 
https://jenkins.fedorainfracloud.org/job/389-ds-base/ws/build-warns.1208.txt
Last 100 lines of warning log:

ldap/servers/slapd/pw_verify.c:106:9: warning: unused variable ‘rc’ 
[-Wunused-variable]


Build step 'Execute shell' marked build as failure
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Urgent: please review external bind fix

2017-03-13 Thread William Brown 
https://pagure.io/389-ds-base/issue/49165

https://pagure.io/389-ds-base/issue/raw/files/9c8c82e1a43e1adf854e0857e5b12ad6de4c7bdc1f1836c1c6ae064ed57ee37b-0001-Ticket-49165-pw_verify-did-not-handle-external-auth.patch

-- 
Sincerely,

William Brown
Software Engineer
Red Hat, Australia/Brisbane



signature.asc
Description: This is a digitally signed message part
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Re: Questions related to lib389 issue #1 cn=config

2017-03-13 Thread William Brown 
On Mon, 2017-03-13 at 06:06 +, Ankit Yadav wrote:
> Hello Everyone,
> 
> I am currently working on one of the issue of lib389 issue #1 cn=config. 
> Below are some steps that I did to help myself and a question related to 
> these steps.
> 
> lib389 issue #1 Description: 
> Once we have enough plugin and index code, we should be able to use dsconf to 
> compare the state of two instances. This will let us check for differing 
> plugin, index, configuration values between two servers.
> Additionally, we would be able to mask "known different" values, such as fs 
> paths, hostnames, etc.
> This will help in migrations and upgrades of DS.
> 
> I have an instance of 389-ds installed with this configuration:
> 
> computer name = local.com
> system user = dirsrv
> system group = dirsrv
> network port = 389
> directory server identifier = local
> suffix dc=local
> cn = Directory Manager
> 
> To see configuration of server I tried this command : $ ldapsearch -H ldap:// 
> -x -s base -b "" -LLL "+"
> 
> I got this output: 
> 
> dn:
> creatorsName: cn=server,cn=plugins,cn=config
> modifiersName: cn=server,cn=plugins,cn=config
> createTimestamp: 20170313052148Z
> modifyTimestamp: 20170313052148Z
> nsUniqueId: f4bebe00-07ac11e7-8000-
> namingContexts: dc=local
> nsBackendSuffix: userRoot:dc=local
> subschemaSubentry: cn=schema
> supportedExtension: 2.16.840.1.113730.3.5.7
> supportedExtension: 2.16.840.1.113730.3.5.8
> supportedExtension: 1.3.6.1.4.1.4203.1.11.3
> supportedExtension: 2.16.840.1.113730.3.5.3
> supportedExtension: 2.16.840.1.113730.3.5.12
> supportedExtension: 2.16.840.1.113730.3.5.5
> supportedExtension: 2.16.840.1.113730.3.5.6
> supportedExtension: 2.16.840.1.113730.3.5.9
> supportedExtension: 2.16.840.1.113730.3.5.4
> supportedExtension: 2.16.840.1.113730.3.6.5
> supportedExtension: 2.16.840.1.113730.3.6.6
> supportedExtension: 2.16.840.1.113730.3.6.7
> supportedExtension: 2.16.840.1.113730.3.6.8
> supportedExtension: 1.3.6.1.4.1.4203.1.11.1
> supportedControl: 2.16.840.1.113730.3.4.2
> supportedControl: 2.16.840.1.113730.3.4.3
> supportedControl: 2.16.840.1.113730.3.4.4
> supportedControl: 2.16.840.1.113730.3.4.5
> supportedControl: 1.2.840.113556.1.4.473
> supportedControl: 2.16.840.1.113730.3.4.9
> supportedControl: 2.16.840.1.113730.3.4.16
> supportedControl: 2.16.840.1.113730.3.4.15
> supportedControl: 2.16.840.1.113730.3.4.17
> supportedControl: 2.16.840.1.113730.3.4.19
> supportedControl: 1.3.6.1.1.13.1
> supportedControl: 1.3.6.1.1.13.2
> supportedControl: 1.3.6.1.4.1.42.2.27.8.5.1
> supportedControl: 1.3.6.1.4.1.42.2.27.9.5.2
> supportedControl: 1.2.840.113556.1.4.319
> supportedControl: 1.3.6.1.4.1.42.2.27.9.5.8
> supportedControl: 1.3.6.1.4.1.4203.666.5.16
> supportedControl: 2.16.840.1.113730.3.4.14
> supportedControl: 2.16.840.1.113730.3.4.20
> supportedControl: 1.3.6.1.4.1.1466.29539.12
> supportedControl: 2.16.840.1.113730.3.4.12
> supportedControl: 2.16.840.1.113730.3.4.18
> supportedControl: 2.16.840.1.113730.3.4.13
> supportedFeatures: 1.3.6.1.4.1.4203.1.5.1
> supportedSASLMechanisms: EXTERNAL
> supportedSASLMechanisms: SCRAM-SHA-1
> supportedSASLMechanisms: GSS-SPNEGO
> supportedSASLMechanisms: GSSAPI
> supportedSASLMechanisms: DIGEST-MD5
> supportedSASLMechanisms: CRAM-MD5
> supportedSASLMechanisms: PLAIN
> supportedSASLMechanisms: LOGIN
> supportedSASLMechanisms: ANONYMOUS
> supportedLDAPVersion: 2
> supportedLDAPVersion: 3
> vendorName: 389 Project
> vendorVersion: 389-Directory/1.3.5.15 B2016.308.2026
> 
> Are the above attributes and those configuration attributes which we are 
> trying to compare in this issue are same?

This output you are seeing is the rootDSE: It describes the features and
supported components of the server.

You will eventually be looking at cn=config, but for now your first
check to make the comparison work should be looking at objects from
lib389/idm/group.py for example. Make two groups in dc=example,dc=com,
then compare them.

You'll need a reproducable environment, so first, look at creating a
py.test case in lib389/tests/, and getting that to work, to build and
tear down an instance. We have plenty of examples in that folder of how
to do this. 

From there you can create the groups, then work on the comparison. 

I hope that helps you, 


> 
> Sincerely,
> 
> William Brown
> Software Engineer
> Red Hat, Australia/Brisbane
> 


signature.asc
Description: This is a digitally signed message part
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] please review: Issue 49062 - Reset replication agreement status after total init

2017-03-13 Thread Mark Reynolds 
https://pagure.io/389-ds-base/issue/49062

https://pagure.io/389-ds-base/issue/raw/files/c1454c1a2b025d750a3bf4722983a397dc140489ffae63a72f7bcceb86d82c8b-0001-Issue-49062-Reset-agmt-update-staus-and-total-init.patch
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Questions related to lib389 issue #1 cn=config

2017-03-13 Thread Ankit Yadav 
Hello Everyone,

I am currently working on one of the issue of lib389 issue #1 cn=config. Below 
are some steps that I did to help myself and a question related to these steps.

lib389 issue #1 Description: 
Once we have enough plugin and index code, we should be able to use dsconf to 
compare the state of two instances. This will let us check for differing 
plugin, index, configuration values between two servers.
Additionally, we would be able to mask "known different" values, such as fs 
paths, hostnames, etc.
This will help in migrations and upgrades of DS.

I have an instance of 389-ds installed with this configuration:

computer name = local.com
system user = dirsrv
system group = dirsrv
network port = 389
directory server identifier = local
suffix dc=local
cn = Directory Manager

To see configuration of server I tried this command : $ ldapsearch -H ldap:// 
-x -s base -b "" -LLL "+"

I got this output: 

dn:
creatorsName: cn=server,cn=plugins,cn=config
modifiersName: cn=server,cn=plugins,cn=config
createTimestamp: 20170313052148Z
modifyTimestamp: 20170313052148Z
nsUniqueId: f4bebe00-07ac11e7-8000-
namingContexts: dc=local
nsBackendSuffix: userRoot:dc=local
subschemaSubentry: cn=schema
supportedExtension: 2.16.840.1.113730.3.5.7
supportedExtension: 2.16.840.1.113730.3.5.8
supportedExtension: 1.3.6.1.4.1.4203.1.11.3
supportedExtension: 2.16.840.1.113730.3.5.3
supportedExtension: 2.16.840.1.113730.3.5.12
supportedExtension: 2.16.840.1.113730.3.5.5
supportedExtension: 2.16.840.1.113730.3.5.6
supportedExtension: 2.16.840.1.113730.3.5.9
supportedExtension: 2.16.840.1.113730.3.5.4
supportedExtension: 2.16.840.1.113730.3.6.5
supportedExtension: 2.16.840.1.113730.3.6.6
supportedExtension: 2.16.840.1.113730.3.6.7
supportedExtension: 2.16.840.1.113730.3.6.8
supportedExtension: 1.3.6.1.4.1.4203.1.11.1
supportedControl: 2.16.840.1.113730.3.4.2
supportedControl: 2.16.840.1.113730.3.4.3
supportedControl: 2.16.840.1.113730.3.4.4
supportedControl: 2.16.840.1.113730.3.4.5
supportedControl: 1.2.840.113556.1.4.473
supportedControl: 2.16.840.1.113730.3.4.9
supportedControl: 2.16.840.1.113730.3.4.16
supportedControl: 2.16.840.1.113730.3.4.15
supportedControl: 2.16.840.1.113730.3.4.17
supportedControl: 2.16.840.1.113730.3.4.19
supportedControl: 1.3.6.1.1.13.1
supportedControl: 1.3.6.1.1.13.2
supportedControl: 1.3.6.1.4.1.42.2.27.8.5.1
supportedControl: 1.3.6.1.4.1.42.2.27.9.5.2
supportedControl: 1.2.840.113556.1.4.319
supportedControl: 1.3.6.1.4.1.42.2.27.9.5.8
supportedControl: 1.3.6.1.4.1.4203.666.5.16
supportedControl: 2.16.840.1.113730.3.4.14
supportedControl: 2.16.840.1.113730.3.4.20
supportedControl: 1.3.6.1.4.1.1466.29539.12
supportedControl: 2.16.840.1.113730.3.4.12
supportedControl: 2.16.840.1.113730.3.4.18
supportedControl: 2.16.840.1.113730.3.4.13
supportedFeatures: 1.3.6.1.4.1.4203.1.5.1
supportedSASLMechanisms: EXTERNAL
supportedSASLMechanisms: SCRAM-SHA-1
supportedSASLMechanisms: GSS-SPNEGO
supportedSASLMechanisms: GSSAPI
supportedSASLMechanisms: DIGEST-MD5
supportedSASLMechanisms: CRAM-MD5
supportedSASLMechanisms: PLAIN
supportedSASLMechanisms: LOGIN
supportedSASLMechanisms: ANONYMOUS
supportedLDAPVersion: 2
supportedLDAPVersion: 3
vendorName: 389 Project
vendorVersion: 389-Directory/1.3.5.15 B2016.308.2026

Are the above attributes and those configuration attributes which we are trying 
to compare in this issue are same?
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org