unable to return online state after maintenance #815

New issue

Closed

opened 2025-12-28 17:20:47 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:20:47 +00:00

Owner

Originally created by @vkarak1 on GitHub (Oct 18, 2022).

Originally assigned to: @fyrchik on GitHub.

Unable to return back to online state after maintenance mode

Expected Behavior

Node should be able to successfully set online state after maintenance mode.

Current Behavior

Node still in MAINTENANCE state when set-status --status online has been sent.

Steps to Reproduce (for bugs)

turn on Maintenance Mode config:
neofs-adm morph set-config MaintenanceModeAllowed=true -c configuration/config.yaml
Issue netmap snapshot to verify that the node is in online state:
neofs-cli netmap snapshot -g -r node1.neofs:8080
Set MM:
neofs-cli control set-status --status maintenance --endpoint localhost:8091 -w /etc/neofs/storage/wallet.json
Tick epoch:
neofs-adm morph force-new-epoch -c configuration/config.yaml
Issue netmap snapshot one more time (node state is maintenance):
neofs-cli netmap snapshot -g -r node1.neofs:8080
Set node to online state:
neofs-cli control set-status --status online --endpoint localhost:8091 -w /etc/neofs/storage/wallet.json
Tick epoch:
neofs-adm morph force-new-epoch -c configuration/config.yaml
Issue netmap to verify the status, where ONLINE status is expected:
neofs-adm morph force-new-epoch -c configuration/config.yaml

Actual result:
Node 3: 0266719a2438f03480efa6f29e895baa90bcb5e0aa398fb1c77398c377307cdabc MAINTENANCE /dns4/node2.neofs/tcp/8080

Your Environment

NeoFS Storage node
Version: v0.33.0-6-g4c63be66
GoVersion: go1.18.4

Linux buky 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) x86_64 GNU/Linux

Logs

Originally created by @vkarak1 on GitHub (Oct 18, 2022). Originally assigned to: @fyrchik on GitHub.  Unable to return back to online state after maintenance mode ## Expected Behavior  Node should be able to successfully set online state after maintenance mode. ## Current Behavior  Node still in MAINTENANCE state when set-status --status online has been sent. ## Steps to Reproduce (for bugs)  1. turn on Maintenance Mode config: `neofs-adm morph set-config MaintenanceModeAllowed=true -c configuration/config.yaml` 2. Issue netmap snapshot to verify that the node is in online state: `neofs-cli netmap snapshot -g -r node1.neofs:8080` 3. Set MM: `neofs-cli control set-status --status maintenance --endpoint localhost:8091 -w /etc/neofs/storage/wallet.json` 4. Tick epoch: `neofs-adm morph force-new-epoch -c configuration/config.yaml` 5. Issue netmap snapshot one more time (node state is maintenance): `neofs-cli netmap snapshot -g -r node1.neofs:8080` 6. Set node to online state: `neofs-cli control set-status --status online --endpoint localhost:8091 -w /etc/neofs/storage/wallet.json` 7. Tick epoch: `neofs-adm morph force-new-epoch -c configuration/config.yaml` 8. Issue netmap to verify the status, where ONLINE status is expected: `neofs-adm morph force-new-epoch -c configuration/config.yaml` Actual result: `Node 3: 0266719a2438f03480efa6f29e895baa90bcb5e0aa398fb1c77398c377307cdabc MAINTENANCE /dns4/node2.neofs/tcp/8080 ` ## Your Environment  NeoFS Storage node Version: v0.33.0-6-g4c63be66 GoVersion: go1.18.4 Linux buky 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) x86_64 GNU/Linux [Logs](https://github.com/nspcc-dev/neofs-node/files/9809948/node2.online.txt)