Install does not finish when using interactive-sections: identity

[Jacob Grigg]

Subiquity has the following issues when `interactive-sections: identity` is specified in a custom `user-data`. I am installing using Ubuntu 20.04.3 and have `ds=nocloud-net` set.

 - The identity screen is shown but nothing configured on it ends up being applied.
     - Filling in the `Choose a password` and `Confirm your password` fields is forced even though a password has been specified in `user-data`.
 - The installer gets stuck on and does not run `executing late commands`.
 - The installer does not reboot.

The user specified on the `identity` screen is not created. This was verified by running `sudo cat /target/etc/shadow` from a shell after this installer was stuck.

Once in the stuck state, I wait for any HDD or network activity to finish before leaving the installer for over 10 minutes before forcing a reboot.

The install works as expected if `interactive-sections: identity` is commented out or replaced with `interactive-sections: network`.

Following is the custom `user-data` config which which I am using:

```
#cloud-config
autoinstall:
  version: 1
  interactive-sections:
    - identity
  locale: en_AU.UTF-8
  refresh-installer:
    update: no
  proxy: http://172.16.10.220:3128
  identity:
    hostname: set-hostname-here
    password: [REDACTED]
    username: ansible
  timezone: Australia/Adelaide
  ssh:
      install-server: yes
      authorized-keys:
        - [REDACTED]
      allow-pw: yes
  packages:
    - avahi-daemon
  late-commands:
    - echo "ansible ALL=(ALL:ALL) NOPASSWD:ALL" > /target/etc/sudoers.d/ansible
    - 'echo "IPv4: \\\4" >> /target/etc/issue && echo "IPv6: \\\6" >> /target/etc/issue && echo "" >> /target/etc/issue'
```

[Michael Hudson-Doyle (mwhudson)]

The stuff about the identity page not being filled from the autoinstall data is known (at least to me, not sure there's a bug about it).

The non-completion is strange. From the server log it looks though the identity page was never submitted, and maybe even looks like it or the client crashed. If you can reproduce this (I just tried and it seemed to work fine, although my config was a simpler), are there crash files in /var/crash?

[Jacob Grigg (jacobgrigg.ressys)]

There are no crash files in /var/crash.
I also tried a simpler config with the same result.
Following is the simpler config:

```
#cloud-config
autoinstall:
  version: 1
  interactive-sections:
    - identity
  identity:
    hostname: set-hostname-here
    password: [REDACTED]
    username: ansible
```

[Michael Hudson-Doyle (mwhudson)]

Ah I think this might be a duplicate of https://bugs.launchpad.net/subiquity/+bug/1939176, does that seem possible?

[Launchpad Janitor (janitor)]

[Expired for subiquity (Ubuntu) because there has been no activity for 60 days.]