Comment 19 for bug 1645422

It still happens in maas 3.5.
My machines look like this when the TFTP connection breaks when downloading initrd.
2 down my:ipv6::address aldo ubuntu@22.04 gen10 Failed deployment: Performing PXE boot

juju retry-provisioning 2 does nothing.

Adding the --debug and --verbose flags just shows it connecting to the controller and disconnecting:
juju retry-provisioning 2 --debug --verbose
INFO juju.cmd supercommand.go:56 running juju [3.3.3.1 944e4076456009e6f220bb22c3e71e4ce2020c03 gc go1.21.0]
DEBUG juju.cmd supercommand.go:57 args: []string{"/root/dev/juju/_build/linux_amd64/bin/juju", "retry-provisioning", "2", "--debug", "--verbose"}
INFO juju.juju api.go:86 connecting to API addresses: [[controller-ipv6-1]:17070 [controller-ipv6-2]:17070 controller-ipv4:17070]
DEBUG juju.api apiclient.go:1172 successfully dialed "wss://controller-ipv4:17070/model/8c66a8a0-f08a-42aa-8f90-0e2e7b9ec519/api"
INFO juju.api apiclient.go:707 connection established to "wss://controller-ipv4:17070/model/8c66a8a0-f08a-42aa-8f90-0e2e7b9ec519/api"
DEBUG juju.api monitor.go:35 RPC connection died
INFO cmd supercommand.go:556 command finished

The version is weird because it's a local build I made to fix another bug, the MAAS code is untouched.