Engine Yard incident

Stack Configuration Outage

Major Resolved View vendor source →

Engine Yard experienced a major incident on July 2, 2018 affecting Engine Yard Cloud, lasting 4d 4h. The incident has been resolved; the full update timeline is below.

Started
Jul 02, 2018, 05:03 PM UTC
Resolved
Jul 06, 2018, 09:47 PM UTC
Duration
4d 4h
Detected by Pingoru
Jul 02, 2018, 05:03 PM UTC

Affected components

Engine Yard Cloud

Update timeline

  1. identified Jul 02, 2018, 05:03 PM UTC

    There is currently an outage that is preventing chef configuration runs from completing successfully on the Platform. Your applications are not directly impacted, but you may be unable to boot instances or modify the configuration of your running environment. Our Engineering and Support teams are working to restore functionality as quickly as possible.

  2. identified Jul 02, 2018, 11:43 PM UTC

    Functionality for the Stable-v5 stack has been fully restored at this time. Work on the Stable-v4 stacks is still underway. Efforts to restore functionality for EOL stacks will begin once Stable-v4 has been fully restored.

  3. identified Jul 03, 2018, 05:26 AM UTC

    Stable-v4 stack versions 2.0.126 and higher have been restored to normal functionality. Work against older versions of Stable-v4 is ongoing.

  4. identified Jul 04, 2018, 05:55 AM UTC

    In addition to all of Stable-v5, functionality has now been restored to Stable-v4 versions 2.0.84 and above as well as to Stable-v1 versions 1.1.422 and above. All supported stack versions are expected to be fully functional by end of day July 4th, End Of Life Stack versions should be restored by Saturday, July 9th.

  5. identified Jul 04, 2018, 10:45 PM UTC

    Functionality has now been restored to Stable-v4 versions 2.0.28 to 2.0.46 as well as to Stable-v2 versions 1.1.413 and above. Work continues on the remaining supported versions of the stack.

  6. identified Jul 05, 2018, 09:59 PM UTC

    All versions of stack Stable-v4 have now been restored, as well as Stable-v2 versions 1.1.81 and above. Work continues on the remaining versions of Stable-v2 and Stable-v1.

  7. resolved Jul 06, 2018, 09:47 PM UTC

    All current generation stacks are fully recovered at this time (Stable-v4, Stable-v5). Work continues on a handful of End of Life stacks at this time, but since the Supported stacks are complete we are marking this incident Resolved at this time. If you are experiencing any trouble with your environment please open a ticket for our Support team.