Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-9385

aws: terraform: eventual consistency: error reading Route Table: couldn't find resource

XMLWordPrintable

    • Quality / Stability / Reliability
    • None
    • None
    • None
    • Low
    • None
    • Unspecified
    • None
    • None
    • None
    • None
    • None
    • If docs needed, set a value
    • None
    • None
    • None
    • None
    • None

      Version: master branch

      • IPI (automated install with `openshift-install`. If you don't know, then it's IPI)

      What happened?

      terraform fails to find route table immediately after creation:

      time="2022-07-12T14:52:59Z" level=error
      time="2022-07-12T14:52:59Z" level=error msg="Error: error reading Route Table (rtb-0f35a4184bea5e3dd): couldn't find resource"
      time="2022-07-12T14:52:59Z" level=error
      time="2022-07-12T14:52:59Z" level=error msg=" with module.vpc.aws_route_table.private_routes[0],"
      time="2022-07-12T14:52:59Z" level=error msg=" on vpc/vpc-private.tf line 1, in resource \"aws_route_table\" \"private_routes\":"
      time="2022-07-12T14:52:59Z" level=error msg=" 1: resource \"aws_route_table\" \"private_routes\" {"
      time="2022-07-12T14:52:59Z" level=error

      example from CI here:
      https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-multiarch-master-nightly-4.12-ocp-e2e-aws-heterogeneous/1546812630155399168

      I will open an upstream PR soon.

      Note: we are getting lots of route table failures, but they seem subtly different. The error message for this one looks like a failure to read, but terraform resources "read" themselves right after create. So this is a failure of the route table to read itself upon creation--not another resource trying to read the route table, which is a different class of bugs we have.

              padillon Patrick Dillon
              padillon Patrick Dillon
              None
              None
              Yunfei Jiang Yunfei Jiang
              None
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: