nspcc-dev / nspcc-dev/neofs-node

7 IR nodes take too much time to deploy

Open
#3,697 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug I4 neofs-ir S4 U2
Dominant language
Go
Stars
38
Forks
51
Avg merge
1d 20h
Merged PRs (30d)
38

Description

COMMAND: ./neofs-cli --config /home/runner/work/neofs-testcases/neofs-testcases/neofs-testcases/test-run-2025-11-24-00-20-11-073849/env_files/neofs-env-2025-11-24-00-39-51-140432251341696/inner_ring_adddgqxpbd/ir_cli_config_sjubosyzif.yml control healthcheck --endpoint 'localhost:59263' --ir
RETCODE: 1

STDOUT:
Health status: INITIALIZING_NETWORK

STDERR:

Start / End / Elapsed	 00:44:08.568351 / 00:44:09.104425 / 0:00:00.536074

...

COMMAND: ./neofs-cli --config /home/runner/work/neofs-testcases/neofs-testcases/neofs-testcases/test-run-2025-11-24-00-20-11-073849/env_files/neofs-env-2025-11-24-00-39-51-140432251341696/inner_ring_adddgqxpbd/ir_cli_config_sjubosyzif.yml control healthcheck --endpoint 'localhost:59263' --ir
RETCODE: 1

STDOUT:
Health status: INITIALIZING_NETWORK

STDERR:

Start / End / Elapsed	 00:49:07.444896 / 00:49:07.955859 / 0:00:00.510963

Logs:

ir0 node logs-2.zip
ir1 node logs.zip
ir2 node logs.zip
ir3 node logs.zip
ir4 node logs.zip
ir5 node logs.zip
ir6 node logs.zip

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the recorded neofs-cli control healthcheck commands and compare the seven attached node logs, from ir0 node logs-2.zip through ir6 node logs.zip. Investigate why the nodes remain in INITIALIZING_NETWORK and take too long to deploy; done means identifying the cause and demonstrating that the healthcheck completes successfully within the expected deployment time.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.