Barbican cannot build on F20

Bug #1353696 reported by James Li
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Barbican
Fix Released
Medium
Ravi Sankar Penta

Bug Description

2014-08-06 00:44:20.046 | In file included from src/module.c:24:0:
2014-08-06 00:44:20.046 |
2014-08-06 00:44:20.046 | src/connection.h:33:21: fatal error: sqlite3.h: No such file or directory
2014-08-06 00:44:20.046 |
2014-08-06 00:44:20.046 | #include "sqlite3.h"
2014-08-06 00:44:20.046 |
2014-08-06 00:44:20.046 | ^
2014-08-06 00:44:20.046 |
2014-08-06 00:44:20.046 | compilation terminated.
2014-08-06 00:44:20.046 |
2014-08-06 00:44:20.046 | error: command 'gcc' failed with exit status 1

Full log is here:
http://logs.openstack.org/46/111846/1/check/gate-solum-devstack-dsvm-f20/3a67480/logs/devstacklog.txt.gz

Revision history for this message
Venkat Sundaram (tsv) wrote :

Is libsqlite3-dev package installed ?

sudo apt-get install libsqlite3-dev

Revision history for this message
Douglas Mendizábal (dougmendizabal) wrote :

I agree with Venkat that this error seems like you're missing the sqlite headers. For fedora the command to install them should be:

sudo yum install sqlite-devel

Revision history for this message
James Li (james-li-3) wrote :

Thanks! we are seeing this error on Solum gate as we want to use barbican.

So is it reasonable to update contrib/devstack/lib/barbican to take care of the case of Fedora?

Changed in barbican:
assignee: nobody → Ravi Sankar Penta (ravips)
Changed in barbican:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to barbican (master)

Reviewed: https://review.openstack.org/113404
Committed: https://git.openstack.org/cgit/openstack/barbican/commit/?id=126b9a032ab25642caf4bbcbf64811f186ca4b96
Submitter: Jenkins
Branch: master

commit 126b9a032ab25642caf4bbcbf64811f186ca4b96
Author: Ravi Sankar Penta <email address hidden>
Date: Mon Aug 11 16:23:30 2014 -0700

    Install sqlite-devel package on fedora

    On fedora-20 when devstack tries to install barbican,
    it is failing with missing sqlite headers. Added sqlite-devel
    pkg to resolve the issue.

    Closes-Bug: #1353696
    Change-Id: Ib2bb66ac6805693d2c275ca7cba0879e141659da

Changed in barbican:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to barbican (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/115122

Revision history for this message
Ravi Sankar Penta (ravips) wrote :
Revision history for this message
Ravi Sankar Penta (ravips) wrote :

Adding some background for comment #5 and #6.
Change in comment #4 fixed gcc complaining sqlite3.h header but still barbican failed on F20 with 'Cloning not allowed in this configuration' error, more error details are provided in comment #6 log file.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to barbican (master)

Reviewed: https://review.openstack.org/115122
Committed: https://git.openstack.org/cgit/openstack/barbican/commit/?id=6fba9d6785e3b0a4b4c55475e29a16a8b0ceb0be
Submitter: Jenkins
Branch: master

commit 6fba9d6785e3b0a4b4c55475e29a16a8b0ceb0be
Author: Ravi Sankar Penta <email address hidden>
Date: Mon Aug 18 14:33:12 2014 -0700

    Allow devstack to do git clone of barbican

    Currently on F20 env when devstack tries to install barbican and
    barbicanclient, it's failing as corresponding dir doesn't exist and
    ERROR_ON_CLONE=True. As barbican is not part of devstack yet,
    we don't expect this dir to be present in this case, we should
    set ERROR_ON_CLONE=False to allow devstack to do git clone.

    Related-Bug: #1353696
    Change-Id: I3c362f1b2e6c9abf940ea68a12085dd747ede37c

Thierry Carrez (ttx)
Changed in barbican:
milestone: none → juno-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in barbican:
milestone: juno-3 → 2014.2
Changed in barbican:
importance: Undecided → Medium
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.