StaticIPAddress matching query does not exist.

This is happening on 3.3.2 during an Openstack deployment.

I reduced my entire bucektsconfig to 1 line, and I still get this error, even when cleaning all machines and starting from scratch without any prior config:

disks: []
nics:
  - { id: ens1f0, name: ens1f0, nic: 4, subnets: [], type: physical, fabric: openstack, vlan_id: 0, mtu: 9000 }

This is enough to give me:

ubuntu@brtlvmrs0763co:~/2023-01-30-Telefonica-OCS5-PedroGusso-OP-237579$ fce --debug build --layer maas --steps maas:configure_nodes
2023-04-12-15:16:27 root DEBUG fce --debug build --layer maas --steps maas:configure_nodes
2023-04-12-15:16:27 root DEBUG FCE version: 2.18.2
2023-04-12-15:16:27 root DEBUG [localhost]: juju export-bundle -m foundations-maas:lma-maas
2023-04-12-15:16:27 root ERROR [localhost] Command failed: juju export-bundle -m foundations-maas:lma-maas
2023-04-12-15:16:27 root ERROR [localhost] STDOUT follows:
b''
2023-04-12-15:16:27 root ERROR [localhost] STDERR follows:
ERROR controller foundations-maas not found

2023-04-12-15:16:27 root DEBUG [localhost]: juju export-bundle -m foundations-maas:openstack
2023-04-12-15:16:27 root ERROR [localhost] Command failed: juju export-bundle -m foundations-maas:openstack
2023-04-12-15:16:27 root ERROR [localhost] STDOUT follows:
b''
2023-04-12-15:16:27 root ERROR [localhost] STDERR follows:
ERROR controller foundations-maas not found

2023-04-12-15:16:27 root DEBUG Running 'zone' project check
2023-04-12-15:16:27 fce.build INFO Started building layer: maas
2023-04-12-15:16:30 fce.maas INFO Starting step: maas:configure_nodes
2023-04-12-15:16:30 root DEBUG [localhost]: maas root machines read hostname=brtlvmrs0754co domain=maas
2023-04-12-15:16:33 root DEBUG [localhost]: maas root tags create name=control-nodes
2023-04-12-15:16:35 root ERROR [localhost] Command failed: maas root tags create name=control-nodes
2023-04-12-15:16:35 root ERROR [localhost] STDOUT follows:
{"name": ["Tag with this Name already exists."]}
2023-04-12-15:16:35 root ERROR [localhost] STDERR follows:
b''
2023-04-12-15:16:35 root DEBUG [localhost]: maas root tag update-nodes control-nodes add=aws7he
2023-04-12-15:16:36 root INFO Applying config 'control-nodes' to 'brtlvmrs0754co.maas'
2023-04-12-15:16:36 root DEBUG [localhost]: maas root machines read hostname=brtlvmrs0754co domain=maas
2023-04-12-15:16:39 root INFO Skipping storage configuration.
2023-04-12-15:16:39 root INFO Setting up networking on 'aws7he'
2023-04-12-15:16:39 root INFO Clearing previous network configuration
2023-04-12-15:16:39 root DEBUG [localhost]: maas root machine restore-networking-configuration aws7he
2023-04-12-15:16:43 root ERROR [localhost] Command failed: maas root machine restore-networking-configuration aws7he
2023-04-12-15:16:43 root ERROR [localhost] STDOUT follows:
StaticIPAddress matching query does not exist.
2023-04-12-15:16:43 root ERROR [localhost] STDERR follows:
b''
2023-04-12-15:16:43 root ERROR ('brtlvmrs0754co.maas', 'control-nodes'):Command '['maas', 'root', 'machine', 'restore-networking-configuration', 'aws7he']' returned non-zero exit status 2.
Traceback (most recent call last):
  File "/usr/local/bin/fce", line 33, in <module>
...

Subscribed field-critical on this one since deployment just got blocked.

For some reason, Django attempts to fetch the record by the foreign key, even though it is nullable. Probably because there *was* a value in the first place, although I cannot seem to reproduce that exact failure locally. A hotfix would be to handle the error in `default_gateways`.

Removing field-critical since I have a workaround (re-install with maas 3.2 for now, upgrade again later).

I just moved to MaaS 3.3 on Support's request and now facing the same issue. The issue for me happens when I have static IP's assigned to the node and run maas:configure_nodes steps. The command it fails on maas', 'admin', 'machine', 'restore-networking-configuration'<node-id>. If I go into the maas UI and delete the statically assigned IP then run the step again it works..

I've encountered this on MAAS 3.3.4.

When I configure nodes (with fce) and it executes the restore-networking-configuration sub-command, I get the StaticIPAddress error. I can recreate it at the command-line:

  $ maas root machine restore-networking-configuration fk7ncm
  StaticIPAddress matching query does not exist.

If I recommission that machine and re-run the restore-networking-configuration sub-command, the error goes away but seems to pop up on a different node. I've gone through a few cycles of this whack-a-mole.

I'm not using any static IP addresses.

I have 42 machines. I just recommissioned them all at once and, when done ran the following and had positive results for every machine:

  $ for id in $(maas root machines read | jq -r '.[]|.system_id'); do
      maas root machine restore-networking-configuration $id | grep fqdn;
    done

Then, after running `fce build --layer maas --steps generate_buckets,configure_nodes` I saw no errors.

Why would this give different results than recommissioning individual nodes at a time? Maybe I got lucky?

A less drastic work-around than recommissioning all nodes (or rolling back to 3.2) is the following db update:

  sudo su - maas -c "psql maasdb -c 'update maasserver_node set gateway_link_ipv4_id=null where system_id='\''cpg88q'\'';' "

Where cpg88q is the system id of the node where the restore-networking-configuration command fails.

Subscribing ~field-high.

Basically `maas <PROFILE> machine restore-networking-configuration` is not working. And there is no known workaround unless doing a database surgery or completely removing and re-adding a machine.

This should be available in 3.3/edge: 3.3.5-13208-g.beee034cf for anyone who needs it.

Thanks Chris.

So far I checked also re-commisioning the nodes also help, so that at least cuts the time on enlisting nodes. Looking forward to that change landing in stable.