Description of problem: Whene supplying broker address as IPv6 literal (ex. [IPv6]) the qpid-cluster fails to connect. It's probably tries to resolve literal as domain name. Version-Release number of selected component (if applicable): qpid-tools-0.12-2.el6.noarch python-qpid-0.14-1.el6.noarch python-qpid-qmf-0.14-3.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. start up cluster with --cluster-url with IPv6 able broker (ex. amqp:tcp:[IPv6]) 2. run qpid-cluster -C [IPv6] 3. observe that qpid-cluster fails Actual results: Traceback (most recent call last): File "/usr/bin/qpid-cluster", line 311, in <module> sys.exit(main()) File "/usr/bin/qpid-cluster", line 302, in main raise Exception("Failed: %s - %s" % (e.__class__.__name__, e)) Exception: Failed: gaierror - [Errno -2] Name or service not known Expected results: qpid-cluster lists active connections Additional info:
Sorry for the inconvenience, there is an mistake in step 1. there is no need to setting up cluster-url with IPv6 literal.
Is this a duplicate of Bug 790571?
This is not a duplicate, it is simmilar case but on different place. This says that qpid-cluster -C cannot parse IPv6 literal on command line. (so here is no need to set cluster-url to IPv6 literal) Bug 790571 says, that qpid-cluster -C cannot parse IPv6 literal supplied in cluster-url set on broker.