Chef incident

Customers may be experiencing a disruption to their Chef services

Minor Resolved View vendor source →

Chef experienced a minor incident on September 19, 2019, lasting 1d. The incident has been resolved; the full update timeline is below.

Started
Sep 19, 2019, 04:00 PM UTC
Resolved
Sep 20, 2019, 04:09 PM UTC
Duration
1d
Detected by Pingoru
Sep 19, 2019, 04:00 PM UTC

Update timeline

  1. investigating Sep 19, 2019, 05:12 PM UTC

    Please note that some customers may be experiencing a disruption to their Chef services. We are actively investigating this issue and working on a resolution. We apologize for the disruption and will regularly update this page with a status and resolution timeline.

  2. identified Sep 19, 2019, 07:48 PM UTC

    We have isolated the issue to be failures in Chef client runs whose cookbooks rely on libraries which are not currently available. Mirrors that sync these libraries will also encounter issues. These issues do not impact customer data, privacy or data integrity. We are working to resolve these issues ASAP and will provide a further update shortly.

  3. identified Sep 19, 2019, 08:51 PM UTC

    We will shortly have remediation steps for repairing environments affected by this issue.

  4. monitoring Sep 20, 2019, 01:08 AM UTC

    We have identified a fix and released new versions of relevant cookbooks and libraries. Remediation steps will be shared to customers via our customer success teams.

  5. resolved Sep 20, 2019, 04:09 PM UTC

    We've received independent verification from customers that remediation steps have resolved the issue for their use case(s) and are calling this incident resolved. Please reach out to Chef Support if you experience further problems. The affected gems (chef-sugar, chef-api, stove) have been restored to the rubygems.org site under their original namespaces.