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.

Sign up for GitHub

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

Jump to bottom

Netapp.Volume API doesn't identify what we set in previous run for the SnapshotID property #17834

Closed
neil-yechenwei opened this issue Feb 14, 2022 · 1 comment
Closed

Netapp.Volume API doesn't identify what we set in previous run for the SnapshotID property #17834

neil-yechenwei opened this issue Feb 14, 2022 · 1 comment
Assignees
@paulomarquesc
Labels
NetApp 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

@neil-yechenwei
Copy link

neil-yechenwei commented Feb 14, 2022 •
edited
Loading

After tested, I found Netapp Volume can be created successfully with the SnapshotID. Then I tried to only update tags of this resource but it failed and threw below error message. Seems Netapp Volume API doesn't identify what we set in previous run for the SnapshotID property even if I didn't change this property. I assume api should know what we set in previous run for the SnapshotID property to identify whether this property is changed. Does it make sense?

Error message:

netapp.VolumesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="VolumeReadOnlyPropertyCanNotBeChanged" Message="The volume's snapshotId property is not allowed to be updated. Please check that snapshotId is not part of the update request or isn't being changed from the current value."
@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Feb 14, 2022
@neil-yechenwei neil-yechenwei mentioned this issue Feb 14, 2022
Closed
@ankhyk ankhyk added NetApp 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. labels Feb 15, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Feb 15, 2022
@paulomarquesc
Copy link

I'm working on this, it is not an issue with the API or SDK, this will be fixed on Terraform ANF module.

@paulomarquesc paulomarquesc self-assigned this Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@paulomarquesc paulomarquesc

Labels
NetApp 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
Milestone
No milestone
Development

No branches or pull requests
3 participants
@paulomarquesc @neil-yechenwei @ankhyk