crash trying to install jammy beta on a ppc64le

Thanks Patricia.

All the crashes seem to be of the same form:
 Traceback (most recent call last):
   File "/snap/subiquity/3244/usr/lib/python3/dist-packages/aiohttp/connector.py", line 829, in _resolve_host
     addrs = await \
   File "/snap/subiquity/3244/usr/lib/python3/dist-packages/aiohttp/resolver.py", line 29, in resolve
     infos = await self._loop.getaddrinfo(
   File "/snap/subiquity/3244/usr/lib/python3.8/asyncio/base_events.py", line 825, in getaddrinfo
     return await self.run_in_executor(
   File "/snap/subiquity/3244/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
     result = self.fn(*self.args, **self.kwargs)
   File "/snap/subiquity/3244/usr/lib/python3.8/socket.py", line 918, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
 socket.gaierror: [Errno -3] Temporary failure in name resolution

Looks like it's happening near mirror handling, is that right?
Also, can you elaborate on the network situation here?

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967324

Hi Dan, yes, right after the `Configure Ubuntu archive mirror `, it goes to the
`Guided storage configuration`, and :

 ┌────────────────────────────────────────────────────────────────────────┐
   │ │
   │ Sorry, an unknown error occurred. │
   │ │
   │ [ View full report ] │
   │ │
   │ If you want to help improve the installer, you can send an error │
   │ report. │
   │ │
   │ [ Send to Canonical ] │
   │ │
   │ [ Close report ] │
   │ │
   └────────────────────────────────────────────────────────────────────────┘

I was wondering it would be a problem with the DNS, but I tried to install focal on the same system/same config and didn't hit the issue.

I was re-testing jammy beta and it crashes with the same error.

About the network config -
There are these 2 files in netplan dir:

root@ubuntu-server:~# ls /etc/netplan
00-installer-config.yaml 50-cloud-init.yaml.dist-subiquity

(the DNS is pointing out to our MAAS (10.245.71.3)):
---------------------------------------------------------------
root@ubuntu-server:/etc/netplan# cat 00-installer-config.yaml
# This is the network config written by 'subiquity'
network:
  ethernets:
    enP2p1s0f0:
      critical: true
      dhcp-identifier: mac
      dhcp4: true
      nameservers:
        addresses:
        - 10.245.71.3
        - 10.128.58.210
        search:
        - maas.
    enP2p1s0f1:
      dhcp4: true
    enP2p1s0f2:
      dhcp4: true
    enP2p1s0f3:
      dhcp4: true
  version: 2
------------------------------------------------------------------------------
root@ubuntu-server:/etc/netplan# cat 50-cloud-init.yaml.dist-subiquity
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    ethernets:
        enP2p1s0f0:
            critical: true
            dhcp-identifier: mac
            dhcp4: true
            nameservers:
                addresses:
                - 10.245.71.3
                - 10.128.58.210
                search:
                - maas.
        zz-all-en:
            dhcp4: true
            match:
                name: en*
        zz-all-eth:
            dhcp4: true
            match:
                name: eth*
    version: 2
------------------------------------------------------------------------------

Not sure if this is an intermittent failure. Was trying to reproduce again on one server and it was able to install jammy via netboot, but tried again via ISO Virtual Media and it has crashed as I've reported here:
```
2022-04-07 17:23:20,491 DEBUG root:39 finish: subiquity/Filesystem/guided_POST: SUCCESS: 200 {"status": "DONE", "error_report": null, "bootloader": "PREP", "orig_config":...
 2022-04-07 17:23:20,491 INFO aiohttp.access:233 [07/Apr/2022:17:23:20 +0000] "POST /storage/guided HTTP/1.1" 200 17864 "-" "Python/3.8 aiohttp/3.6.2"
 2022-04-07 17:23:22,464 ERROR subiquity.server.server:416 top level error
 Traceback (most recent call last):
   File "/snap/subiquity/3244/usr/lib/python3/dist-packages/aiohttp/connector.py", line 829, in _resolve_host
     addrs = await \
   File "/snap/subiquity/3244/usr/lib/python3/dist-packages/aiohttp/resolver.py", line 29, in resolve
     infos = await self._loop.getaddrinfo(
   File "/snap/subiquity/3244/usr/lib/python3.8/asyncio/base_events.py", line 825, in getaddrinfo
     return await self.run_in_executor(
   File "/snap/subiquity/3244/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
     result = self.fn(*self.args, **self.kwargs)
   File "/snap/subiquity/3244/usr/lib/python3.8/socket.py", line 918, in getaddrinfo
     for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
 socket.gaierror: [Errno -3] Temporary failure in name resolution
 2022-04-07 17:23:22,466 DEBUG subiquitycore.common.errorreport:384 generating crash report
 2022-04-07 17:23:22,466 INFO subiquitycore.common.errorreport:406 saving crash report 'unknown error crashed with gaierror' to /var/crash/1649352202.466186285.unknown.crash
 2022-04-07 17:23:22,467 INFO root:39 start: subiquity/ErrorReporter/1649352202.466186285.unknown/add_info:
```

This looks like some use of the aiohttp client API is resulting in an socket.gaierror instead of something derived from aiohttp.ClientError (unfortunately I can't tell what, I think the only use of aiohttp client APIs in the server is geoip but I might be missing something). I guess we need to catch gaierror as well?

This bug has now been superceeded by bug 1969393 , which describes the same issue reproduced on the "final" Jammy image.
Marking this one as "won't fix".