Bug 2033256
| Summary: | openshift-installer intermittent failure on AWS with "Error: Provider produced inconsistent result after apply" when creating the module.vpc.aws_route_table.private_routes resource | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Greg Sheremeta <gshereme> |
| Component: | Installer | Assignee: | Patrick Dillon <padillon> |
| Installer sub component: | openshift-installer | QA Contact: | Yunfei Jiang <yunjiang> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | beth.white, bparees, cblecker, padillon, yunjiang |
| Version: | 4.9 | Keywords: | ServiceDeliveryImpact |
| Target Milestone: | --- | ||
| Target Release: | 4.11.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-23 15:08:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2047390 | ||
we also hit this in CI, example: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.9-e2e-aws-canary/1471825120237457408 overall in CI we see 0.17% of our AWS jobs hit it, and it's 0.46% of our aws failures: https://search.ci.openshift.org/?search=When+applying+changes+to+module.vpc.aws_route_table.default&maxAge=48h&context=1&type=bug%2Bjunit&name=aws&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job There does not appear to be an upstream fix for this in the aws terraform provider. Let's monitor CI after we land the upgrade to the terraform provider to see if this issue persists. If so, we will need to contribute a fix upstream. *** Bug 2045049 has been marked as a duplicate of this bug. *** Now that the terraform sdk has been bumped, we should search ci to see if this error is still occurring. This bug seems to have been fixed indirectly by the terraform-aws-provider bump in https://github.com/openshift/installer/pull/5666 No occurrences in master branch CI have been seen for 14 days. Found a same error in recent CI log [1] [1] https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-launch-aws-modern/1544684093524938752 Verified. Not found such errors in recent CI logs. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.11.1 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:6103 |
$ openshift-install version 4.9.x Platform: AWS -- OSD and ROSA, specifically Please specify: IPI What happened? level=info msg=Creating infrastructure resources... level=error level=error msg=Error: Provider produced inconsistent result after apply level=error level=error msg=When applying changes to module.vpc.aws_route_table.private_routes[2], level=error msg=provider "registry.terraform.io/-/aws" produced an unexpected new value for level=error msg=was present, but now absent. What did you expect to happen? Successful install How to reproduce it (as minimally and precisely as possible)? It is random and rare Flow seems to be: 1 Installer creates a thing 2 AWS creates it 3 AWS says it doesn't exist 4 Terraform dies related: https://bugzilla.redhat.com/show_bug.cgi?id=2032521