| Summary: | Add an option to /etc/glusterfs/glusterd.vol to change the base-port of brick processes | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Niels de Vos <ndevos> |
| Component: | glusterfs | Assignee: | Niels de Vos <ndevos> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | barumuga, joe, jonathansteffan, kkeithle, ndevos, silas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.4.1-3.fc19 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-14 03:05:25 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: | |
|
Description
Niels de Vos
2013-10-26 15:10:20 UTC
Verification that the patch works: 1. create and start a volume: [root@vm130-31 tmp]# gluster volume create somevol replica 2 vm130-31:/bricks/somevol/data vm130-32:/bricks/somevol/data volume create: somevol: success: please start the volume to access data [root@vm130-31 tmp]# gluster volume start somevol volume start: somevol: success 2. check the ports used (default is 49152) [root@vm130-31 tmp]# gluster volume status Status of volume: somevol Gluster process Port Online Pid ------------------------------------------------------------------------------ Brick vm130-31:/bricks/somevol/data 49152 Y 1118 Brick vm130-32:/bricks/somevol/data 49152 Y 26308 NFS Server on localhost 2049 Y 1128 Self-heal Daemon on localhost N/A Y 1135 NFS Server on 192.168.130.32 2049 Y 26320 Self-heal Daemon on 192.168.130.32 N/A Y 26324 There are no active volume tasks 3. uncomment and change the base-port option (50152): [root@vm130-31 tmp]# vi /etc/glusterfs/glusterd.vol 4. restart the processes [root@vm130-31 tmp]# systemctl restart glusterfsd [root@vm130-31 tmp]# systemctl restart glusterd 5. check if the port has been modified [root@vm130-31 tmp]# gluster volume status Status of volume: somevol Gluster process Port Online Pid ------------------------------------------------------------------------------ Brick vm130-31:/bricks/somevol/data 50152 Y 1204 Brick vm130-32:/bricks/somevol/data 49152 Y 26308 NFS Server on localhost 2049 Y 1212 Self-heal Daemon on localhost N/A Y 1219 NFS Server on 192.168.130.32 2049 Y 26320 Self-heal Daemon on 192.168.130.32 N/A Y 26324 There are no active volume tasks -> VERIFIED, vm130-31 uses port 50152 after updating base-port in glusterd.vol glusterfs-3.4.1-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/glusterfs-3.4.1-3.fc18 glusterfs-3.4.1-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/glusterfs-3.4.1-3.fc19 glusterfs-3.4.1-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/glusterfs-3.4.1-3.fc20 Package glusterfs-3.4.1-3.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glusterfs-3.4.1-3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20091/glusterfs-3.4.1-3.fc20 then log in and leave karma (feedback). glusterfs-3.4.1-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. glusterfs-3.4.1-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. glusterfs-3.4.1-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |