Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-22738

[RHOSO] Rabbit operator managing pods from another operator

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • rabbitmq-cluster-operator
    • None
    • Important

      To Reproduce Steps to reproduce the behavior:

      1. Deploy RHOSO.
      2. Deploy a second RabbitMQ operator in another namespace to other purpose.
      3. Do any change on RHOSO RabbitMQ as an update.
      4. See it's changing the pods from the RabbitMQ not related to Openstack.

      Expected behavior

      • RHOSO deployment not impacting other namespace.

      Device Info (please complete the following information):

      • RHOSO 18
      • Openshift 4.16.37

      Bug impact

      • Not able to use an isolated rabbitmq operator.

      Known workaround

      • Use the parameter OPERATOR_SCOPE_NAMESPACE in t he containers [1].

      Additional context

      •  [1]https://www.rabbitmq.com/kubernetes/operator/configure-operator-defaults

              Unassigned Unassigned
              rh-ee-cgussobo Conrado Gusso Bozza
              rhos-dfg-pidone
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: