-
Notifications
You must be signed in to change notification settings - Fork 4
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
deployment's gone from the provider but not the chain / unreserving unmanaged order #107
Comments
can't confirm the reproducerHurricane provider has 31 active leases deployed much earlier than the RPC node's earliest block height
cause can't be determined based on the logsCan't find the cause but can see that the deployment manifest wasn't found. It is possible that the deployment was accepted but the manifest file has never been sent. Or there might have been a different issue where the manifest was removed.
|
The deployment
11648596
's gone from the provider on 12th of July 2023; In the chain it was activedseq
11648596
dseq owner
akash1c5xu5xmauq4zkam0t4hlddvwk327ny20y68ddt
provider
akash1pl9sm32kt0xmcyfwjsf9guu9f93yf8p6k7grtn
Versions
network: mainnet-2
provider-services
0.2.1
akash
v0.22.8
(the RPC his provider is using)Provider Logs
Checking the
11648596
dseq:11648596
dseq is only visible against the RPC that has history when that dseq was createdChain view for
11648596
dseqPotential reason
I'm thinking if that could do anything with that the RPC's history begins with the
11754001
height whereas dseq11648596
was deployed at11648598
height .. https://www.mintscan.io/akash/txs/ABC0DD6AF3F477155A1F177CD0323DB613C95962789E1F7BF92E2B73E259146DNext steps
Find the reproducer
To reproduce one would need to follow this path:
akash-provider
service and see what happens to that deployment from the step 2.Refs
#17
The text was updated successfully, but these errors were encountered: