Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Unexpected Error when using chef-automate fetcher #258
Ubuntu and Centos, running on default Vagrant test kitchen config (Chef Development Kit Version: 1.4.3, installed on MacOS)
Was attempting to use a trial environment generated via the new Automate Pilot Learn Chef module to get a locally running vagrant VM to fetch and report compliance data to my local Automate instance.
Steps to Reproduce:
Run through the above tutorial to the point where you have an automate server running on your local machine. Via the Compliance UI, select an arbitrary profile to download. I used the linux SSH baseline in my test.
Generate a new cookbook with the stock generator, and make the following updates:
Once complete, simply run a kitchen converge. All default vagrant settings/suites were used.
Compliance scan results for the machine's SSH benchmarks in my local automate server.
Failure to fetch profile, with a header validation error:
This looks to be a conflict between some recent validations added to inspec:
...and an empty header sent via the automate fetcher:
From some conversations with @adamleff, I don't believe the enterprise header to be required to fetch a profile, so I'm going to attempt removing it entirely and test to see if there are any other validations that triggers. If so, will re-try with an arbitrary value (e.g. 'default').