Terraform Runs Marked as Needs Confirmation
Resolved

We have confirmed that the fix deployed resolves the issue.

Wed, Sep 12, 2018, 01:00 AM
(6 years ago)
·
Affected components

No components marked as affected

Updates

Resolved

We have confirmed that the fix deployed resolves the issue.

Wed, Sep 12, 2018, 01:00 AM

Monitoring

We have deployed a fix for the issue and will continue to monitor it.

Wed, Sep 12, 2018, 12:03 AM(56 minutes earlier)

Identified

We have now resolved the issue with runs marked as "Planned" locking the workspace in which they are running. The user interface is still incorrectly marking some runs as "Needs Confirmation", and we are continuing to work on a fix for that issue.

Tue, Sep 11, 2018, 11:33 PM(30 minutes earlier)

Identified

We have identified the commit causing plans with no changes to be marked as “Needs Confirmation” in the UI. Additionally, runs marked as “Planned” may lock the workspace in which they’re running. If the workspace is locked, it is safe to unlock the workspace via the workspace settings page and proceed with any queued or pending plans.

Tue, Sep 11, 2018, 10:16 PM(1 hour earlier)

Identified

We have identified the commit causing plans with no changes to be marked as “Needs Confirmation” in the UI. Additionally, runs marked as “Planned” may lock the workspace in which they’re running. If the workspace is locked, it is safe to unlock the workspace and proceed with any queued or pending plans.

Tue, Sep 11, 2018, 09:58 PM(18 minutes earlier)

Investigating

The user interface is incorrectly marking some runs as "Needs Confirmation". We are investigating.

Tue, Sep 11, 2018, 09:42 PM(15 minutes earlier)