QA

Motivation¶

An HMC was setup 10.145.14.33 and OPS-Service/salt actually includes A and AAAA entries:

salt/profile/dns/files/prg2_suse_org/dns-oqa.prg2.suse.org:powerhmc1.oqa.prg2.suse.org.     300  A     10.145.14.33
salt/profile/dns/files/prg2_suse_org/dns-oqa.prg2.suse.org:powerhmc1.oqa.prg2.suse.org.     300  AAAA  2a07:de40:b203:15:10:145:14:33

I think this was added by mistake in the "oqa" domain in

commit 873119359
Author: Gschlotter <gschlotter@suse.de>
Date:   Wed Sep 6 11:54:16 2023 +0200

    add powerhmc1.oqa.prg2.suse.org

which should actually have been a QE generic entry. Communication and coordination about the setup of this HMC was very spotty, e.g. see #132140-15 . So likely the A+AAAA records should be in a qe.prg2.suse.org network and also a reverse-PTR entry is missing.

Acceptance criteria¶

• AC1: Our relevant documentation references a forward and backward reachable HMC instance

Acceptance tests¶

• AT1-1: host powerhmc1.qe.prg2.suse.org or similar yields a valid entry
• AT1-2: ping -c1 $fqdn is reachable from various end-points, e.g. home office VPN as well as internal servers
• AT1-3: host $ipv4 yields valid FQDN
• AT1-4: Verify that our documentation, e.g. wiki, references the forward and backward reachable HMC instance

Suggestions¶

• Wait for #137885 to have a complete PRG2 based QE setup
• Suggest to move powerhmc1.oqa.prg2.suse.org to that proper QE network
• Conduct ATs and check what is missing, fix or ask Eng-Infra for help as needed
• Add to documentation accordingly, cross-check older references to powerhmc1/2/3, etc.