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

virtual hosted-style doesn't work since 4.14

XMLWordPrintable

    • Low
    • Yes
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when enabling `virtualHostedStyle` with `regionEndpoint` set in image registry operator config, the image registry would ignore the virtual hosted style config and would fail to start. This update fixes the issue by using a new upstream distribution configuration, which is force path style, in favor of the downstream only version, which is virtual hosted style. (link:https://issues.redhat.com/browse/OCPBUGS-32710[(*OCPBUGS-32710*)]
      Show
      * Previously, when enabling `virtualHostedStyle` with `regionEndpoint` set in image registry operator config, the image registry would ignore the virtual hosted style config and would fail to start. This update fixes the issue by using a new upstream distribution configuration, which is force path style, in favor of the downstream only version, which is virtual hosted style. (link: https://issues.redhat.com/browse/OCPBUGS-32710 [(* OCPBUGS-32710 *)]
    • Bug Fix
    • Done

      Description of problem:

          When enabled virtualHostedStyle with regionEndpoint set in config.image/cluster , image registry failed to be running. errors throw:
      
      time="2024-04-22T14:14:31.057192227Z" level=error msg="s3aws: RequestError: send request failed\ncaused by: Get \"https://s3-fips.us-west-1.amazonaws.com/ci-ln-67zbmzk-76ef8-4n6wb-image-registry-us-west-1-xjyfbabyboc?list-type=2&max-keys=1&prefix=\": dial tcp: lookup s3-fips.us-west-1.amazonaws.com on 172.30.0.10:53: no such host" go.version="go1.20.12 X:strictfipsruntime" 

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

          4.14.18

      How reproducible:

          always

      Steps to Reproduce:

          1.
      $ oc get config.imageregistry/cluster -ojsonpath="{.status.storage}"|jq 
      {
        "managementState": "Managed",
        "s3": {
          "bucket": "ci-ln-67zbmzk-76ef8-4n6wb-image-registry-us-west-1-xjyfbabyboc",
          "encrypt": true,
          "region": "us-west-1",
          "regionEndpoint": "https://s3-fips.us-west-1.amazonaws.com",
          "trustedCA": {
            "name": ""
          },
          "virtualHostedStyle": true
        }
      }     
          2. Check registry pod
      $ oc get co image-registry
      NAME             VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
      image-registry   4.15.5    True        True          True       79m     Degraded: Registry deployment has timed out progressing: ReplicaSet "image-registry-b6c58998d" has timed out progressing
          
          

      Actual results:

      $ oc get pods image-registry-b6c58998d-m8pnb -oyaml| yq '.spec.containers[0].env'
      - name: REGISTRY_STORAGE_S3_REGIONENDPOINT
        value: https://s3-fips.us-west-1.amazonaws.com
      [...]
      - name: REGISTRY_STORAGE_S3_VIRTUALHOSTEDSTYLE
        value: "true"
      [...]
      
      $ oc logs image-registry-b6c58998d-m8pnb
      [...]
      time="2024-04-22T14:14:31.057192227Z" level=error msg="s3aws: RequestError: send request failed\ncaused by: Get \"https://s3-fips.us-west-1.amazonaws.com/ci-ln-67zbmzk-76ef8-4n6wb-image-registry-us-west-1-xjyfbabyboc?list-type=2&max-keys=1&prefix=\": dial tcp: lookup s3-fips.us-west-1.amazonaws.com on 172.30.0.10:53: no such host" go.version="go1.20.12 X:strictfipsruntime"     

      Expected results:

          virtual hosted-style should work

      Additional info:

          

            fmissi Flavian Missi
            rh-ee-xiuwang XiuJuan Wang
            XiuJuan Wang XiuJuan Wang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: