action #159306
closedcoordination #121720: [saga][epic] Migration to QE setup in PRG2+NUE3 while ensuring availability
coordination #123800: [epic] Provide SUSE QE Tools services running in PRG2 aka. Prg CoLo
coordination #137630: [epic] QE (non-openQA) setup in PRG2
Fix AAAA records in qe.prg2.suse.org size:S
0%
Description
Motivation¶
Apparently
https://gitlab.suse.de/OPS-Service/salt/-/blob/production/salt/profile/dns/files/prg2_suse_org/dns-qe.prg2.suse.org has wrong AAAA records. Asked in
https://suse.slack.com/archives/C04MDKHQE20/p1713438519404599
… you lately added entries for "storage" in https://gitlab.suse.de/OPS-Service/salt/-/blob/production/salt/profile/dns/files/prg2_suse_org/dns-qe.prg2.suse.org?ref_type=heads&plain=1 with AAAA records. Those AAAA records are addresses which would match to DHCPv6 entries but AFAIK there is no DHCPv6 in qe.prg2.suse.org but SLAAC. So is it that you added wrong entries and haven't checked those? If yes what's the quickest way to update all AAAA records to match the SLAAC addresses?
Acceptance criteria¶
- AC1: https://gitlab.suse.de/OPS-Service/salt/-/blob/production/salt/profile/dns/files/prg2_suse_org/dns-qe.prg2.suse.org has correct AAAA entries for all hosts compliant with SLAAC
Suggestions¶
- Streamline scripting from #156250-7
- Update AAAA records for all to be SLAAC compliant
- At best also do reverse PTR entries