Details

    • Type: Bug
    • Status: Awaiting Release (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: jaeger-operator-1.17.2
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Tracing Sprint #39, Tracing Sprint #41, Tracing Sprint #42
    • SFDC Cases Counter:
    • SFDC Cases Links:

      Description

      Tried this Kafka CR on a disconnected environment and kafka results image pull failure.

      Subscription:
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: amq-streams
        namespace: openshift-operators
      spec:
        channel: stable
        installPlanApproval: Automatic
        name: amq-streams
        source: redhat-operators
        sourceNamespace: openshift-marketplace
        startingCSV: amqstreams.v1.4.0
      
      Versions:
      amq-stream-cluster-operator: registry.redhat.io/amq7/amq-streams-rhel7-operator@sha256:4079eadd9a806adfbf3222f071c0498b17a6c54f9b8d199cf5af4961bcbdd83a
      
      $ oc version
      Client Version: 4.3.13
      Server Version: 4.3.13
      Kubernetes Version: v1.16.2
      
      Steps to reproduce:
      • Setup disconnected environment
      • Mirror Red Hat Operators(registry.redhat.io)
      • Install amq-stream-cluster-operator
      • Deploy Kafka CR
      Files:

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jkandasa Jeeva Kandasamy
                Reporter:
                jkandasa Jeeva Kandasamy
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: