Page MenuHomeClusterLabs Projects
Create Task
Maniphest T908

Always use generated Corosync config in regression tests
Closed (Merged)Public
Actions

Assigned To
clumens
Authored By
kgaillot
Tue, Oct 29, 12:36 PM
Tags
  • Restricted Project
  • Restricted Project
  • Restricted Project
Referenced Files
None
Subscribers
kgaillot

Description

The cts-attrd, cts-fencing, and cts-exec regression tests run Corosync. That can be a problem if tests are run on more than one node in a cluster at the same time (for example, cts-fencing assumes no other node besides the local one will respond to fence queries).

The tests use the APIs in python/pacemaker/_cts/corosync.py. The APIs currently use any existing corosync.conf if present, otherwise they generate a new (single-node cluster) config. If there is an existing corosync.conf, we should temporarily rename it, generate a new config, and move the original one back when done.

Note that cts-lab uses cmcorosync.py instead of corosync.py, so it should be unaffected.

Revisions and Commits

rP Pacemaker
rPdfa8f13145c6 Fix: python: Always use generated corosync config in regression tests

Event Timeline

kgaillot triaged this task as Normal priority.Tue, Oct 29, 12:36 PM
kgaillot created this task.
kgaillot created this object with edit policy "Restricted Project (Project)".
clumens changed the task status from Open to WIP.Tue, Nov 12, 11:45 AM
clumens claimed this task.
clumens closed this task as Merged by committing rPdfa8f13145c6: Fix: python: Always use generated corosync config in regression tests.Tue, Nov 12, 5:54 PM
clumens added a commit: rPdfa8f13145c6: Fix: python: Always use generated corosync config in regression tests.
kgaillot added a project: Restricted Project.Tue, Nov 12, 7:07 PM