{"id":18833,"date":"2023-07-14T10:02:50","date_gmt":"2023-07-14T14:02:50","guid":{"rendered":"https:\/\/qxf2.com\/blog\/?p=18833"},"modified":"2023-07-14T10:02:50","modified_gmt":"2023-07-14T14:02:50","slug":"issues-using-chef-inspec-with-github-actions","status":"publish","type":"post","link":"https:\/\/qxf2.com\/blog\/issues-using-chef-inspec-with-github-actions\/","title":{"rendered":"Troubleshooting Common Issues when using Chef InSpec with GitHub Actions"},"content":{"rendered":"

At Qxf2<\/a>, we have been using Infrastructure tests at our clients for a while now. We recently came up with the idea of adding some infrastructure tests for our own servers and applications within Qxf2. We used Chef Inspec<\/a> to write and execute our tests. Chef InSpec is a popular open-source framework that helps you test and review your applications and infrastructure. It works by checking if your system matches the way you want it to be, which you can describe using simple and understandable Chef InSpec code. I came up with the idea for this blog when working on automating the process of running the infrastructure tests for our systems, by setting up Chef Inspec to run on Github workflow. I came across a number of issues and some misleading errors which was a bit challenging to fix. So, I decided to write this small post to share some of the issues that I came across and how I was was able to resolve it, so that anyone facing similar issues need not pull their hair searching for solutions.<\/p>\n

Issue 1: Chef InSpec cannot execute without valid licenses<\/h4>\n

1. One common issue that users may encounter when running Chef InSpec with GitHub Actions, is the inability to execute tests due to missing licenses. There can be multiple reasons why you may hit this issue. But, the least expected reason is the way Chef Inspec is installed in your build container.
\n2. Many would use the Github Action “actionshub-chef-install<\/em>“, to try and install Chef Inspec. However, this leads to the error, “Chef InSpec cannot execute without valid licenses<\/em><\/code>“, despite accepting the license Chef license.
\n

\"License<\/a>
GitHub Workflow failing with a license error<\/figcaption><\/figure>
\n3. If you are facing a similar issue you can simply fix it by downloading and installing Chef Inspec using the cURL<\/em> command rather than using any prebuilt Github actions for it. <\/p>\n
\r\n    - name: \"Install Chef Inspec\"\r\n      run: curl https:\/\/omnitruck.chef.io\/install.sh | sudo bash -s -- -P inspec\r\n<\/pre>\n
4. In addition, do not forget to accept the Chef license. To do so, you can simply create an environment variable “CHEF_LICENSE<\/em>” and set the value “accept-silent<\/em>” to it.<\/p>\n
\r\n    env:\r\n      CHEF_LICENSE: accept-silent \r\n<\/pre>\n
Issue 2: Client error, can’t connect to “ssh” backend: Your SSH Agent has no keys added, and you have not specified a password or a key file<\/h4>\n
1. Chef Inspec uses SSH for connecting to remote systems and running the tests. For this, we need the authentication key used to connect to the host system. We usually store this key in the Github Secrets. However, when we try passing this Secret directly in the SSH command like below we would hit an error:<\/p>\n
\r\ninspec exec survey_frontend_tests --input-file ubuntu_tests\/input.yaml -t ssh:\/\/ubuntu@12.345.67.890 -i ${{ secrets.SURVEY_FRONTEND_KEY }}\r\n<\/pre>\n
The above command would give us  a client error:”can't connect to 'ssh' backend: Your SSH Agent has no keys added, and you have not specified a password or a key file<\/em><\/code>“.
\n
\"SSH<\/a>
GitHub Workflow failing with SSH error<\/figcaption><\/figure>
\n2. This is because the SSH command cannot directly read the key from the Secrets and the key needs to be stored in a new file with the right permissions. We can do this by simply adding a step in our workflow to save the key from the Secrets to a new file and setting the required permissions for it<\/p>\n
\r\n    - name: Set the Instance key\r\n      run: |\r\n        echo \"${{ secrets.SURVEY_FRONTEND_KEY }}\" | tr -d '\\r' > key.pem\r\n        chmod 400 key.pem\r\n<\/pre>\n
3. We can then use this newly created key file in our SSH command to resolve our issue.<\/p>\n
\r\ninspec exec survey_frontend_tests --input-file survey_frontend_tests\/input.yaml -t ssh:\/\/ubuntu@12.345.67.890 -i key.pem \r\n<\/pre>\n
 Issue 3: GitHub workflow failing when there are skips in your tests<\/h4>\n
1. Another interesting issue that I stumbled upon is that, the  GitHub workflow fails when any of the tests in our Chef InSpec profile is skipped. You may be wondering why this happens. This is because when there are skipped tests, the exit status of your test run would be ‘101<\/strong>‘.
\n2. GitHub workflow interprets any status code other than 0 as a failure. Therefore when there are skipped tests in your test run the overall workflow status gets marked as failed.
\n
\"Chef<\/a>
GitHub Workflow failing when one or more tests are skipped.<\/figcaption><\/figure>
\n3. We can resolve this issue by setting Chef InSpec to return only two distinct exit codes. ‘0’ on failure and ‘1’ on success. We can achieve this by passing the –no-distinct-exit<\/em> flag when executing our Chef InSpec tests. This ensures that the skipped tests does not cause the test run to exit with a non-zero status unless there is an actual failure.<\/p>\n
\r\ninspec exec survey_frontend_tests --input-file survey_frontend_tests\/input.yaml -t ssh:\/\/ubuntu@12.345.67.890 -i key.pem --no-distinct-exit \r\n<\/pre>\n
Bonus: Publishing InSpec results on Netlify<\/h4>\n
1. As part of your Chef InSpec workflow, you may want to publish the test results somewhere, let’s say Netlify<\/a>. To do this this we first need to save our test results into a htm<\/code>l file. We can simply use the –reporter<\/em> flag of Chef Inspec to achieve this. <\/p>\n
\r\ninspec exec survey_frontend_tests --input-file survey_frontend_tests\/input.yaml -t ssh:\/\/ubuntu@12.345.67.890 -i key.pem --no-distinct-exit --reporter=cli html:.\/test_report\/index.html\r\n<\/pre>\n
2. We then need to add a new site in our Netlify account and set the NETLIFY_AUTH_TOKEN<\/strong> and NETLIFY_SITE_ID<\/strong>. We won’t be going into the details of the setup procedure here. You can refer the following<\/a> blog post for more information on setting up your Netlify account
\n3. Once we have our Netlify account setup, We can then use a Github action ‘nwtgck\/actions-netlify<\/em>‘ to deploy our html file on it.<\/p>\n
\r\n    - name: Deploy DataDocs to Netlify\r\n      if: always()\r\n      uses: nwtgck\/actions-netlify@v1.2\r\n      with:\r\n        publish-dir: \".\/test_report\"\r\n        production-deploy: true\r\n      env:\r\n        NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}\r\n        NETLIFY_SITE_ID: ${{ secrets.NETLIFY_SITE_ID }}\r\n      timeout-minutes: 1\r\n<\/pre>\n
\"Output<\/a>
Successful publication of InSpec test results on Netlify<\/figcaption><\/figure>\n
I hope you found this post helpful in resolving some of your issues. Also, keep an eye out! We have more posts on testing Infrastructure coming out soon.<\/p>\n
\n
Hire technical testers from Qxf2<\/h4>\n
Hiring Qxf2 brings the advantage of working with technical testers who go beyond traditional test automation practices. Our diverse skill set and expertise enable us to solve critical testing challenges and help teams iterate quickly and confidently. With our focus on early-stage products and modern technical stacks, we provide valuable insights and contribute to the success of your software development projects. Contact us<\/a>!<\/p>\n
\n","protected":false},"excerpt":{"rendered":"
At Qxf2, we have been using Infrastructure tests at our clients for a while now. We recently came up with the idea of adding some infrastructure tests for our own servers and applications within Qxf2. We used Chef Inspec to write and execute our tests. Chef InSpec is a popular open-source framework that helps you test and review your applications […]<\/p>\n","protected":false},"author":29,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[367,301,316,366,1],"tags":[],"class_list":["post-18833","post","type-post","status-publish","format-standard","hentry","category-chef-inspec","category-github-action","category-infrastructure","category-netlify","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/18833","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/comments?post=18833"}],"version-history":[{"count":39,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/18833\/revisions"}],"predecessor-version":[{"id":18963,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/18833\/revisions\/18963"}],"wp:attachment":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/media?parent=18833"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/categories?post=18833"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/tags?post=18833"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}