Description of problem:
Samba requires backend LDAP servers to support bitwise operations
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Search with filters like
No match on the extended matching rule
This patch works for Samba's tests, but hasn't been more broadly or specifically
Created attachment 154518 [details]
Patch to implement bitwise operations
Your implementation looks good.
Created attachment 154865 [details]
cvs commit log
I added an --enable-bitwise option to configure (on by default - use
--disable-bitwise to disable it). I also added the plugin entry to the
configuration during new instance creation.
Samba4 uses this nicely, what do we need to wait for to close this bug as fixed?
(In reply to comment #4)
> Samba4 uses this nicely, what do we need to wait for to close this bug as fixed?
It takes a QA person to move this to the CLOSED/RESOLVED state. All us poor
developers can do is to move it to the MODIFIED state, which means some lucky QA
person has the task of verifying this.
Unfortunately, we have no QA directly assigned to Fedora DS.
So, for all intents and purposes, we can treat this bug as resolved since
bitwise is included in Fedora DS and works for its intended purpose.
(In reply to comment #0)
> Additional info:
> This patch works for Samba's tests, but hasn't been more broadly or specifically
Andrew - can you share or provide some information about where to find/view these samba tests ..
I take it that now Fedora DS now works as a Samba backend that this is all done?
Certainly, the LDAP tests I'm describing are now part of the standard testsuite, and that is run against Fedord DS (389).
We have a machine called buildsamba02 in the Samba build farm that is configured to run with DS backend. These are the test results:
As of today there are still about ~80 failures. Do you know which test cases involve bitwise operations?
This is covered by the filter/bitw_filter.sh test.
filter run Tests PASS : 100% (257/257)
Marking VERIFIED sanity.