RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1044140 - Allow search to look up 'in memory RUV'
Summary: Allow search to look up 'in memory RUV'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-17 21:19 UTC by Nathan Kinder
Modified: 2020-09-13 20:31 UTC (History)
2 users (show)

Fixed In Version: 389-ds-base-1.3.3.1-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 09:29:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 687 0 None None None 2020-09-13 20:31:12 UTC
Red Hat Product Errata RHSA-2015:0416 0 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 14:26:33 UTC

Description Nathan Kinder 2013-12-17 21:19:26 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47350

For a given replica, the ruv data structure is written back on a database entry with the DN "dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,<suffix>".

The database RUV is then look up by monitoring tools (like repl-monitor.pl or ldapsearch).
Since 1.2.8 (543633), see https://fedorahosted.org/389/ticket/564, in memory RUV is in sync with database RUV entry.

The fix for ticket 564, reintroduces a shift between in memory RUV/database RUV where in memory RUV reflects the exact state of the updates and database RUV is late ~30s.

This ticket is to create a new monitoring method to look up the in memory RUV.

We may use the replica_config_search (search on "cn=replica,cn="<suffix>",cn=mapping tree,cn=config") to handle that.
Comment 2 Viktor Ashirov 2015-01-19 03:57:25 UTC 
$ rpm -qa | grep 389
389-ds-base-debuginfo-1.3.3.1-11.el7.x86_64
389-ds-base-libs-1.3.3.1-11.el7.x86_64
389-ds-base-1.3.3.1-11.el7.x86_64

I'm using script from the upstream ticket
$ ./test_ruv 

=============== Mon Jan 19 04:43:46 CET 2015 =====================

DB  RUV= bc7b4a0000007b0000
MEM RUV= bc7b4a0000007b0000
modifying entry "uid=usr0,ou=People,dc=example,dc=com"

DB  RUV= bc7d710000007b0000
MEM RUV= bc7d710000007b0000

=============== Mon Jan 19 04:43:56 CET 2015 =====================

DB  RUV= bc7d710000007b0000
MEM RUV= bc7d710000007b0000
modifying entry "uid=usr0,ou=People,dc=example,dc=com"

DB  RUV= bc7d7b0000007b0000
MEM RUV= bc7d7b0000007b0000

=============== Mon Jan 19 04:44:26 CET 2015 =====================

DB  RUV= bc7d7b0000007b0000
MEM RUV= bc7d7b0000007b0000
modifying entry "uid=usr0,ou=People,dc=example,dc=com"

DB  RUV= bc7d990000007b0000
MEM RUV= bc7d990000007b0000


In memory RUV from 'cn=replica,cn=\"<suffix\",cn=mapping tree,cn=config' and DB RUV from 'nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,<suffix>' return the same value. 

Marking as VERIFIED.
Comment 4 errata-xmlrpc 2015-03-05 09:29:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0416.html
Note You need to log in before you can comment on or make changes to this bug.