[HDDS-8219] Run HA secure tests from s3g container

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Fix Version/s: 1.4.0
• Component/s: test
• Labels: pull-request-available
• Target Version/s: 1.4.0
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 20/Mar/23 08:17
• Updated: 25/Mar/23 09:25
• Resolved: 25/Mar/23 09:25

Description

In ozonesecure-ha environment SCM containers have hostnames like "scm1.org", but all Kerberos principals for SCM nodes are in the form testuser/[e-mail]. Since no host named scm exists, lookup takes quite some time:

$ OZONE_LOGLEVEL=TRACE ozone sh volume create /vol1 |& grep 'lookup'
[main] TRACE security.SecurityUtil: Name lookup for om2 took 1 ms.
[main] TRACE security.SecurityUtil: Name lookup for om3 took 0 ms.
[main] TRACE security.SecurityUtil: Name lookup for om1 took 0 ms.
[main] TRACE security.SecurityUtil: Name lookup for scm took 497 ms.

We can improve this simply by executing the same commands from another container, e.g. s3g:

$ OZONE_LOGLEVEL=TRACE ozone sh volume create /vol2 |& grep 'lookup'
[main] TRACE security.SecurityUtil: Name lookup for om2 took 1 ms.
[main] TRACE security.SecurityUtil: Name lookup for om3 took 0 ms.
[main] TRACE security.SecurityUtil: Name lookup for om1 took 0 ms.
[main] TRACE security.SecurityUtil: Name lookup for s3g took 0 ms.

Issue Links

• links to: GitHub Pull Request #4444