libffi-dev is missing in bindep.txt

Bug #1697613 reported by Akihiro Motoki
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Ihar Hrachyshka

Bug Description

When installing PyNaCL (required via paramiko by tempest) from tarball, libffi-dev is required. When a wheel package is not available, the installation fails.

This also happens for cffi (required by oslo.privsep).

Revision history for this message
Akihiro Motoki (amotoki) wrote :

I checked if there are missing bindep entries other than libffi-dev, but it looks like libffi-dev is the only one.

I checked it in the following steps.

- Prepare Ubuntu 16.04 with minimum installation
- Create a new virtualenv
- pip install bindep
- sudo apt-get install `bindep -b -r bindep.txt test'
- sudo apt-get install libffi-dev
- pip install --no-binary :all: -r requirements.txt -r test-requirements.txt
(we can avoid using wheel packages by --no-binary :all: option)

Changed in neutron:
importance: Undecided → Low
Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

This also breaks pep8 job.

Changed in neutron:
status: New → Confirmed
importance: Low → Critical
Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :
Changed in neutron:
assignee: nobody → Ihar Hrachyshka (ihar-hrachyshka)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Submitter: Jenkins
Branch: master

commit 8e8f721f6ff615bf43f8563e8940e4d46388c0e7
Author: Akihiro Motoki <email address hidden>
Date: Tue Jun 13 07:29:39 2017 +0000

    Add libffi-dev to bindep.txt

    libffi-dev is required to install cffi and PyNaCL from tarballs.
    cffi is installed from requirements.txt, so 'test' profile is not

    We usual use wheel packages when installing python packages,
    but tarball is sometimes used, for example, when a new version
    is uploaded. I think it is worth adding it to bindep.txt
    to avoid accidental gate failure.

    Closes-Bug: #1697613
    Change-Id: I4800c9f213fa5c8f28c8603e022264e6aa139090

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron

This issue was fixed in the openstack/neutron development milestone.

tags: added: neutron-proactive-backport-potential
tags: removed: neutron-proactive-backport-potential
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.