Currently, setting an object state to "absent" doesn't account for linked database entries such as tags, IP allocations, rackspace, or parent/child relationships. Although the IP allocation can be handled with the existing module, these cases should be handled natively by the object module. Additional work is required to find all of the relevant references in the racktables schema, and ensure they are cleanly removed when removing an object.
Currently, setting an object state to "absent" doesn't account for linked database entries such as tags, IP allocations, rackspace, or parent/child relationships. Although the IP allocation can be handled with the existing module, these cases should be handled natively by the object module. Additional work is required to find all of the relevant references in the racktables schema, and ensure they are cleanly removed when removing an object.