Bug 1517424

Summary: [WA] : New port numbers are not being reflected , even after 90 mins of volume restart.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Ambarish <asoman>
Component: web-admin-tendrl-gluster-integrationAssignee: Nishanth Thomas <nthomas>
Status: CLOSED ERRATA QA Contact: Vijay Avuthu <vavuthu>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhgs-3.3CC: rhinduja, rhs-bugs, sankarshan, vavuthu
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-18 04:38:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
OldPort none

Description Ambarish 2017-11-25 06:22:07 UTC 
Description of problem:
------------------------

Restarted a Gluster Volume visible in tendrl UI.

New ports are assigned to bricks post volume restarts.

*Before restart* : Ports = 49152,49154.

arbiter-2/gqas004.sbu.lab.eng.bos.redhat.com-bricks-arbiter-3.pid -S /var/run/gluster/ec5a9683478a0b41cb903ec5d90cd14f.socket --brick-name /bricks/arbiter-3 -l /var/log/glusterfs/bricks/bricks-arbiter-3.log --xlator-option *-posix.glusterd-uuid=f6b80b93-aa90-43db-969b-29551fac7e33 --brick-port 49152 --xlator-option arbiter-2-server.listen-port=49152

root     28092     1  0 Nov24 ?        00:12:04 /usr/sbin/glusterfsd -s gqas004.sbu.lab.eng.bos.redhat.com --volfile-id arbiter-2.gqas004.sbu.lab.eng.bos.redhat.com.bricks-arbiter_2 -p /var/run/gluster/vols/arbiter-2/gqas004.sbu.lab.eng.bos.redhat.com-bricks-arbiter_2.pid -S /var/run/gluster/796e54317318773e63e53f46d3e52b1c.socket --brick-name /bricks/arbiter_2 -l /var/log/glusterfs/bricks/bricks-arbiter_2.log --xlator-option *-posix.glusterd-uuid=f6b80b93-aa90-43db-969b-29551fac7e33 --brick-port 49154 --xlator-option arbiter-2-server.listen-port=49154


*After Volume restart* : Ports : 49157,49158

root     18260     1  0 00:32 ?        00:00:00 /usr/sbin/glusterfsd -s gqas004.sbu.lab.eng.bos.redhat.com --volfile-id arbiter-2.gqas004.sbu.lab.eng.bos.redhat.com.bricks-arbiter_2 -p /var/run/gluster/vols/arbiter-2/gqas004.sbu.lab.eng.bos.redhat.com-bricks-arbiter_2.pid -S /var/run/gluster/796e54317318773e63e53f46d3e52b1c.socket --brick-name /bricks/arbiter_2 -l /var/log/glusterfs/bricks/bricks-arbiter_2.log --xlator-option *-posix.glusterd-uuid=f6b80b93-aa90-43db-969b-29551fac7e33 --brick-port 49157 --xlator-option arbiter-2-server.listen-port=49157

root     18284     1  0 00:32 ?        00:00:00 /usr/sbin/glusterfsd -s gqas004.sbu.lab.eng.bos.redhat.com --volfile-id arbiter-2.gqas004.sbu.lab.eng.bos.redhat.com.bricks-arbiter-3 -p /var/run/gluster/vols/arbiter-2/gqas004.sbu.lab.eng.bos.redhat.com-bricks-arbiter-3.pid -S /var/run/gluster/ec5a9683478a0b41cb903ec5d90cd14f.socket --brick-name /bricks/arbiter-3 -l /var/log/glusterfs/bricks/bricks-arbiter-3.log --xlator-option *-posix.glusterd-uuid=f6b80b93-aa90-43db-969b-29551fac7e33 --brick-port 49158 --xlator-option arbiter-2-server.listen-port=49158


UI shows port number as 49152,49154 even after one and a half hours of volume restart.

Screenshot attached.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------

[root@gqac015 ~]# rpm -qa|grep tendrl
tendrl-commons-1.5.4-4.el7rhgs.noarch
tendrl-grafana-selinux-1.5.3-2.el7rhgs.noarch
tendrl-node-agent-1.5.4-5.el7rhgs.noarch
tendrl-api-httpd-1.5.4-2.el7rhgs.noarch
tendrl-grafana-plugins-1.5.4-5.el7rhgs.noarch
tendrl-notifier-1.5.4-3.el7rhgs.noarch
tendrl-ansible-1.5.4-1.el7rhgs.noarch
tendrl-api-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.5.4-4.el7rhgs.noarch
tendrl-monitoring-integration-1.5.4-5.el7rhgs.noarch
tendrl-selinux-1.5.3-2.el7rhgs.noarch


How reproducible:
-----------------

1/1
Comment 2 Ambarish 2017-11-25 06:22:55 UTC 
Created attachment 1358896 [details]
OldPort
Comment 10 errata-xmlrpc 2017-12-18 04:38:26 UTC 
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:3478