redstack stop does not stops the conductor process
Bug #1283276 reported by
Sushil Kumar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Trove Integration |
Triaged
|
Low
|
Unassigned | ||
Bug Description
When doing a redstack stop it shutsdown tr-api and tr-tmgr but tr-cond still remains live.
This could be foud by checking screen sessions also (screen -x)
Even after kick-start process there comes up 2 tr-cond processes in screen
Steps to reproduce
Stop the stack completely
redstack stop
redstack stop-deps
Start it
redstack start-deps
Stop trove processes only
redstack stop
Now log-in to screen, screen -x, and see one tr-cond is still alive.
| Changed in trove-integration: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| milestone: | none → juno-1 |
To post a comment you must log in.
