RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1314413 - swift-proxy-server depends on packaging for 3 erasure pllugins causing swift-proxy-server to fail to start
Summary: swift-proxy-server depends on packaging for 3 erasure pllugins causing swift-...
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-swift
Version: trunk
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: Kilo
Assignee: Tzach Shefi
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 14:23 UTC by Steven Dake
Modified: 2016-05-19 15:34 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:34:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Steven Dake 2016-03-03 14:23:05 UTC
Description of problem:
swift-proxy-server fails to start.  I think the issue is that the following dependencies are not installed:
[1] Jerasure, C library that supports erasure coding in storage applications, h
ttp://jerasure.org
 [2] Intel(R) Storage Acceleration Library (Open Source Version), https://01.org
/intel%C2%AE-storage-acceleration-library-open-source-version
 [4] Kota Tsuyuzaki <tsuyuzaki.kota.co.jp>, Ryuta Kon <kon.ryuta
.co.jp>, "NTT SHSS Erasure Coding backend"

I built the library myself (the erasure library) and it does not build the dependencies that erasure is looking for here:

https://bugs.launchpad.net/kolla/+bug/1552669


Version-Release number of selected component (if applicable):
v1.0.9

How reproducible:
100%

Steps to Reproduce:
1. Deploy swift in Kolla (which deploys swift-proxy-server)
2. swift-proxy-server restarts
3.

Actual results:
swift-proxy-server fails to complete startup

Expected results:
swift-proxy-server should complete startup

Additional info:
original bug report https://bugs.launchpad.net/kolla/+bug/1552669

Comment 1 Chandan Kumar 2016-05-19 15:34:31 UTC
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.


Note You need to log in before you can comment on or make changes to this bug.