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

Attempting to tag an existing azure public ip of an instance within a vm scaleset gives a resource not found #23395

Open
neville-cb opened this issue Sep 3, 2024 · 5 comments
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 Network 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

@neville-cb
Copy link

neville-cb commented Sep 3, 2024

Bug Report

  • import path of package in question, e.g. .../services/compute/mgmt/2018-06-01/compute
    "github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/network/armnetwork/v5"

  • SDK version e.g. master, latest, 18.1.0

    • Specify the exact commit if possible; one way to get this is the REVISION
      column output by go list -m <module>, for example go list -m github.com/Azure/azure-sdk-for-go/sdk/azcore.
  • output of go version
    github.com/Azure/azure-sdk-for-go/sdk/azcore v1.14.0
    github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/network/armnetwork/v5 v5.2.0

  • What happened?
    I deployed a VM scaleset with 1 instance that has both the public and private IPs created.
    On calling go sdk function - func (client *PublicIPAddressesClient) UpdateTags(ctx context.Context, resourceGroupName string, publicIPAddressName string, parameters TagsObject, options *PublicIPAddressesClientUpdateTagsOptions) (PublicIPAddressesClientUpdateTagsResponse, error) ,it gives the following error
RESPONSE 404: 404 Not Found\nERROR CODE: ResourceNotFound 
{
 "error": {
  "code": "ResourceNotFound", 
  "message": "The Resource 'Microsoft.Network/publicIPAddresses/<identifier>' under resource group '<identifier>' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix"
 }
}

On checking the fully qualified namespace of the public IP created for the instance within the namespace, it looks like the SDK call is looking for the public IP address in a different namespace and the public IP for the instance in the VM scaleset is created in a different namespace.

/subscriptions/<identifier>/resourceGroups/<identifier>/providers/Microsoft.Compute/virtualMachineScaleSets/<identifier>/virtualMachines/0/networkInterfaces/<identifier>/ipConfigurations/<identifier>/publicIPAddresses/<identifier>

Not sure if a wrong SDK method is called here or is this a bug?

  • What did you expect or want to happen?
    I expected the public IP belonging to the instance in the VM scaleset to be updated with all the tags i provided.

  • How can we reproduce it?
    Using the azure golang sdk.
    Please deploy a VM scaleset with 1 instance and check the public IP is assigned.
    Call the method above to update the tags of the public IP address.
    The tag updation fails with the error mentioned above.

  • Anything we should know about your environment.
    N/A

@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 3, 2024
@jhendrixMSFT jhendrixMSFT added Network and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Sep 9, 2024
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Sep 9, 2024
@jhendrixMSFT jhendrixMSFT added the Mgmt This issue is related to a management-plane library. label Sep 9, 2024
@ArcturusZhang
Copy link
Member

Hi @neville-cb thanks for this issue
I think the public ip address resource you created with your vmss is not the same resource in the network RP therefore it cannot be managed by the PublicIPAddressClient in armnetwork package.
And also that public ip resource created by vmss does not have a tag to assign.

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

Hi @neville-cb. 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.

@github-actions github-actions bot removed the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Sep 11, 2024
@neville-cb
Copy link
Author

neville-cb commented Sep 11, 2024

Thanks for getting back @ArcturusZhang

And also that public ip resource created by vmss does not have a tag to assign.

Do you mean tagging a public IP belonging to an instance within a VMSS is not yet supported? Because i attempted to tag it via the Azure UI portal by clicking on Add Tags and it threw some error message. Refer screenshot below

image

And if it's not yet supported then are there any plans to allow doing that in the future?

@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 11, 2024
@ArcturusZhang
Copy link
Member

ArcturusZhang commented Sep 13, 2024

Hi @neville-cb I believe the service API does not support it yet, I do not know if there is any plan for this on VMSS service teams.
If they added the API in the future, we could support it instantly in our SDK - but we are not able to do that if the API does not support it.
As for the plans on service teams, maybe you could try to create support tickets on azure portal directly to VMSS team to ask

@tadelesh tadelesh added the Service Attention Workflow: This issue is responsible by Azure service team. label Sep 18, 2024
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @aznetsuppgithub.

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 Network 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

5 participants