Steps to reproduce:
1. Deploy cluster
2. When cluster is deployed successfully invoke ostf
3. When tests executions begin - go to the action tab and reset cluster
4. When reset task finish - back to health check tab and see results
Expected results:
there are no running tests on reset cluster. Also there is no forked running ostf processes on muster node
Actual Result:
Tests are running (some of them failed without any message (nodes are in bootrap))
Forked ostf proccess are running om master node
root 14973 0.1 5.0 342952 51648 ? S 13:14 0:03 \_ /opt/fuel_plugins/ostf/bin/python /opt/fuel_plugins/ostf/bin/ostf-server --host=127.0.0.1 --port=8777 --log_file=/var/log/ostf.log --dbpath postgresql+psycopg2://ostf:ostf@127.0.0.1:5432/ostf
root 17827 0.0 4.6 341920 47560 ? S 14:07 0:00 \_ /opt/fuel_plugins/ostf/bin/python /opt/fuel_plugins/ostf/bin/ostf-server --host=127.0.0.1 --port=8777 --log_file=/var/log/ostf.log --dbpath postgresql+psycopg2://ostf:ostf@127.0.0.1:5432/ostf
It should not be done on nailgun or orchestrator side.
Nailgun and orchestrator should know nothing about ostf and other fuel plugins.
Do you have some kind of master process where you can monitor state of cluster and in case if cluster changed its state just kill child processes?