Chef incident

Issue resetting chef keys via id.chef.io, and issues logging into supermarket

Minor Resolved View vendor source →

Chef experienced a minor incident on May 5, 2017 affecting Supermarket, lasting 7h 3m. The incident has been resolved; the full update timeline is below.

Started
May 05, 2017, 04:18 PM UTC
Resolved
May 05, 2017, 11:21 PM UTC
Duration
7h 3m
Detected by Pingoru
May 05, 2017, 04:18 PM UTC

Affected components

Supermarket

Update timeline

  1. identified May 05, 2017, 04:18 PM UTC

    We have identified an issue where users are unable to reset their chef keys on id.chef.io. Users attempting to do so will obtain an empty key instead. We are working on deploying a fix ASAP, but in the meantime you can reset your key from inside chef manage at manage.chef.io. In addition to this, users logging into supermarket are currently receiving errors when viewing their profile page and will be unable to publish to supermarket. Users who are already logged in should be unaffected.

  2. identified May 05, 2017, 05:49 PM UTC

    A fix for the issue has been identified and we are in the process of deploying it.

  3. resolved May 05, 2017, 11:21 PM UTC

    We have deployed a fix for the issue and both key resets and supermarket for newly logged in users should be working normally.