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

Using IBM S3 Storage for cluster container registry operator

XMLWordPrintable

    • None
    • None
    • Unspecified
    • If docs needed, set a value

      Description of problem:

      I'm trying to configure Registry Operator with IBM COS S3 buckets.
      It looks fine except that the underlying ibm-cos-sdk/api is giving following error.

      I0612 12:02:47.220252 7 controller.go:214] object changed: *v1.Config, Name=cluster (status=true): changed:status.conditions.0.lastTransitionTime=

      {"2020-06-12T12:02:46Z" -> "2020-06-12T12:02:47Z"}

      , changed:status.conditions.0.message=

      {"InvalidLocationConstraint: Container storage location with specified provisioning code not available\n\tstatus code: 400, request id: 7eb1009b-6d75-42bb-a381-5bdb0a36f3c4, host id: " -> "InvalidLocationConstraint: Container storage location with specified provisioning code not available\n\tstatus code: 400, request id: 26a59ddd-c6e7-4754-a094-46c5d9ffb80b, host id: "}

      , changed:status.conditions.2.message=

      {"Unable to apply resources: unable to sync storage configuration: InvalidLocationConstraint: Container storage location with specified provisioning code not available\n\tstatus code: 400, request id: 7eb1009b-6d75-42bb-a381-5bdb0a36f3c4, host id: " -> "Unable to apply resources: unable to sync storage configuration: InvalidLocationConstraint: Container storage location with specified provisioning code not available\n\tstatus code: 400, request id: 26a59ddd-c6e7-4754-a094-46c5d9ffb80b, host id: "}

      I attached a reproducer bash script ..

              cewong@redhat.com Cesar Wong
              openshift_jira_bot OpenShift Jira Bot
              Red Hat Employee
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: