Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 739502

Summary:	ctdb init script must use tdbdump and tdbtool from tdb-tools
Product:	Red Hat Enterprise Linux 5	Reporter:	Sumit Bose <sbose>
Component:	ctdb	Assignee:	Sumit Bose <sbose>
Status:	CLOSED ERRATA	QA Contact:	Cluster QE <mspqa-list>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	5.7	CC:	bgollahe, djansa, jpayne, sgallagh
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ctdb-1.0.112-2.el5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-08 07:29:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	736112

Description Sumit Bose 2011-09-19 10:03:22 UTC

Description of problem:

A conflict in the samba and the tdb-tools packages make is necessary to rename the binaries form tdb-tools. Since some of them are used by the ctdb start script it has to be updated to search for the tools under their new name.

Comment 1 RHEL Program Management 2011-09-23 00:53:56 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 7 Justin Payne 2012-08-06 16:27:44 UTC

Verified in ctdb-1.0.112-2.el5:

[root@dash-03 ~]# grep ctdb /var/log/yum.log 
Aug 06 11:17:57 Installed: ctdb-1.0.112-1.el5.x86_64
Aug 06 11:22:13 Updated: ctdb-1.0.112-2.el5.x86_64
[root@dash-03 ~]# rpm -q ctdb
ctdb-1.0.112-2.el5
[root@dash-03 ~]# diff /etc/init.d/ctdb /root/ctdb
112,125d111
<       local TDBTOOL12_HAS_CHECK=`echo "help" | /usr/bin/tdbtool12 | grep check | wc -l`
< 
<       test x"$TDBTOOL12_HAS_CHECK" = x"1" && {
<               #
<               # Note tdbtool12 always exits with 0
<               #
<               local OK=`/usr/bin/tdbtool12 $PDBASE check | grep "Database integrity is OK" | wc -l`
<               test x"$OK" = x"1" || {
<                       return 1;
<               }
< 
<               return 0;
<       }
<

Comment 9 errata-xmlrpc 2013-01-08 07:29:54 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.

http://rhn.redhat.com/errata/RHBA-2013-0059.html