Bug 1040426

Summary:	Rebase ctdb to 2.5.1
Product:	Red Hat Enterprise Linux 7	Reporter:	Sumit Bose <sbose>
Component:	ctdb	Assignee:	Sumit Bose <sbose>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Cluster QE <mspqa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	jpayne
Target Milestone:	rc	Keywords:	Rebase
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ctdb-2.5.1-1.el7	Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-13 10:16:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sumit Bose 2013-12-11 12:21:34 UTC

I would recommend to rebase ctdb to the latest upstream release 2.5.1.

Besides various bug fixes there are a couple of additional reasons to consider a rebase:

- since version 2,4 ctdb has native systemd support. The upstream systemd support is based on the patches used for the current RHEL7 build the enhancements and modifications were done upstream. A rebase would make coordination with upstream easier in the context of systemd related issues.
- other products like RHS might want to use a more current version in their next release: A rebase would help to minimize the different version we have to maintain.
- since version 2.5 ctdb is reintegrated into the samba source tree and the next major samba release would contain ctdb as part of samba. A rebase would help to lower the update efforts on RH and customer side when samba is rebased to a version including ctdb.

Comment 2 Justin Payne 2014-04-09 16:12:31 UTC

Marking Verified:

-bash-4.1$ for i in `seq 1 3`; do qarsh root@dash-0$i rpm -q ctdb; done
ctdb-2.5.1-2.el7.x86_64
ctdb-2.5.1-2.el7.x86_64
ctdb-2.5.1-2.el7.x86_64

Comment 3 Ludek Smid 2014-06-13 10:16:13 UTC

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.