Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

crm config delete should check or wait until pacemaker scheduler is IDLE #1631

Open
zzhou1 opened this issue Dec 16, 2024 · 0 comments
Open

Comments

@zzhou1
Copy link
Contributor

zzhou1 commented Dec 16, 2024

Here is the example,

  1. setup a ocfs2 cluster
    adm@tws-1:~> sudo crm cluster init -ys /dev/disk/by-partlabel/sbd-tw -o /dev/disk/by-partlabel/ocfs2

  2. sudo crm resource stop ocfs2-clone

  3. sudo crm config del ocfs2-clone ocfs2-group ocfs2-clusterfs dlm

The improvement is about step#3, to let it by default to check or wait until pacemaker scheduler is IDLE before proceed. Otherwise, there could be the faulty situation step#2 RA does not fully stopped, the delete operations in step#3 can fail badly in the middle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant