Automate 2 version 20181020020209 Released!

Chef Release Announcements
1

We are delighted to announce the availability of version 20181020020209 of Chef Automate 2.

New Features

  • Easier nested page navigation: All "Go back" bars on nested pages have been changed to Breadcrumbs components, which allow the user to see where they are in the application page tree.
  • New BETA feature: Google Cloud API scan support via the integrations and scan jobs screens.

Improvements

  • More data, no problem: Automate migration is improved to be more reliable and stable for systems with a large amount of data.
  • Migration Guard: Automate migration is protected from starting if the data is considered possibly corrupted or malformed.
  • Updated Reporting: Compliance reporting is now rejecting reports with no node_uuid defined.

Bug Fixes

  • Daylight Savings Adjustment: Fixes excess/deficient number of buckets in the Event Feed Guitar Strings control for the weeks that include the beginning or end of daylight saving.
  • Precision Reporting: Scan jobs with more than 100 nodes now accurately report their job status.
  • Hours of Operation: Aborted scan jobs are now updated with an end_time.
  • Ingest Logging: The ingest-service listens to log level configuration. Use either of the below config settings to set the ingest-service log level to debug.
[ingest.v1.sys.log]
level = "debug"

[global.v1.log]
level = "debug"
  • ES Sidecar Logging: The es-sidecar-service listens to log level configuration. Use either of the below config settings to set the es-sidecar-service log level to debug.
[es_sidecar.v1.sys.log]
level = "debug"

[global.v1.log]
level = "debug"
  • Automate Migration Fix: Now updates the Node State from the last chef-client run on disk.
  • CIS RHEL 7 server compliance profiles fixes: Controls 6.2.7 through 6.2.14 will now exclude system users (root, sync, halt, shutdown) from tests, as per CIS procedure.
  • CIS RHEL5 server compliance profiles fixes:
    • Controls, which test service state, now correctly use the be_enabled matcher instead of the non-existent be_disabled matcher.
    • Controls, which CIS does not specify automated tests for, will now result in a skipped result instead of having no code.

How to Upgrade

By default Chef Automate 2 will automatically upgrade to this new version. If you have disabled automatic upgrades you can manually initiate an upgrade by running:

chef-automate upgrade run

As always, we welcome your feedback and invite you to contact us directly or share your feedback online. Thanks for using Chef Automate 2!