Remove tempest container support from Wallaby release
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
In Progress
|
Critical
|
chandan kumar |
Bug Description
During Queens release, since all the services shipped are containerized.
So, we also shipped tempest in a container.
Earlier we used to test tempest container in tripleo ci jobs using tripleo-
we worked very hard to consolidate tempest execution/
Ansible role openstack-
This role is so extensible that it solved all the use cases related to tempest.
Due to this, we are deprecating the validate-tempest role this year and tempest container is no longer used and tested in CI.
From Queens to till now, we have received doc bugs related to the tempest container and the tempest container contains so many hacks to run it. It is very hard to maintain.
There are no users we have seen, so we are removing the tempest container.
Here is the tripleo-common patch for Removing tempest container build:
https:/
Here is the RH bugzilla for tracking the same: https:/
Changed in tripleo: | |
milestone: | wallaby-3 → wallaby-rc1 |
Changed in tripleo: | |
milestone: | wallaby-rc1 → xena-1 |
Changed in tripleo: | |
milestone: | xena-1 → xena-2 |
Changed in tripleo: | |
milestone: | xena-2 → xena-3 |
https:/ /review. opendev. org/c/openstack /tripleo- heat-templates/ +/776615 Remove tempest container support from tht