Add volume for morph_chain #70
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-dev-env#70
Loading…
Reference in a new issue
No description provided.
Delete branch "achuprov/frostfs-dev-env:feat/morph_chain_volume"
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?
Close #68
Signed-off-by: Alexander Chuprov a.chuprov@yadro.com
701c1aa176
to7837919a49
@ -84,3 +77,1 @@
echo "Transfer GAS to wallet $${f}" \
&& ./vendor/frostfs-adm -c frostfs-adm.yml morph refill-gas --storage-wallet $${f} --gas 10.0 \
|| die "Failed to transfer GAS to alphabet wallets"; \
@if ! ./vendor/frostfs-adm morph dump-hashes --config frostfs-adm.yml > /dev/null 2>&1; then
How about to check for presence and
exit
if exists?Diff will be shorter in this case.
dump-hashes
is not a reliable check, because we could kill adm deploy before e.g. all NNS aliases are set.init
should be idempotent, if it is not, then it is a separate bug.What error do you get if you execute
init
twice?What error do you get if you execute
init
twice?You are right, this check is not needed. The error that occurs when calling init again is:
Error: can't create transfer transaction: script failed (FAULT state) due to an error: at instruction 280 (ASSERT): ASSERT failed
Add volume for morph_chainto WIP: Add volume for morph_chain@achuprov why is it WIP?
See #72 (comment)
WIP: Add volume for morph_chainto Add volume for morph_chain7837919a49
toc6c5346870
Tested with #76