Node 3 details loading forever when node 2 is offline

I tested with Alma 9 cluster on Proxmox and Virtualbox.

When node 2 goes down, node 3 shows no node details:

After starting node 2, node 3 shows the details correctly.

EDIT:

Browser console:

cluster/task/da258311-fa33-4c4d-93ed-e69e3a76cb28 
Object { action: "get-cluster-status", data: null, extra: {…}, id: "da258311-fa33-4c4d-93ed-e69e3a76cb28", parent: "", queue: "cluster/tasks", timestamp: "2023-05-21T20:21:50.66642191Z", user: "admin" }
 
Object { progress: 100, status: "running" }
notification.js:213:14
cluster/task/da258311-fa33-4c4d-93ed-e69e3a76cb28 
Object { action: "get-cluster-status", data: null, extra: {…}, id: "da258311-fa33-4c4d-93ed-e69e3a76cb28", parent: "", queue: "cluster/tasks", timestamp: "2023-05-21T20:21:50.66642191Z", user: "admin" }
 
Object { progress: 100, status: "completed" }
​
progress: 100
​
status: "completed"
​
<prototype>: Object { … }
notification.js:213:14
taskResult get-info 
Object { error: "", exit_code: 0, file: "task/node/3/3b8f2c5b-a19b-4f65-963f-231cbba21b4d", output: {…} }
notification.js:231:16
taskResult get-info 
Object { error: "", exit_code: 0, file: "task/node/1/2deca2c3-17f7-45e1-9de9-5adecfd0b200", output: {…} }
notification.js:231:16
taskResult get-cluster-status 
Object { error: "Error executing task get-info on node/2 Client \"node/2\" was not found\n", exit_code: 0, file: "task/cluster/da258311-fa33-4c4d-93ed-e69e3a76cb28", output: {…} }
notification.js:231:16
node/1/task/4bb17057-9ad3-4541-a065-aef70f5ed031 
Object { action: "get-node-status", data: null, extra: {…}, id: "4bb17057-9ad3-4541-a065-aef70f5ed031", parent: "", queue: "node/1/tasks", timestamp: "2023-05-21T20:22:02.110081603Z", user: "admin" }
 
Object { progress: 0, status: "pending" }
notification.js:213:14
node/1/task/4bb17057-9ad3-4541-a065-aef70f5ed031 
Object { action: "get-node-status", data: null, extra: {…}, id: "4bb17057-9ad3-4541-a065-aef70f5ed031", parent: "", queue: "node/1/tasks", timestamp: "2023-05-21T20:22:02.110081603Z", user: "admin" }
 
Object { progress: 0, status: "running" }
notification.js:213:14
node/1/task/4bb17057-9ad3-4541-a065-aef70f5ed031 
Object { action: "get-node-status", data: null, extra: {…}, id: "4bb17057-9ad3-4541-a065-aef70f5ed031", parent: "", queue: "node/1/tasks", timestamp: "2023-05-21T20:22:02.110081603Z", user: "admin" }
 
Object { progress: 100, status: "running" }
notification.js:213:14
node/1/task/4bb17057-9ad3-4541-a065-aef70f5ed031 
Object { action: "get-node-status", data: null, extra: {…}, id: "4bb17057-9ad3-4541-a065-aef70f5ed031", parent: "", queue: "node/1/tasks", timestamp: "2023-05-21T20:22:02.110081603Z", user: "admin" }
 
Object { progress: 100, status: "completed" }
notification.js:213:14
cluster/task/7fe03d30-17a3-4390-a80b-b87ffcefb297 
Object { action: "get-cluster-status", data: null, extra: {…}, id: "7fe03d30-17a3-4390-a80b-b87ffcefb297", parent: "", queue: "cluster/tasks", timestamp: "2023-05-21T19:47:42.83459957Z", user: "admin" }
 
Object { progress: 0, status: "running" }
notification.js:213:14
cluster/task/5d501cc5-955f-4f0e-bfe9-938a3306eb06 
Object { action: "get-cluster-status", data: null, extra: {…}, id: "5d501cc5-955f-4f0e-bfe9-938a3306eb06", parent: "", queue: "cluster/tasks", timestamp: "2023-05-21T19:47:47.820488639Z", user: "admin" }
 
Object { progress: 0, status: "running" }
notification.js:213:14
taskResult get-node-status 
Object { error: "", exit_code: 0, file: "task/node/1/4bb17057-9ad3-4541-a065-aef70f5ed031", output: {…} }
notification.js:231:16
2 Likes

Thank you for reporting.
We already plan to refactor the page, but indeed this is a case we should test.
Card added: Trello

2 Likes

As your exit codes are 0, I think this PR should fix the reported #bug

1 Like