search

microsoft / azure-load-testing

MIT License
22 stars 2 forks source link

[BUG] Unable to modify a existing load-test to target private endpoint. #137

Open mithunshanbhag opened 1 year ago

mithunshanbhag commented 1 year ago

Describe the bug

  1. First, I had created a "quick test" to target a public endpoint. That ran successfully.
  2. Then, I edited the test to target a valid private endpoint.
    • Modified the domain and path accordingly.
    • Changed test traffic mode to private and specified a valid vnet + subnet.
  3. Now if I run this altered test, it fails (returns 404s).
  4. As you can see the private API endpoint is indeed accessible from a VM (in the same VNET). See last screenshot.

Additional Details

  1. Private API Endpoint: https://contoso-traders-intcartsctprod.thankfulglacier-49f2b35e.eastus.azurecontainerapps.io/v1/ShoppingCart/loadtest
  2. Azure Subscription ID: d0c33f09-f408-4bb7-935e-c53c50358a38
  3. Resource group name: contoso-traders-rg
  4. Region: East US
  5. Load Test Resource Name: contoso-traders-loadtestctprod

Relevant log files

Screenshots

Screenshot 2023-01-20 200406

Screenshot 2023-01-20 191229

image

CC: @MarcusFelling

AB#1728177

Nagarjuna-Vipparthi commented 1 year ago

@mithunshanbhag Thank you for reaching out. We will look into the issue and get back to you. We will reach out to you if we need any additional information.

mithunshanbhag commented 1 year ago

Ok, the good news is that this issue doesn't seem to repro anymore. I just re-tried the scenario.

Test runs (created & executed entirely via github actions)

Test runs (manually created, first targeting public endpoint, then modified to target private endpoint)

Would just like the product team to revalidate this scenario before we can close this issue.