Open Mmdixon opened 2 months ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @amjads1 @avirishuv @Drewm3 @vaibhav-agar.
@Mmdixon - when running fetch script, I am getting the correct region
Can you please share more details on how you are creating your compute?
I used below CLI command
az ml compute create -g
@achauhan-scc I believe the compute cluster was made using the browser portal: https://ml.azure.com/compute/list/training and navigating the New modal.
Thanks @Mmdixon - Able to see the different, will provide an update.
Describe the bug
returns the wrong region in the
location
field.To Reproduce
ws.compute.get("compute_name").location
Expected behavior Expect the
location
to say eastus2 which is the region of the compute, not centralus, which is the region of the workspace. There is no other field or property to indicate the compute region iflocation
is indeed meant to only be for the workspace information.Screenshots If applicable, add screenshots to help explain your problem.
Additional context AzureML Studio does show the eastus2 region for the compute. In Azure, the Resource JSON does have the structure
but these properties are
{}
when retrieved from the SDK.