Bug 1467997

Summary:	upgrade liberasurecode and pyeclib libraries to 1.5.0
Product:	Red Hat OpenStack	Reporter:	Thiago da Silva <thiago>
Component:	liberasurecode	Assignee:	Jon Schlueter <jschluet>
Status:	CLOSED ERRATA	QA Contact:	Mike Abrams <mabrams>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	12.0 (Pike)	CC:	apevec, derekh, lhh, pgrist, srevivo, thiago, zaitcev
Target Milestone:	beta	Keywords:	Rebase, Triaged
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	liberasurecode-1.5.0-1.el7ost python-pyeclib-1.5.0-1.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1468002 1518834 (view as bug list)		Environment:
Last Closed:	2017-12-13 21:39:17 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:
Embargoed:
Bug Depends On:	1468002
Bug Blocks:	1518834

Description Thiago da Silva 2017-07-05 18:23:10 UTC

new liberasurecode and pyeclib rpms should be built and included in Pike. Release 1.5.0 was released last week:

liberasurecode: https://github.com/openstack/liberasurecode/releases/tag/1.5.0

pyeclib: https://github.com/openstack/pyeclib/releases/tag/1.5.0

Comment 1 Jon Schlueter 2017-07-05 20:41:40 UTC

RDO bug for rebase filed and being worked on.  Once builds are in RDO these will make their way into OSP 12

Comment 2 Pete Zaitcev 2017-07-06 01:15:06 UTC

Well, good luck with that. So far, I hit a couple of problems:

- Cannot build 1.5.0 on a system that already has 1.4.0 installed. It will then include system headers sometimes and pull the wrong version.

- Koji blows up with
/builddir/build/BUILD/liberasurecode-1.5.0/test/.libs/lt-liberasurecode_test: error while loading shared libraries: liberasurecode.so.1: cannot open shared object file: No such file or directory

Of course you can just disable the %check step, but generally 1.5.0
seems like rife with regressions. At least we don't yet have the CRC32
debacle in.

Comment 10 errata-xmlrpc 2017-12-13 21:39:17 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.

https://access.redhat.com/errata/RHEA-2017:3462

Comment 12 Red Hat Bugzilla 2023-09-14 04:00:40 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days