Tempest plugin is no more compatible with other plugins used in CI
Bug #1589964 reported by
Valeriy Ponomaryov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Critical
|
Valeriy Ponomaryov |
Bug Description
Recently merged commit to "neutron-fwaas" project [1] started using one of Tempest's modules that appeared after version our plugin uses. It forces us either to start using latest Tempest (which is correct approach) or to disable "neutron-fwaas"'s plugin (which is applicable only as fast workaround until we make all compatibility changes to latest Tempest in our plugin).
For the moment, we cannot switch to latest Tempest as we already have incompatibility for it, see bug [2].
[1] https:/
[2] https:/
Changed in manila: | |
importance: | Undecided → Critical |
assignee: | nobody → Valeriy Ponomaryov (vponomaryov) |
milestone: | none → newton-2 |
status: | New → In Progress |
tags: | added: tempest |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/326442
Review: https:/