action #156250
closedcoordination #121720: [saga][epic] Migration to QE setup in PRG2+NUE3 while ensuring availability
coordination #129280: [epic] Move from SUSE NUE1 (Maxtorhof) to new NBG Datacenters
Ensure IPv6 works in qe.nue2.suse.org
0%
Description
Motivation¶
With https://jira.suse.com/browse/ENGINFRA-3958 and #155824 IPv6 was mainly setup also for NUE2. From a VM (tumblesle.qe.nue2.suse.org) I can confirm that I can reach hosts over IPv6 but the DNS record only returns an A-record, not AAAA. What do we need to ensure hosts in qe.nue2.suse.org can also be reached over IPv6?
Suggestions¶
- Read what was done in #155824
- If SLAAC is used, simply add AAAA records for every machine controlled by salt
- Take a machine listed in https://progress.opensuse.org/issues/155824#note-19
- Lookup its MAC e.g. via SSH or looking in https://gitlab.suse.de/OPS-Service/salt/-/blob/production/pillar/domain/qe_nue2_suse_org/hosts.yaml?ref_type=heads
- Convert it to UID-64 with e.g. https://progress.opensuse.org/issues/155824#note-20 or any other tool
- Add an AAAA entry based on the network-prefix + UID from step 3
Updated by okurz about 2 months ago
- Related to action #155824: Support IPv6 SLAAC in our infrastructure size:M added
Updated by okurz about 2 months ago
sudo salt '*.qe.nue2.suse.org' cmd.run 'ip -6 a | grep 2a07 | sed -n "s/^.*inet6 \([^/]*\).*global dynamic mngtmpaddr.*$/\1/p"' looks promising:
backup-qam.qe.nue2.suse.org:
2a07:de40:a102:5:ec4:7aff:fe71:97b8
osiris-1.qe.nue2.suse.org:
2a07:de40:a102:5:ae1f:6bff:fe47:58d2
sapworker1.qe.nue2.suse.org:
2a07:de40:a102:5:b645:6ff:fee9:4f51
sapworker3.qe.nue2.suse.org:
2a07:de40:a102:5:b645:6ff:fee9:48eb
sapworker2.qe.nue2.suse.org:
2a07:de40:a102:5:b645:6ff:fee9:49bd
openqaworker1.qe.nue2.suse.org:
2a07:de40:a102:5:2e60:cff:fe73:3d6
qamaster.qe.nue2.suse.org:
2a07:de40:a102:5:225:90ff:fef1:d8e4
petrol.qe.nue2.suse.org:
2a07:de40:a102:5:9abe:94ff:fe03:e94b
imagetester.qe.nue2.suse.org:
2a07:de40:a102:5:225:90ff:fea2:ba92
monitor.qe.nue2.suse.org:
2a07:de40:a102:5:5054:ff:fe00:894e
baremetal-support.qe.nue2.suse.org:
2a07:de40:a102:5:5054:ff:fe67:81a2
jenkins.qe.nue2.suse.org:
2a07:de40:a102:5:5054:ff:fe71:8933
tumblesle.qe.nue2.suse.org:
2a07:de40:a102:5:5054:ff:fef4:58ab
diesel.qe.nue2.suse.org:
2a07:de40:a102:5:9abe:94ff:fe04:4817
unreal6.qe.nue2.suse.org:
2a07:de40:a102:5:225:90ff:fee5:344
mania.qe.nue2.suse.org:
2a07:de40:a102:5:42f2:e9ff:fe31:5460
schort-server.qe.nue2.suse.org:
2a07:de40:a102:5:5054:ff:fe3f:5a7f
openqa-piworker.qe.nue2.suse.org:
2a07:de40:a102:5:e65f:1ff:febb:6340
backup-vm.qe.nue2.suse.org:
2a07:de40:a102:5:5054:ff:fe98:19ff
created https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4916
For the other entries a bit of hackery. I put the script from nicksinger from #155824-20 into a local script file "mac-to-ipv6" and then
yq -r 'to_entries[] | [.key, .value.mac] | @tsv' pillar/domain/qe_nue2_suse_org/hosts.yaml | while read -r host mac; do ip=$(prefix=2a07:de40:a102:5: mac-to-ipv6 $mac); ping -q -c1 $ip >/dev/null && echo "$host AAAA $ip"; done
Updated by okurz about 2 months ago
- Due date set to 2024-03-29
- Status changed from In Progress to Feedback
Added another commit into https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4916
Now, should we also include AAAA records for currently not reachable machines or leave 'em out for now?
Updated by okurz about 2 months ago
- Due date deleted (
2024-03-29) - Status changed from Feedback to Blocked
discussed with nicksinger, we could do one of the following three:
- we could just add AAAA records for all systems and remove on individual ones where there are problems
- add all records and verify all -> too much effort
- leave it as-is and add entries as necessary in the future
For now we will stay with 3.
blocked on https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4916
Updated by okurz about 1 month ago
- Status changed from Blocked to Resolved
https://gitlab.suse.de/OPS-Service/salt/-/merge_requests/4916 merged and deployed and verified.
Updated by okurz 8 days ago
- Related to action #159555: IPMI access over IPv6 doesn't work on imagetester - try to update BIOS with physical access size:S added