search

microsoft / azure-load-testing

MIT License
22 stars 2 forks source link

[BUG] Tests stuck in Provisioning state #56

Closed alessiofilippin closed 2 years ago

alessiofilippin commented 2 years ago

Describe the bug After creating and start a test. The status remain stuck in Provisioning indefinitely.

To Reproduce

  1. Go to tests part in the Azure Load Testing Resource (create in region North Europe)
  2. Run a test.
  3. See status.

Expected behavior test should start.

Screenshots image

Additional context

Tests doesn't seem to get always stuck in that state. But it's happening often in the last 2 days.

we tried with different types of JMeters tests, but we got the same result

Is there a way to check if the status of Azure Load testing is healthy somehow?

Sachid26 commented 2 years ago

@alessiofilippin .. Thank you for reporting the issue. Adding @issacnitin from our team

alessiofilippin commented 2 years ago

JFYI: I left the tests running in "provisioning" over the night - I found all them failed this morning.

let me know if I can help somehow :) - thanks

image

alessiofilippin commented 2 years ago

I also re-run some of them this morning.

image

They seem in executing state .. this looks like being an intermittent issue then.

jwyza-pi commented 2 years ago

I've seen this as well, sometimes it'll just sit in provisioning for hours then suddenly start running or fail.

abranj1219 commented 2 years ago

@jwyza-pi and @alessiofilippin I hope you are not seeing these issues anymore. Please confirm. We will keep this ticket open for few days to confirm the behavior.

jwyza-pi commented 2 years ago

I'll keep an eye on it. I haven't seen it happen today or yesterday, but definitely was happening a fair bit last week.

jwyza-pi commented 2 years ago

I have not seen this occur again, so from my perspective, we're good.

alessiofilippin commented 2 years ago

Same from my side - it stopped after a couple of days

DanielLarsenNZ commented 2 years ago

I had two stuck in provisioning today (East US 2)

abranj1219 commented 2 years ago

We are looking into this and will get back soon!

shilamontubig commented 2 years ago

Same here but I was using Australia East region.

abranj1219 commented 2 years ago

It has been fixed now. We'll keep this open for couple of more days to confirm the consistent behavior

issacnitin commented 2 years ago

Closing the issue as no new reports since March

ejerskov commented 2 years ago

This is still happening.

hkarthik7 commented 1 year ago

Hiya, This issue still persists but intermittently. I had created 2 resources and tried creating the test cases, in one resource I can create the test cases successfully however not in the second resource.

issacnitin commented 1 year ago

Hiya, This issue still persists but intermittently. I had created 2 resources and tried creating the test cases, in one resource I can create the test cases successfully however not in the second resource.

could you share your test run id

hkarthik7 commented 1 year ago

Here is the test run id - 65cbeb5c-83de-4279-bd6a-b8378f77546e

issacnitin commented 1 year ago

@hkarthik7 the test runs failed while configuring, out of 3 VMs you provisioned, only one was configured successfully, we saw the VM restarted in between configuring as well, we'd like to check your JMX and other input configuration to determine the root cause.. please use azure support to raise a ticket on us

hkarthik7 commented 1 year ago

Cheers, will do, thank you.

jdubagilisys commented 9 months ago

Hi, currently experiencing this issue when trying to run tests using private test traffic mode (UK South)