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

azurerm_site_recovery_network_mapping fails with "Error checking for presence of existing site recovery network mapping network-primary2secondary" #6026

Closed
martenbohlin opened this issue Mar 7, 2020 · 4 comments

Comments

@martenbohlin
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform v0.12.17

  • provider.azurerm v2.0.0

Affected Resource(s)

  • azurerm_site_recovery_network_mapping

Terraform Configuration Files

This problem is detected by the integration. test TestAccAzureRMSiteRecoveryNetworkMapping_basic

Debug Output

Panic Output

Expected Behavior

A network mapping should have been created.

Actual Behavior

The folllowing error:
--- FAIL: TestAccAzureRMSiteRecoveryNetworkMapping_basic (501.84s)
testing.go:640: Step 0 error: errors during apply:

    Error: Error checking for presence of existing site recovery network mapping mapping-200307180752678515 (vault acctest-vault-200307180752678515): siterecovery.ReplicationNetworkMappingsClient#Get: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="BadRequest" Message="An invalid parameter NetworkMappingName was passed." Details=[{"activityId":"e3c8c514-7a1b-aaac-5e45-ee6cacf41c3a","clientRequestId":"66625d9f-10cb-4fb9-92d7-665e3688fb32","code":"InvalidParameter","message":"An invalid parameter NetworkMappingName was passed.","possibleCauses":"Parameter value is not correct for this action.","recommendedAction":"Correct the parameter value and retry the last action. If the issue persists, contact Support."}]

      on /var/folders/7s/t24np7dn2w5_rg6nhsdjpgr00000gp/T/tf-test089678882/main.tf line 49:
      (source code not available)

Steps to Reproduce

make testacc TESTARGS='-run=TestAccAzureRMSiteRecoveryNetworkMapping'

Important Factoids

References

  • #0000
@wenesak
Copy link

wenesak commented Mar 22, 2020

same here same error, anybody knows of a work around?

martenbohlin added a commit to Avinode/terraform-provider-azurerm that referenced this issue May 3, 2020
tombuildsstuff added a commit that referenced this issue May 6, 2020
…r-issue-6026

Workaround for strange response code in recovery services network mappings API. Fixes issue #6026
@tombuildsstuff tombuildsstuff added this to the v2.9.0 milestone May 6, 2020
@tombuildsstuff
Copy link
Member

Fixed via #6747

@ghost
Copy link

ghost commented May 8, 2020

This has been released in version 2.9.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.9.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Jun 5, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@hashicorp hashicorp locked and limited conversation to collaborators Jun 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants