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

Internal Registry does not recognize the `ca-west-1` AWS Region

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • 4.14.z
    • 4.14, 4.15
    • Image Registry
    • Critical
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, the image registry did not support {aws-first} region `ca-west-1`. With this release, the image registry can now be deployed in this region. (link:https://issues.redhat.com/browse/OCPBUGS-31857[*OCPBUGS-31857*])
      Show
      Previously, the image registry did not support {aws-first} region `ca-west-1`. With this release, the image registry can now be deployed in this region. (link: https://issues.redhat.com/browse/OCPBUGS-31857 [* OCPBUGS-31857 *])
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-31641. The following is the description of the original issue:

      This is a clone of issue OCPBUGS-29233. The following is the description of the original issue:

      Description of problem:

      Internal registry Pods will panic while deploying OCP on `ca-west-1` AWS Region

      Version-Release number of selected component (if applicable):

      4.14.2    

      How reproducible:

      Every time    

      Steps to Reproduce:

          1. Deploy OCP on `ca-west-1` AWS Region
      
      

      Actual results:

      $ oc logs image-registry-85b69cd9fc-b78sb -n openshift-image-registry
      time="2024-02-08T11:43:09.287006584Z" level=info msg="start registry" distribution_version=v3.0.0+unknown go.version="go1.20.10 X:strictfipsruntime" openshift_version=4.14.0-202311021650.p0.g5e7788a.assembly.stream-5e7788a
      time="2024-02-08T11:43:09.287365337Z" level=info msg="caching project quota objects with TTL 1m0s" go.version="go1.20.10 X:strictfipsruntime"
      panic: invalid region provided: ca-west-1goroutine 1 [running]:
      github.com/distribution/distribution/v3/registry/handlers.NewApp({0x2873f40?, 0xc00005c088?}, 0xc000581800)
          /go/src/github.com/openshift/image-registry/vendor/github.com/distribution/distribution/v3/registry/handlers/app.go:130 +0x2bf1
      github.com/openshift/image-registry/pkg/dockerregistry/server/supermiddleware.NewApp({0x2873f40, 0xc00005c088}, 0x0?, {0x2876820?, 0xc000676cf0})
          /go/src/github.com/openshift/image-registry/pkg/dockerregistry/server/supermiddleware/app.go:96 +0xb9
      github.com/openshift/image-registry/pkg/dockerregistry/server.NewApp({0x2873f40?, 0xc00005c088}, {0x285ffd0?, 0xc000916070}, 0xc000581800, 0xc00095c000, {0x0?, 0x0})
          /go/src/github.com/openshift/image-registry/pkg/dockerregistry/server/app.go:138 +0x485
      github.com/openshift/image-registry/pkg/cmd/dockerregistry.NewServer({0x2873f40, 0xc00005c088}, 0xc000581800, 0xc00095c000)
          /go/src/github.com/openshift/image-registry/pkg/cmd/dockerregistry/dockerregistry.go:212 +0x38a
      github.com/openshift/image-registry/pkg/cmd/dockerregistry.Execute({0x2858b60, 0xc000916000})
          /go/src/github.com/openshift/image-registry/pkg/cmd/dockerregistry/dockerregistry.go:166 +0x86b
      main.main()
          /go/src/github.com/openshift/image-registry/cmd/dockerregistry/main.go:93 +0x496
          

      Expected results:

      The internal registry is deployed with no issues    

      Additional info:

      This is a new AWS Region we are adding support to. The support will be backported to 4.14.z    

            fmissi Flavian Missi
            openshift-crt-jira-prow OpenShift Prow Bot
            Wen Wang Wen Wang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: