akash-network / akash-network/console
Automatic installation of akash console does not work
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 264
- Forks
- 94
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 297
Description
All processes are running on a clean ubuntu 24 system, when automatically configured, the Check Akash Node Readiness process returns the following error after 10 minutes
{"status":"Pending"}
Akash node pod not ready yet, waiting 10 seconds before next check
{"status":"Pending"}
Akash node pod not ready yet, waiting 10 seconds before next check
{"status":"Pending"}
Akash node pod not ready yet, waiting 10 seconds before next check
Akash node pod did not become ready within 600 seconds
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the automatic configuration on a clean Ubuntu 24 system and start with the Check Akash Node Readiness process. Investigate why the Akash node pod remains Pending for 600 seconds; done means the pod becomes ready and the readiness check completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100