Hi all,

Stanislav, thanks for your investigation. Could you do a separate PR with the commit azure: Re-group test envs (it would unblock our other PRs without waiting for your PR 5656 to be reviewed)?

On my side I investigated the "java.net.BindException: Address already in use" exception and I suspect it's related to the way we setup /etc/hosts on the machines. Since commit 1906afb, pki defines 2 AJP connectors, one using localhost4 and the other localhost6 but our /etc/hosts defines only localhost. I created a PR to check if the exception goes away with a proper /etc/hosts configuration (PR 5749).
So the action plan would be:
1. fix azure pipelines with Stanislav's PR
2. fix the "Address already in use" with my PR
3. make the same modification to /etc/hosts in freeipa-pr-ci, so that the tests running in PRCI also have localhost4 and localhost6 defined

How does it sound?

On Tue, May 4, 2021 at 8:38 PM Stanislav Levin via FreeIPA-devel <freeipa-devel@lists.fedorahosted.org> wrote:
The mentioned Java traceback is there even for OK cases.

Unfortunately, I don't know the exact reason right now.
It may be related to the region of Azure hosting and for example,
countermeasures for mining through GH Actions(performance downgrade). I
run exactly the same CI on my account without failures:

if test env's memory limit(sum of limits) doesn't exceed provided by
Azure VM(7Gb+4Gb swap), then tests are OK:



FreeIPA-devel mailing list -- freeipa-devel@lists.fedorahosted.org
To unsubscribe send an email to freeipa-devel-leave@lists.fedorahosted.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorahosted.org/archives/list/freeipa-devel@lists.fedorahosted.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure