detach health policy will not truly disable it in mult-engine environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
senlin |
Fix Released
|
High
|
RUIJIE YUAN |
Bug Description
When using pull model in health policy, we will select one engine to process it. We will record the engine id into DB and runtime data to that engine(health manager actually).
However, when we want to unregister the cluster, we dispatch this request to a NONE engine, which will be processed by one of the engine randomly, it will delete the DB record, but will not disable or unregister the cluster since we are not guaranteed to remove the runtime data from the right engine...
https:/
https:/
https:/
Changed in senlin: | |
assignee: | nobody → RUIJIE YUAN (cnjie0616) |
Changed in senlin: | |
status: | New → Triaged |
importance: | Undecided → High |
restart engine will reload the tasks. Just need to figure out how to dispatch the "unregister_ cluster" to the right engine.