Comment 3 for bug 1904810

Is this actually fixed? I am seeing this currently on our MAAS using the 2.9 snap (2.9.2 (9165-g.c3e7848d1))

maas.log shows this for each failed deployment:
2021-04-20T18:29:27.482734+00:00 lxc-maas maas.node: [info] lalande: Status transition from ALLOCATED to DEPLOYING
2021-04-20T18:29:27.796705+00:00 lxc-maas maas.subnet: [warn] Next IP address to allocate from 'Internal-IPs (10.1.10.0/23)' has been observed previously: 10.1.11.231 was last claimed by 00:21:9b:9b:53:1e via eth1 (physical) on lxc-maas at 2021-02-09 16:23:16.398982.
2021-04-20T18:29:28.357973+00:00 lxc-maas maas.subnet: [warn] Next IP address to allocate from 'Internal-IPs (10.1.10.0/23)' has been observed previously: 10.1.11.231 was last claimed by 00:21:9b:9b:53:1e via eth1 (physical) on lxc-maas at 2021-02-09 16:23:16.398982.
2021-04-20T18:29:28.504844+00:00 lxc-maas maas.node: [info] lalande: Aborting DEPLOYING and reverted to ALLOCATED. Unable to power control the node. Please check power credentials.
2021-04-20T18:29:28.515866+00:00 lxc-maas maas.node: [info] lalande: Status transition from DEPLOYING to ALLOCATED

There is nothing in regiond.log or rackd.log around those timestamps. Nor is there any clue in any other log.