Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-8263

Apicast Operator stops reconciliating

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Major
    • None
    • 2.11.2 GA
    • Apicast Operator
    • None
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started

    Description

      We encountered Apicast operator which stopped reconciliating with only this in its logs:

      {"level":"info","ts":1646137787.3967032,"logger":"setup","msg":"Operator Version: 0.5.1"}
      {"level":"info","ts":1646137787.4776747,"logger":"setup","msg":"Go Version: go1.13.15"}
      {"level":"info","ts":1646137787.4868631,"logger":"setup","msg":"Go OS/Arch: linux/amd64"}
      I0301 12:29:59.260431       1 request.go:645] Throttling request took 1.194387909s, request: GET:https://172.30.0.1:443/apis/apps/v1?timeout=32s
      E0301 12:34:31.960395       1 request.go:1001] Unexpected error when reading response body: context deadline exceeded (Client.Timeout exceeded while reading body)
      

      Workaround for this issue is to kill the pod

      Attachments

        Activity

          People

            Unassigned Unassigned
            phala@redhat.com Petr Hála
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: