[Rdo-list] Announce: All 2014.1.2 updates now live

Eric Harney eharney at redhat.com
Thu Sep 11 15:22:11 UTC 2014


On 09/11/2014 11:18 AM, Dafna Ron wrote:
> Adding David and Yaniv Eylon
> 
> On 09/11/2014 04:03 PM, Kaul, Yaniv wrote:
>>> -----Original Message-----
>>> From: Dafna Ron [mailto:dron at redhat.com]
>>> Sent: Thursday, September 11, 2014 6:01 PM
>>> To: Kaul, Yaniv; Rich Bowen; rdo-list at redhat.com; eha >> Eric Harney
>>> Subject: Re: [Rdo-list] Announce: All 2014.1.2 updates now live
>>>
>>> Hi Yaniv,
>>>
>>> I encountered this when doing cinder upgrades and found the same
>>> reported by
>>> users on line:
>>>
>>> https://ask.openstack.org/en/question/28335/you-should-rebuild-using-libgmp-
>>>
>>> 5-to-avoid-timing-attack-vulnerability-_warnnot-using-mpz_powm_sec-you-
>>> should-rebuild-using-libgmp-5-to-avoid-timing/
>> The warning is not the problem. I've lived with it for months.
>>
>> "Non-zero exit code (2) from test listing."
>>
>> Is the issue.
>> The advised workaround to downgrade some Python packages did not work
>> for me (comment 12 @ https://bugs.launchpad.net/tempest/+bug/1277538 )
>> Y.
>>
>>
>>
>>> There is a bug reported on this as well for this as well in bugzilla.
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1123339
>>>
>>> adding Eric if tempest tests are braking on RDO.
>>>
>>> Thanks!
>>> Dafna
>>>
>>>
>>> On 09/11/2014 03:55 PM, Kaul, Yaniv wrote:
>>>>> -----Original Message-----
>>>>> From: rdo-list-bounces at redhat.com
>>>>> [mailto:rdo-list-bounces at redhat.com] On Behalf Of Rich Bowen
>>>>> Sent: Thursday, September 11, 2014 4:34 PM
>>>>> To: rdo-list at redhat.com
>>>>> Subject: [Rdo-list] Announce: All 2014.1.2 updates now live
>>>>>
>>>>> Those of you who were waiting for the 2014.1.2 updates for EL6, they
>>>>> have emerged successfully from the CI testing process, and are now
>>>>> available at
>>>>> https://repos.fedorapeople.org/repos/openstack/openstack-icehouse/epe
>>>>> l-
>>>>> 6/?C=M;O=D
>>>>>
>>>>> As always, questions and concerns should come back to this list. We
>>>>> eagerly anticipate your feedback on these packages.
>>>>>
>>>>> --Rich
>>>> I wonder if it can explain the breakage in Tempest tests. I have not
>>>> changed
>>> anything in my environment or deployment script, yet Tempest fails:
>>>> /run_tempest.sh -N --serial 'tempest.api.volume*'
>>>> /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57:
>>> PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using
>>> libgmp >= 5 to avoid timing attack vulnerability.
>>>>     _warn("Not using mpz_powm_sec.  You should rebuild using libgmp >=
>>>> 5 to avoid timing attack vulnerability.", PowmInsecureWarning)
>>>> Non-zero exit
>>> code (2) from test listing.
>>>> ----------------------------------------------------------------------
>>>> Ran 0 tests in 5.070s
>>>>
>>>>
>>>>

The "Non-zero exit code (2) from test listing." sounds like testr is
failing within tempest itself.  Tempest should have a log file (or the
ability to generate one) which will tell you what error actually
occurred here.

This means that tempest failed to load up its own tests independently of
the other OpenStack services, I believe.




More information about the dev mailing list