Hi Pierre, This is bug https://bugs.launchpad.net/devstack/+bug/1883468 You need to fix the uwsgi path on devstack plugin side too, I have pushed the fix on blazar - https://review.opendev.org/#/c/738071/ -gmann ---- On Thu, 25 Jun 2020 04:59:59 -0500 Pierre Riteau <pierre at stackhpc.com> wrote ---- > Hello, > > The blazar devstack CI jobs are currently failing due to issues > related to uwsgi. logs/screen-blazar-a.txt shows: > > Jun 25 09:26:47.037179 ubuntu-bionic-limestone-regionone-0017387278 > systemd[1]: Starting Devstack devstack at blazar-a.service... > Jun 25 09:26:47.038997 ubuntu-bionic-limestone-regionone-0017387278 > systemd[18254]: devstack at blazar-a.service: Failed to execute command: > No such file or directory > Jun 25 09:26:47.039047 ubuntu-bionic-limestone-regionone-0017387278 > systemd[18254]: devstack at blazar-a.service: Failed at step EXEC > spawning /usr/local/bin/uwsgi: No such file or directory > Jun 25 09:26:47.039445 ubuntu-bionic-limestone-regionone-0017387278 > systemd[1]: devstack at blazar-a.service: Main process exited, > code=exited, status=203/EXEC > Jun 25 09:26:47.039454 ubuntu-bionic-limestone-regionone-0017387278 > systemd[1]: devstack at blazar-a.service: Failed with result 'exit-code'. > Jun 25 09:26:47.039734 ubuntu-bionic-limestone-regionone-0017387278 > systemd[1]: Failed to start Devstack devstack at blazar-a.service. > > I think it's our devstack plugin that needs fixing. In the meantime no > need to recheck patches, they will keep failing until resolved. > > Pierre Riteau (priteau) > >