ironic-api and pecan 1.0.2/1.0.3/1.0.4 are incompatible

Bug #1615645 reported by Vasyl Saienko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ironic
Won't Fix
Undecided
Unassigned

Bug Description

Installing pecan 1.0.2/1.0.3/1.0.4 and launching ironic-api service (both master/newton and stable/mitaka) leads to the following traceback with any API call (for example ironic node-list)

http://paste.openstack.org/show/562208/

pip list |grep pecan
pecan (1.0.2)
sphinxcontrib-pecanwsme (0.8.0)

pecan 1.0.5 works just fine.

Revision history for this message
Pavlo Shchelokovskyy (pshchelo) wrote :

By simple experiment on DevStack master I've found that earliest Pecan version that does not exhibit this bug is 1.0.5.

Seems we need to bump the global requirements

Vasyl Saienko (vsaienko)
description: updated
summary: - ironic-api and pecan 1.0.2 are incompatible
+ ironic-api and pecan 1.0.2/1.0.3/1.0.4 are incompatible
Revision history for this message
Pavlo Shchelokovskyy (pshchelo) wrote :

Correction - 1.0.0 (lowest version from global requirements) and 1.0.1 do work.
Faulty versions are 1.0.2, 1.0.3, 1.0.4

Revision history for this message
Dmitry Tantsur (divius) wrote :

You're right, it was a bug in pecan back then. As it was fixed, I don't think we can do anything on Ironic side (keep in mind that requirements are not bumped for bug fixes, only for features).

Changed in ironic:
status: New → Won't Fix
Revision history for this message
Pavlo Shchelokovskyy (pshchelo) wrote :

Dmitry, why not just block the faulty versions in requirements then? !=1.0.2,... especially if it is a known problem. Otherwise OpenStack packagers have no knowledge that these particular versions can not in fact be used.

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.