Replies: 5 comments
-
@puremjlee Sometimes Locust (load generator) can take some time to spin up. Did it eventually start? What did the logs show? Also, what size EC2 instance were you using? |
Beta Was this translation helpful? Give feedback.
-
Hi @rcastley No, It eventually didn't start. I waited about 3 hours. you could see the error at the above screenshot. EC2 instance was t2.xlarge. It was set as a default at terraform. I ran into this issue during o11y-workshop for customers (I am a splunker) |
Beta Was this translation helpful? Give feedback.
-
Are you still running into this issue? |
Beta Was this translation helpful? Give feedback.
-
I have exactly same issue. The difference is that I am using multipass on M1 Mac. |
Beta Was this translation helpful? Give feedback.
-
Multipass and the workshop is not supported on teh M1 Mac due to the Online Boutique images being |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
nginx-loadgenerator daemonset fails to deploy. The pod is CrashLoopBacckOff
To Reproduce
cd ~/workshop/k3s/nginx
kubectl create configmap nginxconfig --from-file=nginx.conf
kubectl create -f nginx-deployment.yaml
kubectl create -f locust-deployment.yaml
when you run, kubectl get pod
you could see the pod failed.
Expected behavior
nginx-loadgenerator should run without error so that attendees could try the labs.
Screenshots
Environment (please complete the following information):
I used pre-configured ec2
Beta Was this translation helpful? Give feedback.
All reactions