The "Waiting for node up" task always fails #13

New issue

Closed

opened 2025-12-28 18:01:53 +00:00 by sami · 1 comment

sami commented

2025-12-28 18:01:53 +00:00

Owner

Originally created by @EESergey on GitHub (Jul 11, 2024).

Originally assigned to: @532910 on GitHub.

Current Behavior

The Waiting for node up task cannot complete successfully on all servers because the neofs-ir service has not yet started on them.

Expected Behavior

The check must be run after the neofs-ir service has been launched on all servers.

Possible Solution

Change the task sequence.

Context

Some versions do not work due to a large difference in the start time of the neofs-ir service.
Playbook execution time increases significantly.

Originally created by @EESergey on GitHub (Jul 11, 2024). Originally assigned to: @532910 on GitHub. ## Current Behavior The [Waiting for node up](https://github.com/nspcc-dev/ansible-neofs/blob/master/roles/ir/handlers/restart.yml) task cannot complete successfully on all servers because the neofs-ir service has not yet started on them. ## Expected Behavior The check must be run after the neofs-ir service has been launched on all servers. ## Possible Solution Change the task sequence. ## Context Some versions do not work due to a large difference in the start time of the neofs-ir service. Playbook execution time increases significantly.

sami

2025-12-28 18:01:53 +00:00

closed this issue
added the
bug

U2

S4

I4
labels

sami commented

2025-12-28 18:01:53 +00:00

Author

Owner

@carpawell commented on GitHub (Jul 11, 2024):

The key problem here is ansible waits for IR to be READY, while IR waits for the other IRs to finish deployment before becoming READY.

@carpawell commented on GitHub (Jul 11, 2024): The key problem here is ansible waits for IR to be READY, while IR waits for the other IRs to finish deployment before becoming READY.