Page MenuHomeClusterLabs Projects

Probes should be ordered before stops of other resources
Open, HighPublic

Assigned To
None
Authored By
kgaillot
Aug 5 2024, 1:24 PM
Tags
  • Restricted Project
  • Restricted Project
  • Restricted Project
  • Restricted Project
Referenced Files
None
Subscribers

Description

In this scenario:

  • A cluster has a group with multiple members, and a primitive ordered after the group
  • An internal group member fails and is recovered
  • The failure is cleaned

The clean-up erases the history of the internal group member, which causes the scheduler to treat it as Stopped and schedule a probe of it along with recovery of all later group members and the primitive (since they are all ordered after the previously failed member). When the probe returns OK, the transition will be aborted and the recoveries should be avoided.

However currently, the scheduler will not order the stop of the primitive after the probe of the previously failed member. Thus it gets recovered even if the probe finds the member OK.

Event Timeline

kgaillot triaged this task as High priority.Aug 5 2024, 1:24 PM
kgaillot created this task.
kgaillot created this object with edit policy "Restricted Project (Project)".