Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Kava Protonet Data Reset Chain CI #2025

Draft
wants to merge 57 commits into
base: master
Choose a base branch
from

Conversation

sesheffield
Copy link
Contributor

@sesheffield sesheffield commented Sep 20, 2024

description

  • handle protonet flow with new ansible playbook for reset, restart, seed
  • Using different tags and using autoscaling group for ordering (want the validator to be reset first then api node)
    • Added autoscaling groups to be ran for kava-node-updater since new infra doesn't use KavaChainId and uses ChainId and this is to ensure we reset the validator node first then any api nodes afterwards

kava protonet genesis contains all the necessary fields set

This flow will be removed eventually for testnetV2

Description

Checklist

  • Changelog has been updated as necessary.

@sesheffield sesheffield changed the title feat: handle protonet flow with new ansible playbook for reset and di… feat: Kava Protonet Data Reset Chain CI Sep 20, 2024
@sesheffield sesheffield marked this pull request as ready for review September 23, 2024 21:42
@drklee3 drklee3 mentioned this pull request Sep 24, 2024
1 task
@sesheffield sesheffield changed the base branch from shef-protonet-validator-network to master September 24, 2024 22:34
Copy link
Member

@pirtleshell pirtleshell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does a rebase onto master resolve the failing CI?

we probably shouldn't be updating kvtool in this PR

.github/workflows/cd-reset-internal-testnet.yml Outdated Show resolved Hide resolved
@sesheffield
Copy link
Contributor Author

does a rebase onto master resolve the failing CI?

we probably shouldn't be updating kvtool in this PR

Nick's branch nd-implement-basic-precompile-calling updates the kvtool submodule commit to the 86012 hash.

which then causes issues for ansible with:

skipping: [localhost] TASK [chain-binaries : checkout chain repository] ******************************
2024-09-24T23:08:39.185Z
fatal: [localhost]: FAILED! => 
{
    "changed": false,
    "cmd": [
        "/usr/bin/git",
        "fetch",
        "--tags",
        "--force",
        "origin"
    ],
    "msg": "Failed to download remote objects and refs:  From https://github.com/kava-labs/kava\n   ac1bb5c9..69964888  dl-eip712-domainsep-tests -> origin/dl-eip712-domainsep-tests\n * [new branch]        dl-usdt-gas            -> origin/dl-usdt-gas\n * [new branch]        lbayas/genesis-updates -> origin/lbayas/genesis-updates\n   8ac4c5d0..ee4fc56f  master                 -> origin/master\n * [new branch]        nd-implement-basic-precompile-calling -> origin/nd-implement-basic-precompile-calling\n * [new branch]        shef-protonet-validator-network -> origin/shef-protonet-validator-network\n * [new branch]        shef-protonet-validator-network-ci -> origin/shef-protonet-validator-network-ci\n * [new branch]        shef-protonet-validator-network-ci-v2 -> origin/shef-protonet-validator-network-ci-v2\n   50418c2e..e2217257  ss-protonet-tester     -> origin/ss-protonet-tester\nFetching submodule tests/e2e/kvtool\nfatal: remote error: upload-pack: not our ref 86012e65f20488fa89d509c0183ac259ce55ffca\nErrors during submodule fetch:\n\ttests/e2e/kvtool\n"
}

but you're right, ideally we don't want any kvtool changes here, but this was the branch I needed to test since it's not in master yet.

@sesheffield sesheffield marked this pull request as draft September 26, 2024 18:38
@sesheffield
Copy link
Contributor Author

setting to draft to triple check quality

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants