Tempest concurrency seems to be breaking tests
Bug #1790943 reported by
Alex Kavanagh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nova-lxd |
Won't Fix
|
High
|
Unassigned |
Bug Description
Tempest concurrency of more than 1 seems to be breaking tests.
It's not clear whether this is a nova-lxd <-> pylxd <-> lxd issue, or a problem in tempest.
As a temporary measure, setting the TEMPEST_CONCURRENCY env variable to 1 seems to clear the problem.
Changed in nova-lxd: | |
assignee: | nobody → Alex Kavanagh (ajkavanagh) |
status: | New → In Progress |
importance: | Undecided → High |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/599351 /git.openstack. org/cgit/ openstack/ nova-lxd/ commit/ ?id=c4c16bcf497 ef77119509f6ab6 3a3b769e41e9be
Committed: https:/
Submitter: Zuul
Branch: master
commit c4c16bcf497ef77 119509f6ab63a3b 769e41e9be
Author: Alex Kavanagh <email address hidden>
Date: Mon Sep 3 11:33:57 2018 +0100
Fix bug in scenario/manager and cover it with pep8
manager.py had a syntax error which caused the module to be not tempest_ plugin so that the module
installable. This wasn't picked up in testing. This fixes the bug
and adds pep8 coverage to the nova_lxd_
always remains installable.
Also, this fixes the tempest concurrency at 1. See the related bugs.
Closes-bug: #1790956 7f6363877ff03f0 f9bfc8f3d43
Related-Bug: #1790943
Change-Id: Ie542b062a9f099