search

microsoft / azure-load-testing

MIT License
22 stars 2 forks source link

[BUG] Private Test wont provision #125

Closed MarekLani closed 1 year ago

MarekLani commented 1 year ago

Describe the bug I have created private test deployed to freshly created vnet with subnet dedicated for ALT with sufficient IP Range (/24 mask running only one engine). It is deployed to North Europe. VNET/subnet has no outbound/inbound restrictions set, it is setup without NSG. (Tested also with "fully opened" NSG). To eliminate problem of internal endpoint not being reachable I configured my jmx file to target publicly accessible endpoint. Test won't get provisioned. Only error message I receive is following: "There was an issue with the service. Retry again in sometime. In case the issue persists, raise a ticket with support. "

To Reproduce Steps to reproduce the behavior: See above

Expected behavior Test provisions and executes sucesfuly

Screenshots N/A

AB#1687199

Nagarjuna-Vipparthi commented 1 year ago

@MarekLani Can you please share the test run ID for us to debug the issue? Also, when you tried with public endpoint, did you select the test traffic mode as 'Public'?

MarekLani commented 1 year ago

@Nagarjuna-Vipparthi Thank you very much for your response! I tried running private test reaching private endpoint first that didn't work, so I tried publicly available endpoint as well and since my network is not restricting public outbound access, I was expecting it to work. Please can you instruct me where to find run id, since I can see only the name of the run.

Nagarjuna-Vipparthi commented 1 year ago

@MarekLani When you click on the test run and open the test results page, you will see a 'Share' option. Using this option, you will be able to copy the test run ID

image

MarekLani commented 1 year ago

I see, thank you here are the details: /testId/65b0fa68-3f6e-40b2-b7a0-204b10b3b928/ testRunId/878da84f-26f3-45a8-ad37-4533e70b8068

issacnitin commented 1 year ago

@MarekLani From our internal diagnostics, we found that your subscription have Azure Policy restrictions which prevent deployment of public IP. Deployment of Public IP, NSG and Load Balancer is required for private load testing to work. We're working on surfacing this error to end customer. Please fix the policy restrictions to continue using the feature..

MarekLani commented 1 year ago

@issacnitin thank you very much for the explanation! Closing the issue now.

gougakos commented 10 months ago

hi what is the status of this fix? we are trying to load test privately and get the issue for policy restrictions regarding the public ip. Lifting the restrisction is not an option due to security violation