Hide Forgot
We were leapfrogged by RHEL, in this case. I'll need this BZ fully ACKed to get a build out the door. We might need another errata as well? Meanwhile, I've provided a scratch build here: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=10874601 Vivek, can you see if this resolves the issue? Updating the installed packages to the scratch-built ones and then doing yum update should suffice. If this succeeds, could you also verify that libtevent doesn't have any problems? We should remain on 0.9.26-1 from "rh-gluster-3-samba-for-rhel-6-server-rpms" rather than anything from "rhel-6-server-rpms". If not, I'll provide a rebuild for that as well.
RHEL6 with the scratch-build provided https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=10874600 On a successful yum update, the libtevent is not as expected by jose i. e (We should remain on 0.9.26-1 from "rh-gluster-3-samba-for-rhel-6-server-rpms") instead we get libtevent.x86_64 0.9.26-2.el6_7. ldb-tools.x86_64 1.1.25-2.1.el6rhs @/ldb-tools-1.1.25-2.1.el6rhs.x86_64 libldb.x86_64 1.1.25-2.1.el6rhs @/libldb-1.1.25-2.1.el6rhs.x86_64 libtalloc.x86_64 2.1.5-1.el6 @rhel-6-server-rpms libtdb.x86_64 1.3.8-1.el6_7 @rhel-6-server-rpms libtevent.x86_64 0.9.26-2.el6_7 @rhel-6-server-rpms
The reason of the problem is that RHEL ships libldb in the main channel and ldb-tools (which comes from the same source-RPM) in the optional channel, while RHGS ships ldb-tools and libldb in the same (samba) channel. Hence if ldb-tools is install without the RHEL optional channel being enabled, we can't upgrade to the RHEL version of libldb if that is newer... ==> Workaround: uninstall ldb-tools before upgrading! (ldb-tools are not needed anyways)
Successful yum update with lib packages, ldb-tools.x86_64 1.1.26-1.el6rhs @Samba-libs libldb.x86_64 1.1.26-1.el6rhs @Samba-libs libtdb.x86_64 1.3.8-1.1.el6rhs @Samba-libs libtevent.x86_64 0.9.28-1.el6rhs @Samba-libs tdb-tools.x86_64 1.3.8-1.1.el6rhs @Samba-libs Marking it as verified.
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/RHBA-2016-0673.html