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

[WIP] data/data/azure/vnet: force dependencies #3251

Closed

Conversation

jhixson74
Copy link
Member

Force the subnet resource to depend on the virtual network. This eliminates the
dreaded "AnotherOperationInProgress" error.

https://bugzilla.redhat.com/show_bug.cgi?id=1809346

@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Mar 5, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign jhixson74
You can assign the PR to them by writing /assign @jhixson74 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@@ -17,6 +17,8 @@ resource "azurerm_subnet" "master_subnet" {
] : cidr.value if cidr.include]
virtual_network_name = local.virtual_network
Copy link
Contributor

Choose a reason for hiding this comment

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

Since we are using the output of the created resource, we already depend on it... why do we need the explicit depend?

Copy link
Member Author

@jhixson74 jhixson74 Mar 6, 2020

Choose a reason for hiding this comment

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

I agree that you would /think/ that would handle the issue. Some googling around says otherwise. I agree this is a crude hack, which is why I've labeled the PR a WIP. Nobody seems to know for sure if this is a dependency problem within terraform, or a parallelism problem with Azure. One thing for sure, is that if you set parallelism=1, then all problems go away ;-) Here are some issues on github for reference:

hashicorp/terraform-provider-azurerm#3780
hashicorp/terraform-provider-azurerm#4285
hashicorp/terraform-provider-azurerm#3673

Copy link
Contributor

Choose a reason for hiding this comment

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

+1

Copy link
Contributor

Choose a reason for hiding this comment

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

We should also try to fix this upstream to make sure we don't need this depends on later

@abhinavdahiya
Copy link
Contributor

/test e2e-azure

2 similar comments
@abhinavdahiya
Copy link
Contributor

/test e2e-azure

@abhinavdahiya
Copy link
Contributor

/test e2e-azure

@abhinavdahiya
Copy link
Contributor

/retest

@abhinavdahiya
Copy link
Contributor

/test e2e-azure

Force the subnet resource to depend on the virtual network. This eliminates the
dreaded "AnotherOperationInProgress" error.

https://bugzilla.redhat.com/show_bug.cgi?id=1809346
@jhixson74
Copy link
Member Author

/test e2e-azure

@ironcladlou
Copy link
Contributor

/retest

1 similar comment
@ironcladlou
Copy link
Contributor

/retest

@abhinavdahiya
Copy link
Contributor

This error is no longer happening in the CI or when creating clusters.. seems like azure fixed something in the back end.

So maybe we don't need this PR..

@openshift-ci-robot
Copy link
Contributor

@jhixson74: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/tf-fmt 11a3813 link /test tf-fmt
ci/prow/e2e-aws-fips 11a3813 link /test e2e-aws-fips
ci/prow/e2e-aws-scaleup-rhel7 11a3813 link /test e2e-aws-scaleup-rhel7
ci/prow/e2e-libvirt 11a3813 link /test e2e-libvirt

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jhixson74 jhixson74 closed this Mar 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants