make up
is not stateless anymore #94
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-dev-env#94
Loading…
Add table
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?
Expected Behavior
As far as I remember, frostfs-adm and
make up
command were designed to be stateless, so they can be restarted as many times as user wants and it just skips some steps.Current Behavior
I've noticed that sometimes when I run
make up/basic
and thenmake/up
I get this errorPossible Solution
Seems like an issue of frostfs-adm tool, so we can address it there. Not sure if it worth it, but lets discuss.
Steps to Reproduce (for bugs)
make up
make up
againContext
Regression
I think yes, but not sure.
Your Environment
Latest frostfs-dev-env after #93
Seems similar to TrueCloudLab/frostfs-node#1391
frostfs-adm needs to be idempotent