Yes. It’s affecting manila tests as well:

Patch: https://review.openstack.org/#/c/414286/
Failure: 
http://logs.openstack.org/86/414286/2/gate/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/a79dc50/logs/devstacklog.txt.gz#_2016-12-23_13_26_11_470

Version of OSC: 
http://logs.openstack.org/86/414286/2/gate/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/a79dc50/logs/devstacklog.txt.gz#_2016-12-23_13_19_04_456
 (1.2.0)
Version of OpenStackSDK: 
http://logs.openstack.org/86/414286/2/gate/gate-manila-tempest-minimal-dsvm-lvm-ubuntu-xenial/a79dc50/logs/devstacklog.txt.gz#_2016-12-23_13_19_53_450
 (0.9.11)


From: Steve Martinelli <[email protected]>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<[email protected]>
Date: Friday, December 23, 2016 at 9:16 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<[email protected]>
Subject: Re: [openstack-dev] [all] Intermittent gate failures across multiple 
projects

Those look like they were introduced in the latest release, and related to the 
OpenStackSDK refactoring that hit openstackclient networking commands. We 
actually released the new version because folks were hitting similar errors, 
but for more often used commands (like listing security groups or IPs.)

Is the latest OSC affecting a gate for you?


On Dec 23, 2016 8:33 AM, "Andrey Kurilin" 
<[email protected]<mailto:[email protected]>> wrote:
Hi eveyone!
I found two more failures related to openstackclient which had appeared 
recently:

- "HttpException: Bad Request" while trying to set quotas via openstackclient
  
http://logs.openstack.org/43/414543/1/check/gate-rally-dsvm-neutron-existing-users-rally/36518f0/console.html#_2016-12-23_11_31_55_070176
- "'SecurityGroup' object has no attribute 'keys'" while creating new security 
group
  
http://logs.openstack.org/64/355264/5/check/gate-manila-tempest-dsvm-mysql-generic-ubuntu-xenial-nv/9ff7aec/logs/devstacklog.txt.gz#_2016-12-23_12_53_44_213
State of latest openstackclient doesn't look good to me :(


On Fri, Dec 23, 2016 at 5:24 AM, Tony Breeds 
<[email protected]<mailto:[email protected]>> wrote:
On Thu, Dec 22, 2016 at 04:31:38PM -0800, John Villalovos wrote:
> We believe the error is caused by a bad wheel for lxml 3.7.0 that was
> pushed today to PyPi
>
> Thanks to everyone working together on this issue in #openstack-infra !
>
> A patch is proposed to blacklist that release and we are testing it now.
The fix is now merged so if you're jobs failed with 'Illegal Instruction' feel
free to recheck without swamping our CI.  I believe that eleastic-recheck should
tell you if you match this case.

Thanks to those that found the root cause and worked on the fix

Yours Tony.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
[email protected]?subject:unsubscribe<http://[email protected]?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Best regards,
Andrey Kurilin.

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
[email protected]?subject:unsubscribe<http://[email protected]?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to