Bug 929114 – cleanAllRUV task fails to cleanup config upon completion

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 929114 - cleanAllRUV task fails to cleanup config upon completion

Summary:	cleanAllRUV task fails to cleanup config upon completion

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	389-ds-base (Show other bugs)
Sub Component:
Version:	6.4
Hardware:	Unspecified Unspecified

Priority	urgent Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	Rich Megginson
QA Contact:	Sankar Ramalingam
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:	923503
Blocks:
	Show dependency tree / graph

Reported:	2013-03-29 05:33 EDT by Libor Miksik
Modified:	2013-07-22 14:20 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:	389-ds-base-1.2.11.15-14.el6_4
Doc Type:	Bug Fix
Doc Text:	A task manually constructed an exact value to be removed from the configuration if the "replica-force-cleaning" option was used. Consequently, the task configuration was not cleaned up, and every time the server was restarted, the task behaved in the described manner. This update searches the configuration for the exact value to delete, instead of manually building the value, and the task does not restart when the server is restarted
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-04-15 14:23:12 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2013:0742	normal	SHIPPED_LIVE	Low: 389-ds-base security and bug fix update	2013-04-15 18:21:56 EDT

Groups: None (edit)

Description Libor Miksik 2013-03-29 05:33:59 EDT

This bug has been copied from bug #923503 and has been proposed
to be backported to 6.4 z-stream (EUS).

Comment 4 Sankar Ramalingam 2013-04-13 02:20:45 EDT

Cleanallruv abort task is gracefully exiting if there are no cleanallruv tasks running. 
ldapmodify -ax -D "cn=directory manager" -h localhost -p 1189 -w Secret123 << EOF
dn: cn=M1Task2,cn=abort cleanallruv,cn=tasks,cn=config
cn: M1Task2
objectclass: extensibleObject
replica-base-dn: dc=passsync,dc=com
replica-id: 1234
EOF
adding new entry "cn=M1Task2,cn=abort cleanallruv,cn=tasks,cn=config"
ldap_add: Server is unwilling to perform (53)
	additional info: Replica id (1234) is not being cleaned, nothing to abort.


Also, when the server restarts, it cleans up the failed cleanallruv abort task.
==> /var/log/dirsrv/slapd-M1/errors <==
[13/Apr/2013:02:15:18 -0400] - slapd shutting down - signaling operation threads
[13/Apr/2013:02:15:18 -0400] - slapd shutting down - waiting for 20 threads to terminate
[13/Apr/2013:02:15:18 -0400] - slapd shutting down - closing down internal subsystems and plugins
[13/Apr/2013:02:15:19 -0400] NSMMReplicationPlugin - Abort CleanAllRUV Task: Abort task failed, will resume the task at the next server startup.
[13/Apr/2013:02:15:19 -0400] - Waiting for 4 database threads to stop
[13/Apr/2013:02:15:19 -0400] - All database threads now stopped
[13/Apr/2013:02:15:19 -0400] - slapd stopped.
[13/Apr/2013:02:15:21 -0400] - 389-Directory/1.2.11.15 B2013.100.2247 starting up
[13/Apr/2013:02:15:21 -0400] NSMMReplicationPlugin - Abort CleanAllRUV Task: replica id(1234) is not being cleaned, nothing to abort.  Aborting abort task.


Hence marking the bug as Verified.
rpm -qa |grep -i 389-ds-base
389-ds-base-1.2.11.15-14.el6_4.x86_64
389-ds-base-devel-1.2.11.15-14.el6_4.x86_64
389-ds-base-debuginfo-1.2.11.15-14.el6_4.x86_64
389-ds-base-libs-1.2.11.15-14.el6_4.x86_64

Comment 6 errata-xmlrpc 2013-04-15 14:23:12 EDT

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.

http://rhn.redhat.com/errata/RHSA-2013-0742.html

Note You need to log in before you can comment on or make changes to this bug.