10022 port is not allowed to be used by embedded test execution server

Hi,

We were having error during https://github.com/kiegroup/droolsjbpm-integration/blob/dc817a3b84fe9909275f2549ce37616c3adb6d7a/kie-spring-boot/kie-spring-boot-autoconfiguration/kie-server-spring-boot-autoconfiguration-audit-replication/src/test/java/org/kie/server/spring/boot/autoconfiguration/audit/replication/AuditDataReplicationKieServerTest.java execution on github actions

you can check any of these executions as example




you can find the important log piece here https://issues.redhat.com/browse/BXMSPROD-999?focusedCommentId=15132471&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-15132471

the weird thing for us it was working on our Jenkins machines https://issues.redhat.com/browse/BXMSPROD-999?focusedCommentId=15132558&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-15132558

After investigating this a bit we (our team) agreed on changing artemis embedded broker sever port from 10022 to any other port, 15672 for instance https://github.com/kiegroup/droolsjbpm-integration/pull/2241 and it worked.

The question is… why is this 10022 port blocked/not working there? Any idea? Is there a kind of “ports not be used” list or something?

Thanks,
Enrique Mingorance.

@Ginxo ,

I have created an issue ticket (actions/virtual-environments#1666) to help you report the problem to the appropriate engineering team for further investigation and evaluation.

You can follow this issue ticket and add your comments to it.

Hi, @Ginxo
I tried to reproduce the problem with 10022 port with nginx container on 10022

docker run --name test-10022-nginx -d -p 10022:80 nginx:latest
curl http://localhost:10022

But everything work just fine, it seems that the problem is not about the port, but the connection to port on localhost.
We have seen similar problems here: flaky networking
Could you please try to disable hardware network offloading at the start of the build? For ubuntu the proper way is:
sudo ethtool -K eth0 tx off rx off
I hope it will help, please share with more details if any, thank you!

@Ginxo, @BrightRan
Could you please provide a feedback for the suggested workaround?
Thank you!