| Summary: | qpid-cluster does seem to handle ip binding correctly | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Fabio Massimo Di Nitto <fdinitto> |
| Component: | qpid-cpp | Assignee: | messaging-bugs <messaging-bugs> |
| Status: | NEW --- | QA Contact: | MRG Quality Engineering <mrgqe-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.3 | CC: | jross |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Description of problem: qpid is running on a node with multiple interfaces: [root@rhos4-node4 ~]# qpid-cluster Cluster Name: qpid-cluster Cluster Status: ACTIVE Cluster Size: 2 Members: ID=1.0.0.0:2081 URL=amqp:tcp:192.168.2.179:5672,tcp:192.168.4.179:5672 : ID=2.0.0.0:2085 URL=amqp:tcp:192.168.2.180:5672,tcp:192.168.4.180:5672 [root@rhos4-node4 ~]# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 54:52:00:01:0A:04 inet addr:192.168.4.180 Bcast:192.168.4.255 Mask:255.255.255.0 inet6 addr: fe80::5652:ff:fe01:a04/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:48 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4596 (4.4 KiB) TX bytes:1814 (1.7 KiB) [root@rhos4-node4 ~]# ifdown eth1 wait a bit [root@rhos4-node4 ~]# qpid-cluster Cluster Name: qpid-cluster Cluster Status: ACTIVE Cluster Size: 2 Members: ID=1.0.0.0:2081 URL=amqp:tcp:192.168.2.179:5672,tcp:192.168.4.179:5672 : ID=2.0.0.0:2085 URL=amqp:tcp:192.168.2.180:5672,tcp:192.168.4.180:5672 qpid doesn´t recognize that an interface has gone away. Or even changed IP address. This binding issue can also be simulated by adding secondary addresses to interfaces and makes HA clusters a bit too complicated.