Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: We are using port 24006 for gluster blockd, as it is registered port by 'med-net-svc' we should use a different port. Source: https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=126
Tested and verified this on the build gluster-block-0.2.1-11 and tcmu-runner-1.2.0-14 and gluster-3.8.4-44. When I tried to create block on an existing setup which had the port number 24006 opened, it did not succeed. Deleted port number 24006 and opened 24010 on all the nodes of my 6-node cluster and did multiple block-creates, which were all successful. Moving this bug to verified in rhgs 3.3.0. Logs are pasted below. [root@dhcp47-117 ~]# rpm -qa | grep gluster glusterfs-3.8.4-44.el7rhgs.x86_64 glusterfs-geo-replication-3.8.4-44.el7rhgs.x86_64 glusterfs-api-3.8.4-44.el7rhgs.x86_64 glusterfs-fuse-3.8.4-44.el7rhgs.x86_64 python-gluster-3.8.4-44.el7rhgs.noarch libvirt-daemon-driver-storage-gluster-3.2.0-14.el7_4.2.x86_64 gluster-nagios-common-0.2.4-1.el7rhgs.noarch glusterfs-client-xlators-3.8.4-44.el7rhgs.x86_64 glusterfs-server-3.8.4-44.el7rhgs.x86_64 glusterfs-rdma-3.8.4-44.el7rhgs.x86_64 vdsm-gluster-4.17.33-1.2.el7rhgs.noarch gluster-nagios-addons-0.2.9-1.el7rhgs.x86_64 glusterfs-cli-3.8.4-44.el7rhgs.x86_64 gluster-block-0.2.1-11.el7rhgs.x86_64 glusterfs-libs-3.8.4-44.el7rhgs.x86_64 glusterfs-events-3.8.4-44.el7rhgs.x86_64 [root@dhcp47-117 ~]# [root@dhcp47-117 ~]# rpm -qa | grep tcmu-runner tcmu-runner-1.2.0-14.el7rhgs.x86_64 [root@dhcp47-117 ~]# [root@dhcp47-117 ~]# gluster peer status Number of Peers: 5 Hostname: dhcp47-121.lab.eng.blr.redhat.com Uuid: ca9b34ea-49a5-414b-a2aa-a226c0baa772 State: Peer in Cluster (Connected) Hostname: dhcp47-113.lab.eng.blr.redhat.com Uuid: 8e0ab4d4-4ea0-4c11-9ddd-aa714e5ebf51 State: Peer in Cluster (Connected) Hostname: dhcp47-114.lab.eng.blr.redhat.com Uuid: 4db31bb2-210d-46ac-99b0-e7ef67695fdc State: Peer in Cluster (Connected) Hostname: dhcp47-115.lab.eng.blr.redhat.com Uuid: 720fb48c-ee90-4b01-9056-c2dd169d2d11 State: Peer in Cluster (Connected) Hostname: dhcp47-116.lab.eng.blr.redhat.com Uuid: e7e68cc4-b178-4420-948b-212371e6ce77 State: Peer in Cluster (Connected) [root@dhcp47-117 ~]# [root@dhcp47-117 ~]# [root@dhcp47-117 ~]# gluster v list pluto [root@dhcp47-117 ~]# [root@dhcp47-117 ~]# firewall-cmd --list-ports --zone=public 5666/tcp 443/tcp 80/tcp 5667/tcp 54321/tcp 5900/tcp 5900-6923/tcp 4379/tcp 3260/tcp 111/tcp 24010/tcp [root@dhcp47-117 ~]# [root@dhcp47-117 ~]# gluster v info Volume Name: pluto Type: Distributed-Replicate Volume ID: f8aa15b6-1017-4e11-b8a5-fcfbad5e1f78 Status: Started Snapshot Count: 0 Number of Bricks: 6 x 3 = 18 Transport-type: tcp Bricks: Brick1: 10.70.47.121:/bricks/brick5/pluto_0 Brick2: 10.70.47.113:/bricks/brick5/pluto_1 Brick3: 10.70.47.114:/bricks/brick5/pluto_2 Brick4: 10.70.47.115:/bricks/brick5/pluto_3 Brick5: 10.70.47.116:/bricks/brick5/pluto_4 Brick6: 10.70.47.117:/bricks/brick5/pluto_5 Brick7: 10.70.47.121:/bricks/brick6/pluto_6 Brick8: 10.70.47.113:/bricks/brick6/pluto_7 Brick9: 10.70.47.114:/bricks/brick6/pluto_8 Brick10: 10.70.47.115:/bricks/brick6/pluto_9 Brick11: 10.70.47.116:/bricks/brick6/pluto_10 Brick12: 10.70.47.117:/bricks/brick6/pluto_11 Brick13: 10.70.47.121:/bricks/brick7/pluto_12 Brick14: 10.70.47.113:/bricks/brick7/pluto_13 Brick15: 10.70.47.114:/bricks/brick7/pluto_14 Brick16: 10.70.47.115:/bricks/brick7/pluto_15 Brick17: 10.70.47.116:/bricks/brick7/pluto_16 Brick18: 10.70.47.117:/bricks/brick7/pluto_17 Options Reconfigured: features.quota-deem-statfs: on features.inode-quota: on features.quota: on features.scrub: Active features.bitrot: on server.allow-insecure: on user.cifs: off features.shard-block-size: 64MB features.shard: on cluster.shd-wait-qlength: 10000 cluster.shd-max-threads: 8 cluster.locking-scheme: granular cluster.data-self-heal-algorithm: full cluster.quorum-type: auto cluster.eager-lock: disable network.remote-dio: disable performance.strict-o-direct: on performance.readdir-ahead: off performance.open-behind: off performance.stat-prefetch: off performance.io-cache: off performance.read-ahead: off performance.quick-read: off transport.address-family: inet nfs.disable: on cluster.brick-multiplex: enable [root@dhcp47-121 ~]# gluster-block create Inadequate arguments for create: gluster-block create <volname/blockname> [ha <count>] [auth enable|disable] <HOST1[,HOST2,...]> <size> [--json*] [root@dhcp47-121 ~]# for i in {1..200}; do time gluster-block create pluto/bk$i ha 3 10.70.47.121,10.70.47.113,10.70.47.114 1Mib; done failed to configure on 10.70.47.113 : No route to host failed to configure on 10.70.47.114 : No route to host RESULT:FAIL real 0m7.766s user 0m0.005s sys 0m0.012s failed to configure on 10.70.47.113 : No route to host failed to configure on 10.70.47.114 : No route to host RESULT:FAIL [root@dhcp47-121 ~]# firewall-cmd --list-ports --zone=public 5666/tcp 443/tcp 80/tcp 5667/tcp 54321/tcp 5900/tcp 5900-6923/tcp 4379/tcp 3260/tcp 24006/tcp 111/tcp [root@dhcp47-121 ~]# [root@dhcp47-121 ~]# firewall-cmd --remove-port=24006/tcp --permanent success [root@dhcp47-121 ~]# [root@dhcp47-121 ~]# [root@dhcp47-121 ~]# firewall-cmd --reload success [root@dhcp47-121 ~]# firewall-cmd --list-ports --zone=public 5666/tcp 443/tcp 80/tcp 5667/tcp 54321/tcp 5900/tcp 5900-6923/tcp 4379/tcp 3260/tcp 111/tcp [root@dhcp47-121 ~]# firewall-cmd --add-port=24010/tcp --zone=public --permanent success [root@dhcp47-121 ~]# firewall-cmd --list-ports --zone=public 5666/tcp 443/tcp 80/tcp 5667/tcp 54321/tcp 5900/tcp 5900-6923/tcp 4379/tcp 3260/tcp 111/tcp [root@dhcp47-121 ~]# firewall-cmd --reload success [root@dhcp47-121 ~]# firewall-cmd --list-ports --zone=public 5666/tcp 443/tcp 80/tcp 5667/tcp 54321/tcp 5900/tcp 5900-6923/tcp 4379/tcp 3260/tcp 111/tcp 24010/tcp [root@dhcp47-121 ~]# [root@dhcp47-117 ~]# gluster-block list pluto bk6 bk20 bk22 ... ... bk226 bk233 [root@dhcp47-117 ~]#
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2773