subiquitycore.controller.installprogress:145 curtin_error

my user-data looks like this:

#cloud-config
autoinstall:
  version: 1
  identity:
    hostname: ubuntu-server
    password: '$6$wdAcoXrU039hKYPd$508Qvbe7ObUnxoj15DRCkzC3qO7edjH0VV7BPNRDYK4QR8ofJaEEF2heacn0QgD.f8pO8SNp83XNdWG6tocBM1'
    username: ubuntu
  network:
    network:
      version: 2
      ethernets:
        enp0s3: {dhcp4: true, dhcp-identifier: mac}
  ssh:
    install-server: true
  late-commands:
    - sed -i 's/^#*\(send dhcp-client-identifier\).*$/\1 = hardware;/' /target/etc/dhcp/dhclient.conf
    - 'sed -i "s/dhcp4: true/&\n dhcp-identifier: mac/" /target/etc/netplan/00-installer-config.yaml'

The error is this:

         E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease is not valid yet (invalid for another 2h 21min 14s). Updates for this repository will not be applied.

which probably means the clock is wrong in your VM.

I'll see if I can sort that out thanks for pointing that out. It would be much easier if the console logs would tell me something more useful other than just 'I crashed.' If I would have seen this error in console I would have known time might be a factor.

Thanks a lot I'm going to try and rebuild and see how that goes.

Thanks for the help Michael.

So I got it fixed now with your assistance, but it is pretty curious the results in total.

I have 5 build machines that do one build per machine a day to avoid issues. I have some that are LTS18 and some that are LTS20, all are configured for EST time I just verified.

I switched the machine I'm using for subiquity builds on LTS20 over to UTC time and that seems to have solved the issue so far I think. I got two builds going through where I failed before so I think this looks convincing. The curious part is - my other build boxes that are not using subiquity don't seem to have any issues. I'm also building a 20LTS image using debian installer and that is on EST time and doesn't seem to have any issues. I've had my build boxes up and running the same build processed for more than a year and none complain about time other than subiquity. All have correct time I went and verified.

Thanks a lot of the help, not sure if you can give any insight as to why I'm seeing this weird behavior, but at least my builds seem going good now.

many thanks!