Discoveries are never forgoten

[Ante Karamatić]

On MAAS 2.2b2 I see lots of discovered machine:

ubuntu@maas:~$ maas maas discoveries read | grep resource_uri | wc -l
231

But those machines have not been on the network for extensive time. With the exception of one, all of those machines were even managed by MAAS and deleted within MAAS. This is combination of bare metal machines and LXDs that have been running on those machines, deployed with juju. I don't know if MAAS keeps track of those IPs and, maybe, refuses to issue those IPs to new nodes?

Expectation was that MAAS will not 'discover' nodes that it manages?

[Mike Pontillo (mpontillo)]

I think it's actually useful that MAAS "discover" things that it manages. It's like double-entry accounting that, yes, the machine is using the IP and MAC we thought it would use.

Note that in your case you can clear out all your discoveries and start fresh with:

    maas maas discoveries clear

You can also filter the list of discoveries so that they only include unknown IPs and MACs, like what is shown in the dashboard:

    maas maas discoveries by-unknown-ip-and-mac

[Mike Pontillo (mpontillo)]

Forgot to note: I think it would be good to clear discoveries matching something that gets deleted from MAAS.

For example, if I deploy a machine and juju runs some containers on it, if the machine gets released (and thus, the containers destroyed) we should delete any corresponding discoveries, so that misleading entries do not appear in the dashboard.

[Blake Rouse (blake-rouse)]

Does the UI work the same way? Either way I think this is really wierd. Discoveries should only be for machines MAAS does not know about. I was under the impression that is how it worked.

[Mike Pontillo (mpontillo)]

This bug made me realize that if you delete a machine or device from MAAS, it will show back up in the list of discoveries. The UI only shows things that MAAS does not know about. (And the API I mentioned, too.)

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team