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

Recreate Oraichain in Staging #452

Open
sgerogia opened this issue Feb 12, 2022 · 2 comments · May be fixed by #506
Open

Recreate Oraichain in Staging #452

sgerogia opened this issue Feb 12, 2022 · 2 comments · May be fixed by #506
Assignees

Comments

@sgerogia
Copy link
Contributor

Oraichain is in a broken state in Staging.

DoD

  • If we do not need Oraichain yet, simply delete the Nodeset
  • If we do
    • Follow the 🟩 steps if there is a good online snapshot. Otherwise revert to the 💟 steps, to sync from scratch.
    • Create a YAML manifest and commit to demeris-backend (e.g sample PR). Note no of replicas and persistence size.
    • Make sure persistence size in manifest YAML is auto-resize.
    • Provide updates in Slack
    • Ensure that the chain is removed from the Slack alerts channel and is tracing normally
    • Once complete, notify Alex Cheng and Frontend team to enable in Staging
@akc2267 akc2267 changed the title Enable or delete Oraichain in Staging Recreate Oraichain in Staging Feb 16, 2022
@Pitasi Pitasi self-assigned this Feb 22, 2022
@Pitasi Pitasi linked a pull request Feb 22, 2022 that will close this issue
@akc2267
Copy link
Contributor

akc2267 commented Feb 23, 2022

blocked on Block.Header.AppHash

I'm in contact with oraichain team and will update when they provide assistance

@akc2267
Copy link
Contributor

akc2267 commented Feb 28, 2022

confirmed with the team that the correct version is 0.40.3-alpine

there is a snapshot here: https://orai.s3.us-east-2.amazonaws.com/oraid-bk.tar.gz

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 a pull request may close this issue.

3 participants