xuruidong opened a new pull request, #10388: URL: https://github.com/apache/apisix/pull/10388
### Description <!-- Please include a summary of the change and which issue is fixed. --> <!-- Please also include relevant motivation and context. --> Fixes #9417 There are many failed CI tests due to the grpc test. https://github.com/apache/apisix/actions/runs/6555753481/job/17804672395 https://github.com/apache/apisix/actions/runs/6505891288/job/17670381622 https://github.com/apache/apisix/actions/runs/6505891281/job/17670380923  apisix get 502 from upstream:  The reason is that the grpc-server-example start failed due to port occupancy.  I thought maybe some client sockets occupied on the port and I reproduced the issue. The test use docker container with host network mode and I did not find a way to set `net.ipv4.ip_local_reserved_ports` in github action. The default `net.ipv4.ip_local_port_range` is `32768-60999`, so use the port not in range 32768-60999 to avoid port occupancy. ### Checklist - [x] I have explained the need for this PR and the problem it solves - [ ] I have explained the changes or the new features added to this PR - [ ] I have added tests corresponding to this change - [ ] I have updated the documentation to reflect this change - [ ] I have verified that this change is backward compatible (If not, please discuss on the [APISIX mailing list](https://github.com/apache/apisix/tree/master#community) first) <!-- Note 1. Mark the PR as draft until it's ready to be reviewed. 2. Always add/update tests for any changes unless you have a good reason. 3. Always update the documentation to reflect the changes made in the PR. 4. Make a new commit to resolve conversations instead of `push -f`. 5. To resolve merge conflicts, merge master instead of rebasing. 6. Use "request review" to notify the reviewer after making changes. 7. Only a reviewer can mark a conversation as resolved. --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
