Update
The migration of storages has been completed, which should prevent further issues with attaching storage. Migration of snapshot data is currently ongoing, so snapshot related activities might still fail to complete successfully.
Update
The first hardware replacement was unsuccessful. Another one is attempted. In the meanwhile a data migration is running to migrate data to another storage target. Due to the amount of data to be migrated the migration is estimated to take several hours.
Update
Hardware replacement was completed. Restoration of redundancy is continuing.
Update
Hardware replacement is being conducted. The team continues to mitigate acute storage provisioning issues until hardware replacement and recovery is completed to minimize customer impact.
Update
The team has encountered a complication during the recovery of the second storage server in the pair. Hardware needs to be replaced. Our datacenter team is working on this task. For customers still affected we are working on implementing a mitigation to unblock storage operations in parallel.
Update
Due to the ongoing restoration effort on the storage server customers might still see residual impact when attaching/detaching storage until redundancy is fully restored. We are resetting the impact of the service back to Degraded Performance.
Monitoring
The incident should now be mitigated. The affected storage server is currently getting restored. Once this is completed, redundancy will be fully restored. We do not see any remaining provisioning issues any longer. We are monitoring the situation and the restoration and will then set the incident to resolved.
Update
We have found an issue with one storage server belonging to a redundant storage server pair. Our team is implementing a mitigation.
Update
While provisioning block could be resolved, we are investigating an increased number of storage related errors. We are directing attention to these remaining issues.
Customers could still see issues with attaching storages on Kubernetes.
Customers could still see issues with attaching storages on Kubernetes.
Update
Storage issue has successfully been resolved, however, job provisioning is currently not progressing successfully. Our provisioning team is investigating.
Update
Our storage team has confirmed the suspected culprit. We are currently mitigating the issue and will monitor provisioning job execution afterwards.
Update
We have narrowed down the issue and believe we have the culprit identified. We are currently confirming the finding.
Identified
We have identified a spike in our provisioning engine queue that is a likely root cause for the issues observed. Our provisioning team is informed and has joined the response.
Update
Initial investigation makes a network connectivity issue unlikely. The team is focusing investigation on Managed Kubernetes side.
Investigating
We are currently investigating a suspected network connectivity issue influencing the MK8s service. We will keep the status page updated with new information as they become available.
This incident affects: Location DE/TXL (Managed Kubernetes).