Otter and Buildmaster

[Jon]

I use Otter and BuildMaster together. Otter shares its configuration data with Buildmaster with Otter being the SSOT (single source of truth) and BuildMaster reading only.

I create Roles on Otter for builds that I want to deploy to servers (for instance "Pre-Deployment Servers"). I then add servers to these roles. However, the server will be a member of multiple different roles. For instance it may also be a member of "Patching Thursday" server role. The servers are set to detect and remediate drift immediately.

BuildMaster uses the Pre-Deployment Servers role to deploy a pipeline to. This works very nicely but unfortunately because the servers in the Pre-Deployment Servers have no configuration (the job of the role is just to group servers), when I look on Otter, they constantly look like they are in an "unknown" state because no drift can be detected on the Pre-Deployment role even though the Patching Thursday server role is showing green.

I've tried all sorts of things to try and make them turn Green including on the Pre-Deployment Servers role changing the desired configuration to:

1. Adding a simple PowerShell script with return $true
2. Adding an empty configuration file.
3. Getting it to perform stupid tasks (get the computer name).

Is there anything I can do to fix this?

[philippe.camelio_3885]

Hi @Jon
Based on my experience, you need to add a configuration to each role
like an ensure-file a dummy file to force the drift detection and the remediation for each role.
Having a role without a configuration leave the status in unknown state.

Hope this help
Best regards
PhilippeC.