During registration, systems should link to an existing record if one exists with that mac address.
This comes from a use case of Openstack who has their own provisioning method. A node could be provisioned and registered and then deprovisioned without being unregistered. That same node may be spun up again with the same mac address as previous but will create a new record leading to an explosion of non-existent content host records.
#5 Updated by John Mitsch 9 months ago
- Target version deleted (
- Status changed from New to Rejected
Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.