devstack fails with wsgi-file services on master and epoxy branches

Bug #2109604 reported by kay
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
Invalid
Undecided
Unassigned

Bug Description

Recent master branch and epoxy barbican <email address hidden> are failing with the:

failed to open python file /opt/stack/data/venv/bin/barbican-wsgi-api
unable to load app 0 (mountpoint='') (callable not found or import error)

It seems that the transition to WSGI module path was not properly finished. Keystone was successfully migrated to module path: https://github.com/openstack/devstack/commit/c1eeb773a85b0485b6329e325ac1685d8e3b2dc4

But barbican still uses `wsgi-file = /opt/stack/data/venv/bin/barbican-wsgi-api`, but this file doesn't exist anymore:

# ls -la /opt/stack/data/venv/bin/barbican-wsgi-api
ls: cannot access '/opt/stack/data/venv/bin/barbican-wsgi-api': No such file or directory

Lots of functional tests, based on devstack are failing now, see:

* https://github.com/terraform-provider-openstack/terraform-provider-openstack/pull/1851
* https://github.com/gophercloud/gophercloud/pull/3356

Latest successful tests was executed on 27.04.2025.

Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :
Changed in devstack:
status: New → Invalid
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.