[AMQ Interconnect] How to externalize the the vhost policies in a separate configmap ?

Solution Verified - Updated -

Issue

  • How to externalize the the vhost policies in a configmap ?
  • Interconnect Router Pods are not connecting to one another in the same Namespace and the startup Script is throwing errors:

    Waiting for IP address...
    Traceback (most recent call last):
      File "/opt/interconnect/bin/auto_mesh.py", line 246, in <module>
        get_config(sys.argv[1]).append_connectors(connectors)
      File "/opt/interconnect/bin/auto_mesh.py", line 190, in append_connectors
        properties = self.get_inter_router_properties()
      File "/opt/interconnect/bin/auto_mesh.py", line 179, in get_inter_router_properties
        entities = SimpleParser(self.filename).parse()
      File "/opt/interconnect/bin/auto_mesh.py", line 112, in parse
        e = self.parse_entity()
      File "/opt/interconnect/bin/auto_mesh.py", line 119, in parse_entity
        properties = self.parse_properties()
      File "/opt/interconnect/bin/auto_mesh.py", line 133, in parse_properties
        raise Exception("Could not parse properties: %s" % self.lines[-1])
    Exception: Could not parse properties: }
    
    Error configuring automesh: Could not parse properties: }
    

Environment

  • Red Hat AMQ (AMQ Interconnect) 1.10
  • Red Hat OpenShift Container (Openshift) 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content