[GH-ISSUE #6] [BUG] Removing cluster node errors on "wait_spin 15" #2

New issue

Closed

opened 2026-03-03 01:17:18 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 01:17:18 +03:00

Owner

Originally created by @oskari on GitHub (Jan 16, 2025).
Original GitHub issue: https://github.com/coelacant1/ProxmoxScripts/issues/6

Description

Apparently there's command that is not defined anywhere? I can't even find on google what wait_spin should be?

Steps to Reproduce

clone repo
make scripts executable
run ./GUI.sh
Select 1 for cluster, then 4 to remove cluster node
Give node name as parameter

Expected Behavior

No error, node removed

Screenshots/Logs

Example usage (from script comments):
./RemoveClusterNode.sh [--force] <node_name>

=== Enter parameters for cc_pve/Cluster/RemoveClusterNode.sh (type 'c' to cancel or leave empty to run no-args):
pve-m2

=== Running: cc_pve/Cluster/RemoveClusterNode.sh pve-m2 ===
Node is in a cluster named: Karpalo
Checking for VMs/containers on node "pve-m2"...
=== Removing node "pve-m2" from the cluster ===
[main] notice: resolved node name 'pve-m2' to 'xxx' for default node IP address
[main] notice: forcing local mode (although corosync.conf exists)
Connection to xxx closed.
Running: pvecm delnode pve-m2
Could not kill node (error = CS_ERR_NOT_EXIST)
Killing node 1
/root/ProxmoxScripts/Cluster/RemoveClusterNode.sh: line 104: wait_spin: command not found
[ERROR] line 104, exit code 0 while executing: wait_spin 15

Originally created by @oskari on GitHub (Jan 16, 2025). Original GitHub issue: https://github.com/coelacant1/ProxmoxScripts/issues/6 ## Description Apparently there's command that is not defined anywhere? I can't even find on google what `wait_spin` should be? ## Steps to Reproduce 1. clone repo 2. make scripts executable 3. run `./GUI.sh` 4. Select 1 for cluster, then 4 to remove cluster node 5. Give node name as parameter ## Expected Behavior No error, node removed ## Screenshots/Logs Example usage (from script comments): ./RemoveClusterNode.sh [--force] <node_name> === Enter parameters for cc_pve/Cluster/RemoveClusterNode.sh (type 'c' to cancel or leave empty to run no-args): pve-m2 === Running: cc_pve/Cluster/RemoveClusterNode.sh pve-m2 === Node is in a cluster named: Karpalo Checking for VMs/containers on node "pve-m2"... === Removing node "pve-m2" from the cluster === [main] notice: resolved node name 'pve-m2' to 'xxx' for default node IP address [main] notice: forcing local mode (although corosync.conf exists) Connection to xxx closed. Running: pvecm delnode pve-m2 Could not kill node (error = CS_ERR_NOT_EXIST) Killing node 1 /root/ProxmoxScripts/Cluster/RemoveClusterNode.sh: line 104: wait_spin: command not found [ERROR] line 104, exit code 0 while executing: wait_spin 15

kerem

2026-03-03 01:17:18 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 01:17:19 +03:00

Author

Owner

@raymondh2 commented on GitHub (Jan 16, 2025):

You would seem to be correct. I assume it's a variation of the spin function in Utilities.

@raymondh2 commented on GitHub (Jan 16, 2025): You would seem to be correct. I assume it's a variation of the spin function in Utilities.

kerem commented

2026-03-03 01:17:19 +03:00

Author

Owner

@coelacant1 commented on GitHub (Jan 18, 2025):

Fixed the issue in the latest commit: github.com/coelacant1/ProxmoxScripts@1592e55b5a

This was referencing the testing version of the communication/spinner code. Forgot to update this file!

This was replaced with info() / update() / ok() / err() etc, now within the communication utility script

@coelacant1 commented on GitHub (Jan 18, 2025): Fixed the issue in the latest commit: https://github.com/coelacant1/ProxmoxScripts/commit/1592e55b5a489fc50b4b51e96b1d4383dc249ee1 This was referencing the testing version of the communication/spinner code. Forgot to update this file! This was replaced with info() / update() / ok() / err() etc, now within the communication utility script

kerem referenced this issue

2026-03-03 01:17:25 +03:00

[PR #2] [CLOSED] Update issue templates #20