Red Hat Bugzilla – Bug 1339870
/usr/bin/rados depends on libradosstriper.so.1
Last modified: 2017-07-30 11:07:07 EDT
Description of problem: /usr/bin/rados depends on libradosstriper.so.1, and we do not want to ship libradosstriper in RHCS. Version-Release number of selected component (if applicable): ceph-common-10.2.1-8.el7cp How reproducible: always Steps to Reproduce: yum install ceph-common Actual results: yum installs libradosstriper1 Expected results: yum should not install libradosstriper1
Looks like $(LIBRADOSSTRIPER) was added to rados_LDADD in https://github.com/ceph/ceph/commit/49ab5bb3c436fbe069327859c76b351c4fe06043 I don't know whether we would want to back that patch out downstream (if that's feasible?), or whether we should just ship libradosstriper in the product. Neil, what is your opinion?
It's there to support some additional options to the rados command for manipulating striped objects, came from the community.
Sam, how easy/hard would it be to back out this change in jewel?
Kne, I am not clear on why you don't want to ship this library?
In RHCS 1.3 we made the decision to not ship it: bz 1212208
The comments on 1212208 seem to indicate there were some concerns about the test coverage of the package, and hence stability & maintainability. Sam: are you willing to vouch and maintain the code?
Discussed in the scrub call today with Neil and Sam. Sam will patch this out upstream, and in the meantime we will ship libradosstriper in order to satisfy the package dependency for betas of RHCS 2. But we need to patch this out before GA.
Just pushed wip-bz1341859 to rhgerrit. I'm not sure how to verify that the packages build.
In rhgerrit as wip-bz1339870 (sorry, I had the bz number wrong in the previous message).
*** Bug 1345789 has been marked as a duplicate of this bug. ***
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-1755.html