Status impact color legend
- Black impact: None
- Yellow impact: Minor
- Red impact: Major
- Blue impact: Maintenance
[Serverless Functions/Containers] Custom domain can end up in error status after updating a function/container
Incident
Report for Scaleway
Resolved
A fix has been deployed and domains wrongfully set in "error" status have been updated to "ready" status.
As noted before, there was no impact on the domain behavior itself, which continued to redirect requests to the users functions/containers. Now, the status of the domain as returned by the API reflects the real status.
Sorry about the inconvenience.
As noted before, there was no impact on the domain behavior itself, which continued to redirect requests to the users functions/containers. Now, the status of the domain as returned by the API reflects the real status.
Sorry about the inconvenience.
Identified
We have discovered that when automatically renewing the TLS certificate for a custom domain, the domain status can wrongfully be set to "error".
However, even if the status is marked in error, there is no impact of the domain itself, who will continue to serve requests and redirect them to the user function/container.
However, even if the status is marked in error, there is no impact of the domain itself, who will continue to serve requests and redirect them to the user function/container.
Investigating
Users with a custom domain on a function/container might see their custom domain end up in an error status after updating the http_option field (with message: "failed to create domain: check that the domain correctly points to the container URL").
This should only happen in this set of circumstances, but we are investigating.
This should only happen in this set of circumstances, but we are investigating.
This incident affected: Elements - Products (Serverless Functions).