[temurin-compliance] New Marist s390x machines need /etc/hosts to be fixed

Summary

Marist machines are set up with an /etc/hosts entry that maps the hostname of the machine to 127.0.1.1 - this causes a problem for some of the things we execute on there which are expecting it to resolve to something that is defined on a network interface on the system. Can we please update the /etc/hosts to remove/comment out the entry associating the output from hostname with 127.0.1.1 and adding a line mapping it to the correct external IPv4 address of the machines.

This applies to 148.100.74.163 and 148.100.74.16

It should also be noted that on one machine where we did this manually another line superceding it seems to have appeared, suggesting that something on the system may be overriding this periodically - we will need to watch out for that:

#127.0.1.1      tckubuntu2204.marist.edu        tckubuntu2204
148.100.74.16   tckubuntu2204.marist.edu        tckubuntu2204
127.0.1.1       tckubuntu2204.marist.edu        tckubuntu2204

As another observation, the previous Ubuntu 20.04 machines do not have an entry in /etc/hosts for the hostname, but still resolve their names somewhere in DNS by the look of it. I suspect the new provisioning system at Marist works differently though:

saddisonxls@eclipse-adoptium02:~$ nslookup eclipse-adoptium02
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   eclipse-adoptium02
Address: 148.100.84.95
Name:   eclipse-adoptium02
Address: fe80::c1:21ff:fe46:5174

Steps to reproduce

grep $(hostname) /etc/hosts

ip addr show

What is the current bug behavior?

hostname resolves to 127.0.1.1

What is the expected correct behavior?

/etc/hosts has an entry mapping the hostname of the system to the 'real' external hostname (Note: 127.0.0.1 as the loopback interface's address may also work, but I'd prefer to use the real one as that would likely cause some other problems).

Relevant logs and/or screenshots

n/a

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

Marking this as urgent becuase the provider is quite desperate to reclaim the older systems we have with them, so I want to aim to verify the fixes across the machines tomorrow.