[OSTF] OSTF processes should be killed when resetting or stopping deployment task starts

Bug #1286151 reported by Tatyanka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Triaged
High
Fuel Sustaining
Mitaka
Won't Fix
High
Fuel Python (Deprecated)

Bug Description

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

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :
Revision history for this message
Evgeniy L (rustyrobot) wrote :

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?

Changed in fuel:
status: New → Confirmed
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

need to be discussed, as for now, we do not have such process. May be we should add some polling service(in ostf) that will poll cluster status and ostf processes(include main process and it subproc) and interrupt it(subproc) by signal in case if cluster is not ready. Lets discuss it in irc

Changed in fuel:
assignee: nobody → Artem Roma (aroma-x)
Changed in fuel:
milestone: 5.0 → 5.1
Revision history for this message
Dima Shulyak (dshulyak) wrote :

Evgeniy, ostf it is just client-server application.

To add process that monitors nailgun state - means adding separate process, that will be wasted in 99% time.

Good approach would be to use rabbitmq notifications, with fanout topic, where any application can listen for events.

As a quick fix, i dont see any issues if this will be implemented in astute.

Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 5.1 → 6.0
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 6.0 → 6.1
Artem Roma (aroma-x)
Changed in fuel:
assignee: Artem Roma (aroma-x) → Fuel Python Team (fuel-python)
Dmitry Pyzhov (dpyzhov)
tags: added: feature
Dmitry Pyzhov (dpyzhov)
tags: added: feature-reset-env module-ostf
removed: ostf
tags: added: feature-stop-deployment
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

We are lack of resources in 6.1. Moved to 7.0

Changed in fuel:
milestone: 6.1 → 7.0
tags: added: qa-agree-7.0
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 7.0 → 8.0
Changed in fuel:
importance: Medium → High
status: Confirmed → Triaged
Dmitry Pyzhov (dpyzhov)
tags: added: area-python
Changed in fuel:
milestone: 8.0 → 9.0
tags: added: area-ostf
removed: module-ostf
Changed in fuel:
milestone: 9.0 → 10.0
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

It is a feature request and we cannot backport it to Mitaka.

Dmitry Pyzhov (dpyzhov)
Changed in fuel:
assignee: Fuel Python (Deprecated) (fuel-python) → Fuel Sustaining (fuel-sustaining-team)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.