make up is not stateless anymore #94

Open
opened 2024-12-25 06:54:43 +00:00 by alexvanin · 1 comment
Owner

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 then make/up I get this error

Stage 1: transfer GAS to alphabet nodes.                                                                                                                      
Error: can't create transfer transaction: transfer failed: from=consensus(NfgHwwTi3wHAS8aFAN243C5vGbkYDpqLHP) amount=100000000 amount=1500500000000000: script
failed (FAULT state) due to an error: at instruction 280 (ASSERT): ASSERT failed                                                                              

Possible 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)

  1. Run make up
  2. Wait for a while
  3. Run make up again

Context

Regression

I think yes, but not sure.

Your Environment

Latest frostfs-dev-env after #93

## 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 then `make/up` I get this error ``` Stage 1: transfer GAS to alphabet nodes. Error: can't create transfer transaction: transfer failed: from=consensus(NfgHwwTi3wHAS8aFAN243C5vGbkYDpqLHP) amount=100000000 amount=1500500000000000: script failed (FAULT state) due to an error: at instruction 280 (ASSERT): ASSERT failed ``` ## Possible Solution Seems like an issue of frostfs-adm tool, so we can address it there. Not sure if it worth it, but lets discuss. <!--- No fix can be suggested by a QA engineer. Further solutions shall be up to developers. --> ## Steps to Reproduce (for bugs) 1. Run `make up` 2. Wait for a while 3. Run `make up` again ## Context ## Regression I think yes, but not sure. ## Your Environment Latest frostfs-dev-env after #93
alexvanin added the
bug
discussion
labels 2024-12-25 06:54:43 +00:00
fyrchik was assigned by alexvanin 2024-12-25 06:54:46 +00:00
Owner

Seems similar to TrueCloudLab/frostfs-node#1391
frostfs-adm needs to be idempotent

Seems similar to https://git.frostfs.info/TrueCloudLab/frostfs-node/issues/1391 frostfs-adm needs to be idempotent
achuprov was assigned by fyrchik 2024-12-25 08:41:31 +00:00
fyrchik removed their assignment 2024-12-25 08:41:36 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-dev-env#94
No description provided.