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

error with BICEP Deployment of Recovery services Vault #2212

Open
GBCSIM1 opened this issue Jul 2, 2024 · 0 comments
Open

error with BICEP Deployment of Recovery services Vault #2212

GBCSIM1 opened this issue Jul 2, 2024 · 0 comments

Comments

@GBCSIM1
Copy link

GBCSIM1 commented Jul 2, 2024

Bicep CLI version 0.28.1

Describe the bug
When redeploying a Recovery Services Vault with Private Endpoint, This already exists with VM's using the Backup feature.
I am getting the error:

[{"code":"NameOfExistingPrivateEndpointNicCannotBeChanged","message":"Private Endpoint /subscriptions/xxxxx/resourceGroups/xxxx/providers/Microsoft.Network/privateEndpoints/xxxx-backup-rsv-pep contains existing NIC name xxx-backup-rsv-pep-nic which does not match request's custom network interface name . Updating the name of existing nic not allowed.","details":

however from other environments using the exact same code the NIC has a GUI at the end of the naming convention:

xxxy-backup-rsv-pep.nic.467cef69-ed43-4cbc-9d79-981a3984d293
this i can see is the only issue that i can see as the specific NIC is: [xxxx-backup-rsv-pep-nic]

To Reproduce
Running Pipeline and this still has the same problem.

Additional context
Add any other context about the problem here.

the Original RSV was deployed using the same Pipeline. Please can someone help me?

@anthony-c-martin anthony-c-martin transferred this issue from Azure/bicep Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Development

No branches or pull requests

1 participant