Comment 5 for bug 1629061

Not sure why this was still marked Incomplete; this is a well-understood issue.

Another similar issue came up (bug #1630034), where a static IP address (assigned to a node or BMC) somehow became "orphaned" in the database, and was no longer linked to an interface, yet was still "taking up space" as an allocated IP address in MAAS.

While we have not root-caused the reason why the address was "orphaned", I decided to implement a workaround for #1630034 while at the same time fixing this issue.

I plan to enhance the "read" operation so that IP addresses that do not belong to the requesting user can optionally be seen (while also adding support for viewing other allocated address types at the same time).

Also, I plan to add a "force=true" parameter to the 'release' operation so that administrators can forcibly release IP addresses that belong to another user (or are another type), in case "orphaned" IP addresses appear in the database in the future.