Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List Registries API Returns Duplicated Resources #31173

Closed
6 tasks
jojoochen opened this issue Sep 20, 2024 · 9 comments
Closed
6 tasks

List Registries API Returns Duplicated Resources #31173

jojoochen opened this issue Sep 20, 2024 · 9 comments
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@jojoochen
Copy link

jojoochen commented Sep 20, 2024

  • Package Name: arm-machinelearning
  • Package Version: 3.0.0
  • Operating system:MacOS Sonoma 14.5
  • nodejs
    • version: 18.19.0
  • browser
    • name/version:
  • typescript
    • version:
  • Is the bug related to documentation in

Describe the bug
When retrieving a list of resources using the Azure API(https://learn.microsoft.com/en-us/rest/api/azureml/registries/list-by-subscription?view=rest-azureml-2024-04-01&tabs=HTTP#code-try-0), the number of returned resources is multiplied by the number of regions in which they are deployed. This results in duplicate entries for each unique resource across all regions.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy multiple registries across distinct regions.
  2. Use the API to list the deployed resources (either via CLI or SDK).
  3. Example:
  • With 6 registries deployed across 5 regions, the API returned 30 items, with each registry duplicated 5 times.
  • Similarly, deploying 5 registries across 4 distinct regions (i.e. 2 of them in the same region), returned 20 items, again duplicating the resources based on region count.

Expected behavior
The API should return a single entry per unique resource, regardless of how many regions it is deployed in.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
This is what we've discovered so far, though we are unsure if there may be some underlying mechanism that we're unaware of. We would appreciate your assistance in clarifying this issue.

@jojoochen jojoochen changed the title List Registries API Returns Duplicated Resources Based on Region Count List Registries API Returns Duplicated Resources Sep 20, 2024
@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Sep 20, 2024
@jeremymeng jeremymeng added Client This issue points to a problem in the data-plane of the library. Mgmt This issue is related to a management-plane library. and removed Client This issue points to a problem in the data-plane of the library. labels Sep 20, 2024
@github-actions github-actions bot removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 20, 2024
@kazrael2119
Copy link
Contributor

will check

@kazrael2119
Copy link
Contributor

kazrael2119 commented Sep 23, 2024

@jojoochen ,could you share more screenshots or details?
If I create 2 Registries "A" and "B", and the Primary regions in A is westus and it's additional regions are eastus and eastus2euap, the Primary regions in B is centralus and it's additional regions are eastus and eastus2euap
and then I call the list api, the result will be 4 as there's 4 regions are deployed Registries ?

@kazrael2119
Copy link
Contributor

kazrael2119 commented Sep 23, 2024

now in my resource group, I have one registry with a primary region and two additional regions. Then the result after calling the list api are 2. Does the regions in

With 6 registries deployed across 5 regions, the API returned 30 items, with each registry duplicated 5 times.
Similarly, deploying 5 registries across 4 distinct regions (i.e. 2 of them in the same region), returned 20 items, again duplicating the resources based on region count.

mean the additional regions?

@qiaozha qiaozha added the needs-author-feedback Workflow: More information is needed from author to address the issue. label Sep 25, 2024
Copy link

Hi @jojoochen. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

@jojoochen
Copy link
Author

Thank you for your response and for looking into this issue!

What I meant by region does not refer to the additional regions.

Here are the steps to reproduce the issue:

  1. Using my current resources, I first created five registries, with their locations spread across four different regions—two of them are in the same region.
image
  1. Then, I ran the API command: az ml registry list. (https://learn.microsoft.com/en-us/cli/azure/ml/registry?view=azure-cli-latest#code-try-5)
image
  1. As a result, each registry was listed four times, returning identical entries for each.
image

Therefore, the total count was 5 registries * 4 identical entries = 20 resources.

image

I appreciate your help in resolving this and look forward to your insights. Thanks again!

@github-actions github-actions bot added needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team and removed needs-author-feedback Workflow: More information is needed from author to address the issue. labels Sep 25, 2024
@kazrael2119
Copy link
Contributor

I can repro this issue with using Rest Api, so I think this should be a service backend issue,
Add Service Attention for awareness

@kazrael2119 kazrael2119 added the Service Attention Workflow: This issue is responsible by Azure service team. label Sep 29, 2024
@jojoochen
Copy link
Author

Hi @kazrael2119, thanks for your previous response regarding the issue. Since it's been a week, I wanted to kindly follow up and check on the current status.
Is there any further update on the resolution of this backend issue, or is there anything we need to do on our end.
Thank you so much!

@kazrael2119
Copy link
Contributor

offline ping the api owner , and they logged this issue in their board https://dev.azure.com/msdata/Vienna/_workitems/edit/3544286

@qiaozha
Copy link
Member

qiaozha commented Oct 18, 2024

close it as we will use the above ado link to track this.

@qiaozha qiaozha closed this as completed Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

4 participants