ironic-neutron-agent orphans old "agents"

[Julia Kreger]

Under normal operation of ironic-neutron-agent, it finds "nodes" and related "baremetal ports", and reports status to Neutron across the message bus.

But a challenge to use/operation is that baremetal nodes go away. Operators delete them, but then fail to "delete the agent entry" in Neutron, which creates confusion.

We should explore to see if the agent can reconcile entries.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/networking-baremetal/+/945500

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/networking-baremetal/+/945500
Committed: https://opendev.org/openstack/networking-baremetal/commit/909af1e850a2fbeb04dd1dc66d2a129ac34fc59f
Submitter: "Zuul (22348)"
Branch: master

commit 909af1e850a2fbeb04dd1dc66d2a129ac34fc59f
Author: aarefiev <email address hidden>
Date: Tue Mar 18 04:32:11 2025 -0700

    Clean up baremetal agents on node delete

    Operators may delete ironic node, but related neutron baremetal
    agent entry is left unchanged.

    Clean up old down agents on start up if no related node and delete
    agent when node is deleted.

    Co-Authored-By: Harald Jensås <email address hidden>
    Depends-On: I9db166e9b610f0bafc2be5351f3b79c4c2251664
    Related-Bug: 2086640
    Change-Id: Id8c5ca3923a8d00f9902308625bdea8484dc3fac