Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-7164

AMQ 7.10 Brokers cannot be managed by the FuseConsole on OpenShift

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • AMQ 7.10.0.GA
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      1. Create a testing namespace

      2. Deploy the latest available Operators using the OperatorHub in the created namespace:

          - Deploy AMQ Broker operator latest version

          - Deploy Fuse Console Operator latest version

      3. Create a FuseConsole instance using the web form: use defaults

      4. Deploy an AMQ 7.10 broker using the following CR

      apiVersion: broker.amq.io/v1beta1
kind: ActiveMQArtemis
metadata:
  name: ex-aao-710
spec:
  version: 7.10.0
  upgrades:
    enabled: true
    minor: false
  deploymentPlan:
    persistenceEnabled: false
    size: 1
    image: placeholder
    jolokiaAgentEnabled: true
    managementRBACEnabled: false
    resources:
      limits:
        cpu: 500m
        memory: 512Mi
      requests:
        cpu: 200m
        memory: 128Mi
  console:
    expose: false

      5. Deploy an AMQ 7.9 broker using the following CR

       

      apiVersion: broker.amq.io/v1beta1
kind: ActiveMQArtemis
metadata:
  name: ex-aao-79
spec:
  version: 7.9.0
  upgrades:
    enabled: true
    minor: false
  deploymentPlan:
    size: 1
    image: placeholder
    jolokiaAgentEnabled: true
    managementRBACEnabled: false
    resources:
      limits:
        cpu: 500m
        memory: 512Mi
      requests:
        cpu: 200m
        memory: 128Mi
  console:
    expose: false

       

       

      6. Access to FuseConsole

          - Both AMQ PODs are found, but you cannot establish the connection to the 7.10 version. the version 7.9 works properly.

       

       

       

      Show
      1. Create a testing namespace 2. Deploy the latest available Operators using the OperatorHub in the created namespace:     - Deploy AMQ Broker operator latest version     - Deploy Fuse Console Operator latest version 3. Create a FuseConsole instance using the web form: use defaults 4. Deploy an AMQ 7.10 broker using the following CR apiVersion: broker.amq.io/v1beta1 kind: ActiveMQArtemis metadata:   name: ex-aao-710 spec:   version: 7.10.0   upgrades:     enabled: true     minor: false   deploymentPlan:     persistenceEnabled: false     size: 1     image: placeholder     jolokiaAgentEnabled: true     managementRBACEnabled: false     resources:       limits:         cpu: 500m         memory: 512Mi       requests:         cpu: 200m         memory: 128Mi   console:     expose: false 5. Deploy an AMQ 7.9 broker using the following CR   apiVersion: broker.amq.io/v1beta1 kind: ActiveMQArtemis metadata:   name: ex-aao-79 spec:   version: 7.9.0   upgrades:     enabled: true     minor: false   deploymentPlan:     size: 1     image: placeholder     jolokiaAgentEnabled: true     managementRBACEnabled: false     resources:       limits:         cpu: 500m         memory: 512Mi       requests:         cpu: 200m         memory: 128Mi   console:     expose: false     6. Access to FuseConsole     - Both AMQ PODs are found, but you cannot establish the connection to the 7.10 version. the version 7.9 works properly.      

      The AMQ webconsole cannot be accessed when the FuseConsole is used.

      The running PODs are found, but when you click on the "connect" button, the console cannot be accessed and a the message "No Selected Container. Please select a container to connect to in the navigation bar above and access the management console" appears.

       

      This seems to happen in AMQ 7.10. When you deploy an AMQ 7.9 instance the FuseConsole can connect to the running PODs.

       

        1. Screenshot-error.png
          Screenshot-error.png
          39 kB

              dbruscin Domenico Francesco Bruscino
              ryanezil Rafael Yáñez Illescas
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: