We are adding Windows nodes to Chef and are running into some issues around case sensitivity.
The hostname portion of the server’s AD FQDN may or may not be uppercase.
If a Windows node has already been registered in Chef with the name MYSERVER.domain.com, someone can still accidentally add myserver.domain.com as a new node.
C:>knife search node “fqdn:servername* OR fqdn:SERVERNAME*”
2 items found
Node Name: servername.mydomain.com
Run List: role[base-chef], role[base-baremetal]
Roles: base-chef, base-baremetal
Recipes: role_base-chef, role_base-baremetal
Platform: windows 6.1.7601
Tags: dba, mssql, group1
Is there a way to tell the server to block registration of a Windows platform node if any case matches an existing node? We can’t rely on people naming hosts consistently…since Windows is a case-insensitive OS, we need to assume that the hostname case will vary and not simply Rely Upon the Kindness Of Strangers Doing the Right Thing.
Paula, still very new at this.