hostname starts with future-, or contains -spare and state is active, is a failure.
|operations/software/netbox-reports : master||coherence: Alert on ACTIVE devices with names future- or spare.|
Some discussion occurred on the CR. Should we detect future and spare anywhere in the hostname? I was under the impression that this is not normal nor should we entrench it as a standard practice by checking for it. (The case of spare being inside the hostname turned out to be, essentially, in error afair).
Not sure if it can be considered in scope for this task as the title is pretty generic.
Another check we need is to ensure that the hostname part of some DNS names matches the device name, in particular:
- mgmt ip address
We have cases of host renames that leftover some inconsistency there.
With the soon-to-be DNS autogenerated from Netbox data those errors should surface pretty quickly before going into prod, but probably better to have the check anyway.