mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
cli: Placement bulding error looks unclear #775
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#775
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cthulhu-rider on GitHub (Oct 7, 2022).
I formulated an a priori unenforceable network storage policy by making the number of replicas greater than the current number of nodes. I called
neofs-cli container nodescommand to check. Origin error wasWhile
not enough nodeslooks clear to me, selection part looks not, what empty string do we have here? I propose to clarify the case. Note that the error message is produces by NeoFS SDK Go lib.P.S. the case can be spread to other CLI commands which build container placement.