aws-samples / aws-samples/eks-workshop-v2
[Bug]: fastpaths/developer consisently times out.
- Dominant language
- HCL
- Stars
- 626
- Forks
- 613
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 9
Description
### Installation method
Own AWS account
### What happened?
Going through the EKS Workshop at: https://www.eksworkshop.com/docs/fastpaths/developer and I'm trying to do the first step which is running `prepare-environment fastpaths/developer` , however it consistently times out. Log file attached below. Since i can't figure out where this code actually lives / what its doing, the net result is that the "developer essentials" lab is impossible to start/complete.
```
ec2-user:~/.bashrc.d:$ prepare-environment fastpaths/developer
Welcome to
(EKS Workshop Graphic)
Hands-on labs for Amazon Elastic Kubernetes Service
🚀 We're preparing your environment for the next lab, sit tight!
📦 Refreshing copy of workshop repository from GitHub...
📦 Deploying base application...
🔧 First time setup: provisioning fastpaths infrastructure (this only runs once)...
⏳ Waiting for application to become ready...
error: timed out waiting for the condition
🚨 An error occurred, please contact your workshop proctor or raise an issue at https://github.com/aws-samples/eks-workshop-v2/issues
The full log can be found here: /eks-workshop/logs/action-1787252858.log
Execution time: 193 seconds
ec2-user:~/.bashrc.d:$
```
I tried running through it multiple times just in case it was a one-off issue, however it consistently times out with the same error.
### What did you expect to happen?
The command would complete successfully, whatever that may entail
### How can we reproduce it?
Not sure if necessary to reproduce, but I ran through the "Getting Started" lab first and then moved onto the Developer Essentials lab with the same environment, maybe something is conflicting between the two?
If the above doesn't matter, then just run `prepare-environment fastpaths/developer` and let it try to complete, it won't.
### Anything else we need to know?
It would be nice if the timeout was configurable so I could at least try to give it more time to complete. Log attached.
[action-1787251666.log](https://github.com/user-attachments/files/31277965/action-1787251666.log)
### EKS version
1.33
Contributor guide
Research direction
Start by running `prepare-environment fastpaths/developer` in the EKS Workshop environment and inspect the attached action log, `/eks-workshop/logs/action-1787252858.log`. Trace the first-time fastpaths infrastructure setup and readiness wait; done means the command completes without timing out and the Developer Essentials lab can start.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100