search cancel

Blazemeter Test Executed in the Wrong Region

book

Article ID: 212991

calendar_today

Updated On:

Products

BlazeMeter

Issue/Introduction

The report indicates that test was executed in US-East. The following files with the artifacts directory indicate that the test was actually executed in the central location:

─ grep location * 2>/dev/null

acuvue_bzt.yml:    locations:

bzt.log:[2021-04-13 19:31:51,983 DEBUG Engine] Module config: cloud {'class': 'bzt.modules.blazemeter.CloudProvisioning', 'default-location': 'us-central1-a', 'project': 'Magento - MyAcuvue', 'test': '04-14 Baseline'}

cloud.json:   "default-location": "us-central1-a",

cloud.json:   "locations": {

cloud.yml:  locations:

cloud.yml:    default-location: us-central1-a

effective.json:   "default-location": "us-central1-a",

effective.json:  "locations": {

effective.json:     "dump-locations": true

effective.json:   "locations": {

effective.yml:  locations:

effective.yml:        dump-locations: true

effective.yml:  locations:

effective.yml:    default-location: us-central1-a

Environment

Release : SAAS

Component : BLAZEMETER PERFORMANCE TESTING

Cause

Working as designed.

Resolution

This test was run locally but the test actually runs in the cloud.  The bzt.log snippet you provided shows a time of bzt.log:[2021-04-13 19:31:51,983 DEBUG Engine]m but the bzt.log from the test run shows [2021-04-13 23:33:34,791 DEBUG Engine]. And the region shows 'region': 'us-east-1'.  There is no mention of us-central1-a in the test run bzt.log.

If you look at the taurus.yml, in the execution section it says to run in location us-east-1, which it did.  If you go down to the modules section, default-location in the cloud is set to us-central1-a.  This is stating if you do not set a location in your configuration, it will default to location us-central1-a.

Attachments