pycparser-2.14 wheel is wrongly built and raises AssertionError

Bug #1629830 reported by Sylvain Bauza
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
New
Undecided
Unassigned
Magnum
New
Undecided
Unassigned
OpenStack Compute (nova)
Confirmed
Critical
Unassigned
OpenStack Heat
New
Undecided
Unassigned

Bug Description

Most of our gate jobs are impacted (Nova UTs, Tempest tests, Grenade checks) by a new respin of pycparser that raises an AssertionError when imported.

Note that not only Nova but a lot of OpenStack projects are impacted :
http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%20\%22AssertionError:%20sorry,%20but%20this%20version%20only%20supports%20100%20named%20groups\%22&from=24h

The issue has been logged upstream https://github.com/eliben/pycparser/issues/147 but we somehow need to downgrade pycparser first in order to stabilize our gates.

Tags: testing
Revision history for this message
Sylvain Bauza (sylvain-bauza) wrote :

We need to decouple Swift check from upper-constraint modifications as it prevents us to merge the pycparser downgrade because Swift doesn't actually use upper-constraints yet.. https://review.openstack.org/#/c/381031/1

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.