-
Notifications
You must be signed in to change notification settings - Fork 25
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
Locust Report not uploading #122
Comments
Here is the log from the locust pod.
|
hey @QAInsights, looks like we have multiple errors here. Let's start first with Locust pod error: this value comes from variable Now, regarding the The error |
Thanks @diegomarangoni I see github action released helm version. I just tried with the helm release with the aws credentials. Pods are not getting created, it is throwing CreateContainerConfigError for all the pods. |
what command did you use to install? |
You have to specify |
FYI, I will put this on our backlog to discuss internally some ideas to improve and make it easier the installation process. |
I used
|
Seems that you are installing from the remote repository, make sure you run |
I deleted the helm installation and tried the above command. Pods are getting created. I executed a simple test in locust. Here is the error.
|
I am open to share my screen, in case if you want to take a deep-dive. @diegomarangoni |
URL stills the same:
You have to define
|
Finally no error :) But the report URL is throwing Access Denied. Reports are not there in S3 bucket.
|
Ok, seems we are doing some progress :) Can you check Locust pod logs? |
Here is the pod log.
|
Can you send the part related to report uploading? |
I dont see any upload log info.
|
Ok, Locust seems fine, let's see Kangal Proxy logs |
Can you double-check if the user you are using have write permission to this bucket? |
Could you please share the sample bucket policy? I have enabled public access as of now. |
Got some error in the proxy.
|
This logs have to relation with the Try using the AWS builtin policy |
Sure, so how can I set the config like bucket name and region after the pods are created. Do I have edit the config map? |
Yes, you can edit the config map by using: |
|
|
Yes, I have changed to us-east-2 in the URL, still the access is denied. |
This is my S3 bucket policy
|
hey @QAInsights, I just did a test here and it's working fine I can see the file on the bucket I've just created.
The steps I did:
|
I have followed the exact steps in AWS. Created a new user and added S3 full access. Configured the key and secret in the secrets. Access is denied even for GET report.
|
I can't reproduce this issue. Steps I did:
helm install \
--set environment=dev \
--set configMap.AWS_DEFAULT_REGION=eu-west-1 \
--set configMap.AWS_ENDPOINT_URL=s3.eu-west-1.amazonaws.com \
--set configMap.AWS_BUCKET_NAME=test-kangal \
--set secrets.AWS_ACCESS_KEY_ID="XXXXXXXXXXXXXXXXXXXX" \
--set secrets.AWS_SECRET_ACCESS_KEY="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
--set controller.env.KANGAL_PROXY_URL="http://kangal-proxy-k8s.default.svc.cluster.local" \
kangal kangal/kangal
kubectl port-forward svc/kangal-proxy-k8s 8080:80
http --form POST http://localhost:8080/load-test \
distributedPods=1 \
testFile@kangal-loadtest.py \
type=Locust \
duration=1m
|
Many thanks. I used |
@diegomarangoni Please check my blog post :) https://qainsights.com/performance-testing-in-kubernetes-using-kangal/ |
Glad it works @QAInsights!
Thanks for sharing and for contributing to our community :) |
@diegomarangoni I have installed 1.1.11 as you mentioned in my previous issue. After spinning up the pods, when I try to upload a sample file, I am getting below error.
The text was updated successfully, but these errors were encountered: