Config Track BROKEN

[Michael Holt]

Things are coming together nicely but I'm noticing that Simian is reporting Config Track BROKEN.  What does this mean and what should I do about it (if anything)? Everything appears to be working on the client.

[Justin McWilliams]

Simian looks for a Puppet fact "configtrack", and if it's not present sets the default value to BROKEN: https://github.com/google/simian/blob/fd50692aedf3651aa3ae494d97eb143126ee49d5/src/simian/mac/client/flight_common.py#L475

Maybe we should set this to N/A by default, as not all installs have Puppet...

Thoughts?

On Wed, Jul 22, 2015 at 3:20 AM, Michael Holt <mh...@reallifechurch.org> wrote:

Things are coming together nicely but I'm noticing that Simian is reporting Config Track BROKEN.  What does this mean and what should I do about it (if anything)? Everything appears to be working on the client.

--
You received this message because you are subscribed to the Google Groups "Simian Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simian-discus...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Holt]

ok makes sense. I have Puppet/Facter set up... is this a facter variable I have to set manually? 

[Justin McWilliams]

configtrack is custom/manual.  A best practice if configuration management is to phase deployment across your fleet.  However you bucket/segment your clients, you can build a Facter fact which exposes which bucket a given client is in, and if exposed as configtrack then Simian can report on that.  Like Site/Location, this doesn't unlock much/any functionality within Simian aside from reporting.