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_lb_backend_address_pool_address - fix acctest failure #24265

Merged
merged 2 commits into from
Jan 2, 2024

Conversation

sinbai
Copy link
Contributor

@sinbai sinbai commented Dec 18, 2023

Fix the following acctest failure.
image

Test Result:
PASS: TestAccBackendAddressPoolAddress_globalLbUpdate (341.34s)

Copy link
Member

@catriona-m catriona-m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @sinbai, I ran the tests in team city and it looks like there is still a failure occuring:

------- Stdout: -------
=== RUN   TestAccBackendAddressPoolAddress_globalLbUpdate
=== PAUSE TestAccBackendAddressPoolAddress_globalLbUpdate
=== CONT  TestAccBackendAddressPoolAddress_globalLbUpdate
    testcase.go:113: Step 1/4 error: Error running apply: exit status 1
        Error: waiting for creation/update of Public Ip Address: (Name "acctestpip-231219135001958725-cr" / Resource Group "acctestRG-231219135001958725"): Code="GlobalVipAllocationFailedWithVipRangeNotFound" Message="No matching cross-region PublicIPAddress range could be found. Please make sure the location of the cross-region PublicIPAddress is in the list of supported home regions. For supported home regions visit aka.ms/homeregionForGLB" Details=[]
          with azurerm_public_ip.backend-ip-cr,
          on terraform_plugin_test.tf line 68, in resource "azurerm_public_ip" "backend-ip-cr":
          68: resource "azurerm_public_ip" "backend-ip-cr" {
--- FAIL: TestAccBackendAddressPoolAddress_globalLbUpdate (202.13s)
FAIL

@sinbai
Copy link
Contributor Author

sinbai commented Dec 21, 2023

GlobalVipAllocationFailedWithVipRangeNotFound

Hi @sinbai, I ran the tests in team city and it looks like there is still a failure occuring:

------- Stdout: -------
=== RUN   TestAccBackendAddressPoolAddress_globalLbUpdate
=== PAUSE TestAccBackendAddressPoolAddress_globalLbUpdate
=== CONT  TestAccBackendAddressPoolAddress_globalLbUpdate
    testcase.go:113: Step 1/4 error: Error running apply: exit status 1
        Error: waiting for creation/update of Public Ip Address: (Name "acctestpip-231219135001958725-cr" / Resource Group "acctestRG-231219135001958725"): Code="GlobalVipAllocationFailedWithVipRangeNotFound" Message="No matching cross-region PublicIPAddress range could be found. Please make sure the location of the cross-region PublicIPAddress is in the list of supported home regions. For supported home regions visit aka.ms/homeregionForGLB" Details=[]
          with azurerm_public_ip.backend-ip-cr,
          on terraform_plugin_test.tf line 68, in resource "azurerm_public_ip" "backend-ip-cr":
          68: resource "azurerm_public_ip" "backend-ip-cr" {
--- FAIL: TestAccBackendAddressPoolAddress_globalLbUpdate (202.13s)
FAIL

Hi @catriona-m thanks for your time. After resetting the test, it passed in team city, see the result as follows.
image

Per the description "You can only deploy your cross-region load balancer or Public IP in Global tier in one of the listed Home regions " and run setting as shown below, it seems that the failure may occur in westus2 because westus2 is not included in the home regions. Therefore, I updated the settings to specify the regions to run the loadbalancer in westeurope, eastus2, and westus to fix the above failure. Could you please take another look?

image

Copy link
Member

@catriona-m catriona-m left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @sinbai LGTM!

@catriona-m catriona-m merged commit fc5b078 into hashicorp:main Jan 2, 2024
30 checks passed
@github-actions github-actions bot added this to the v3.86.0 milestone Jan 2, 2024
@sinbai sinbai deleted the loadbalance/fix-acctest branch March 28, 2024 02:42
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants