Bug 977511
| Summary: | [RFE] Gluster trusted pool client authentication should not rely on privileged ports | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Jose A. Rivera <jarrpa> | ||||
| Component: | glusterd | Assignee: | Prasanna Kumar Kalever <prasanna.kalever> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | storage-qa-internal <storage-qa-internal> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 2.1 | CC: | amukherj, rhs-bugs, vagarwal, vbellur | ||||
| Target Milestone: | --- | Keywords: | FutureFeature | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1294468 (view as bug list) | Environment: | |||||
| Last Closed: | 2015-12-28 11:28:01 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1294468 | ||||||
| Attachments: |
|
||||||
Created attachment 764740 [details] Crash-reproducing script. Description of problem: Gluster trusted pool client authentication should not rely on privileged ports. This leads to a resource contention on privileged ports when many connections are made in rapid succession. Version-Release number of selected component (if applicable): 3.4.0.11rhs How reproducible: Always Steps to Reproduce: 1. Add the following lines to the VFS share definition in smb.conf: glusterfs:logfile=<logfile> glusterfs:loglevel=7 2. Run the attached crashmaker.sh script. Usage: ./crashmaker.sh //<server>/<gluster-vfs-share> <username> <password> Actual results: On our systems, around connection 490 we start seeing errors in <logfile> and experience connection timeouts. Expected results: No errors and no timeouts. Additional info: