amazee.io Status

Resolved: Since we rolled back some components, we have no longer seen issues with volumes getting mounted read-only.

Monitoring: Since the rollback we have no longer seen volumes getting falsely mounted as read-only. We will keep monitoring the situation.

Investigating: As a temporary workaround we are immediately reverting some components to a previous version. The impact of this for workloads is like a regular maintenance.

Investigating: We are investigating multiple cases of volumes that were only mounted in read-only mode leading to failed writes for applications.

While we are working on a permanent solution, please do reach out to our support should you see your application being impacted by this.

Resolved: All potentially affected workloads have been restarted.

Identified: We have updated the impacted regions to include au2.lagoon

Identified: We have rolled out a patch and will restart possibly affected workloads.

Investigating: We are investigating multiple cases of volumes that were only mounted in read-only mode leading to failed writes for applications.

While we are working on a permanent solution, please do reach out to our support should you see your application being impacted by this.

Resolved: Since we rolled back some components, we have no longer seen issues with volumes getting mounted read-only.

Monitoring: Since the rollback we have no longer seen volumes getting falsely mounted as read-only. We will keep monitoring the situation.

Investigating: As a temporary workaround we are immediately reverting some components to a previous version. The impact of this for workloads is like a regular maintenance.

Investigating: We are investigating multiple cases of volumes that were only mounted in read-only mode leading to failed writes for applications.

While we are working on a permanent solution, please do reach out to our support should you see your application being impacted by this.

Resolved: Since we rolled back some components, we have no longer seen issues with volumes getting mounted read-only.

Monitoring: Since the rollback we have no longer seen volumes getting falsely mounted as read-only. We will keep monitoring the situation.

Investigating: As a temporary workaround we are immediately reverting some components to a previous version. The impact of this for workloads is like a regular maintenance.

Investigating: We are investigating multiple cases of volumes that were only mounted in read-only mode leading to failed writes for applications.

While we are working on a permanent solution, please do reach out to our support should you see your application being impacted by this.

Resolved: All potentially affected workloads have been restarted.

Identified: We have updated the impacted regions to include au2.lagoon

Identified: We have rolled out a patch and will restart possibly affected workloads.

Investigating: We are investigating multiple cases of volumes that were only mounted in read-only mode leading to failed writes for applications.

While we are working on a permanent solution, please do reach out to our support should you see your application being impacted by this.

Identified: We are investigating multiple cases of volumes that were only mounted in read-only mode leading to failed writes for applications.

While we are working on a permanent solution, please do reach out to our support should you see your application being impacted by this.

Resolved: Since we rolled back some components, we have no longer seen issues with volumes getting mounted read-only.

Monitoring: Since the rollback we have no longer seen volumes getting falsely mounted as read-only. We will keep monitoring the situation.

Investigating: As a temporary workaround we are immediately reverting some components to a previous version. The impact of this for workloads is like a regular maintenance.

Investigating: We are investigating multiple cases of volumes that were only mounted in read-only mode leading to failed writes for applications.

While we are working on a permanent solution, please do reach out to our support should you see your application being impacted by this.

Resolved: Since we rolled back some components, we have no longer seen issues with volumes getting mounted read-only.

Monitoring: Since the rollback we have no longer seen volumes getting falsely mounted as read-only. We will keep monitoring the situation.

Investigating: As a temporary workaround we are immediately reverting some components to a previous version. The impact of this for workloads is like a regular maintenance.

Investigating: We are investigating multiple cases of volumes that were only mounted in read-only mode leading to failed writes for applications.

While we are working on a permanent solution, please do reach out to our support should you see your application being impacted by this.