Thanks for the response Tim - I know its not technically a "libec" or swift issue as such, but would be cool to debug it further (I'm pretty sure we ran into a similar situation last cycle)
Here is the section for the ec-tests storage policy:
[storage-policy:1]
name = ec-tests
policy_type = erasure_coding
A couple things to note, on a "not working" install, I can update to liberasurecode-1.5.0 and it works fine (after restarting the services), however newer installs seem to be working with 1.4.0 - also this only seems to impact CentOS7 builds. (Swift settings are the same).
Thanks for the response Tim - I know its not technically a "libec" or swift issue as such, but would be cool to debug it further (I'm pretty sure we ran into a similar situation last cycle)
Here is the section for the ec-tests storage policy:
[storage-policy:1]
name = ec-tests
policy_type = erasure_coding
ec_type = liberasurecode_ rs_vand data_fragments = 3 parity_ fragments = 2 segment_ size = 1048576
ec_num_
ec_num_
ec_object_
A couple things to note, on a "not working" install, I can update to liberasurecode- 1.5.0 and it works fine (after restarting the services), however newer installs seem to be working with 1.4.0 - also this only seems to impact CentOS7 builds. (Swift settings are the same).
I've done a package comparison between a working build from http:// logs.openstack. org/07/ 488507/ 1/check/ gate-openstack- ansible- os_swift- ansible- func-centos- 7/7e6277f/ console. html#_2017- 07-28_16_ 35_33_056669 for which I added some debug tasks, and a failed build I have:
[root@swift- storage1 ~]# diff good_rpms.txt bad_rpms.txt e451e5b5- 54c22d60
60d59
< gpg-pubkey-
So I don't think there is an issue with different installed packages.
Here is a coredump (or atleast the first 10 lines from the back trace): http:// paste.openstack .org/show/ 616921/
I can get more if that'd help! (It's on liberasurecode- 1.4.0-1)