Vespa Cloud - Notice history

The immediate issue has been resolved, we are monitoring the system

We are currently investigating this incident.

In the deployment view this will be shown as
"Unexpected exception running run 474 of <zone> for <tenant>.<application>: Timed out after waiting PT5M to acquire lock '/controller/v1/locks/certificatePool'"

The cost per hour values seen in the application lists will display old values and are currently not being updated. The underlying issue has been identified and a fix is under development.

During the release of vespa-8.362.16 today, we identified failing deployments to test and staging. This failed due to a change that broke provisioning of nodes from AWS.

We are deploying a fix for this now

Some might get "You encountered a bug", with "TypeError: Cannot read properties of undefined (reading 'apiUrl') in the error trace. We will address this as soon as possible.

To work around this issue do a forced refresh.

Due to a failure during the upgrade of our infrastructure today, the upgrade was incomplete and was causing issues for the System Test and Staging Test runs for applications. We have pinned all applications to their current vespa version to work around this.

If you deploy a new application to production, you will be blocked by this. Please reach out to us if you see that your new application is failing deployment in the System Test and Staging Test runs.