Cloud Composer v2 environments autoscaling might not work.

The issue with Google Cloud Composer has been resolved for all affected users as of Friday, 2022-11-18 10:05 US/Pacific. We thank you for your patience while we worked on resolving the issue.

Summary: Cloud Composer v2 environments autoscaling might not work. Description: The issue is partially mitigated. If your environment is impacted by this problem you can upgrade the Composer environment to a newer version to apply the fix. The Composer engineering team continues to work out a solution to apply a fix for the impacted Composer environments. We will provide an update by Friday, 2022-11-18 12:00 US/Pacific with current details. Diagnosis: Number of Airflow workers in the Composer environment won’t change. Workaround: - Check if an upgrade is available for your Composer environment. If it’s available then perform the update operation to the available version. If an upgrade for your environment is not available or you don’t want to perform the update then you can increase the minimum number of workers to the expected level so autoscaling is not needed to process the DAGs/tasks in your Composer environment.

Summary: Cloud Composer v2 environments autoscaling might not work. Description: The issue is partially mitigated. If your environment is impacted by this problem you can upgrade the Composer environment to a newer version to apply the fix. The Composer engineering team continues to work out a solution to apply a fix for the impacted Composer environments. We will provide an update by Friday, 2022-11-18 10:00 US/Pacific with current details. Diagnosis: Number of Airflow workers in the Composer environment won’t change. Workaround: - Check if an upgrade is available for your Composer environment. If it’s available then perform the update operation to the available version. If an upgrade for your environment is not available or you don’t want to perform the update then you can increase the minimum number of workers to the expected level so autoscaling is not needed to process the DAGs/tasks in your Composer environment.

Summary: Cloud Composer v2 environments autoscaling might not work. Description: The issue is partially mitigated. If your environment is impacted by this problem you can upgrade the Composer environment to a newer version to apply the fix. The Composer engineering team continues to work out a solution to apply a fix for the impacted Composer environments. We will provide an update by Friday, 2022-11-18 09:00 US/Pacific with current details. Diagnosis: Number of Airflow workers in the Composer environment won’t change. Workaround: - Check if an upgrade is available for your Composer environment. If it’s available then perform the update operation to the available version. If an upgrade for your environment is not available or you don’t want to perform the update then you can increase the minimum number of workers to the expected level so autoscaling is not needed to process the DAGs/tasks in your Composer environment.

Summary: Cloud Composer v2 environments autoscaling might not work. Description: The issue is partially mitigated. If your environment is impacted by this problem you can upgrade the Composer environment to a newer version to apply the fix. The Composer engineering team continues to work out a solution to apply a fix for the impacted Composer environments. We will provide an update by Friday, 2022-11-18 07:00 US/Pacific with current details. Diagnosis: Number of Airflow workers in the Composer environment won’t change. Workaround: - Check if an upgrade is available for your Composer environment. If it’s available then perform the update operation to the available version. If an upgrade for your environment is not available or you don’t want to perform the update then you can increase the minimum number of workers to the expected level so autoscaling is not needed to process the DAGs/tasks in your Composer environment.

Summary: Cloud Composer v2 environments autoscaling might not work. Description: The issue is partially mitigated. If your environment is impacted by this problem you can upgrade the Composer environment to a newer version to apply the fix. The Composer engineering team continues to work out a solution to apply a fix for the impacted Composer environments so upgrading without a need for performing the upgrade to fix the issue. We will provide an update by Friday, 2022-11-18 05:00 US/Pacific with current details. Diagnosis: Number of Airflow workers in the Composer environment won’t change. Workaround: - Check if an upgrade is available for your Composer environment. If it’s available then perform the update operation to the available version. If an upgrade for your environment is not available or you don’t want to perform the update then you can increase the minimum number of workers to the expected level so autoscaling is not needed to process the DAGs/tasks in your Composer environment.

Summary: Cloud Composer v2 environments autoscaling might not work Description: Composer 2 environments upgraded to newer Composer versions might experience problems with autoscaling. The issue might occur if upgrade operation was performed between October 27th and November 17th. Users should not upgrade Composer environments to newer versions until further notice. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2022-11-17 14:00 US/Pacific with current details. Diagnosis: Airflow workers number will not change. Workaround: Increase the minimum number of workers to the expected level so autoscaling is not needed to process the DAGs/tasks in your Composer environment.

Summary: Cloud Composer v2 environments autoscaling might not work Description: Composer 2 environments upgraded to newer Composer versions might experience problems with autoscaling. The issue might occur if upgrade operation was performed between October 27th and November 17th. Users should not upgrade Composer environments to newer versions until further notice. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2022-11-17 13:00 US/Pacific with current details. Diagnosis: Airflow workers number will not change. Workaround: Increase the minimum number of workers to the expected level so autoscaling is not needed to process the DAGs/tasks in your Composer environment.

Summary: Cloud Composer v2 environments autoscaling might not work Description: Composer 2 environments upgraded to newer Composer versions might experience problems with autoscaling. The issue might occur if upgrade operation was performed between October 27th and November 17th. Users should not upgrade Composer environments to newer versions until further notice. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2022-11-17 10:00 US/Pacific with current details. Diagnosis: Airflow workers number will not change Workaround: None at this time