Opinie (Serverless Data Processing with Dataflow - CI/CD with Dataflow)

Nikolaos K. · Sprawdzono około 3 lata temu

Cloud Build fails almost everytime with the error 'NoneType'.

Sergey T. · Sprawdzono około 3 lata temu

Syed H. · Sprawdzono około 3 lata temu

Priyanka K. · Sprawdzono około 3 lata temu

please fix soon

Shabaz S. · Sprawdzono około 3 lata temu

Dwaragadeesh R. · Sprawdzono około 3 lata temu

I don't know why gcloud is crashing. I will investigate further.

Nixon M. · Sprawdzono około 3 lata temu

data-pipline-composer Build doesn't complete in 15 minutes It takes longer or fails but what does that mean? It did not complete even after 30 minutes, and the build had already failed 3 times... Execution of the command ended in failure student_03_f4c9967d291c@cloudshell:~/ci-cd-for-data-processing-workflow/env-setup (qwiklabs-gcp-04-9a8c247344cc)$ gcloud composer environments create $COMPOSER_ENV_NAME \ --location $COMPOSER_REGION \ --zone $COMPOSER_ZONE_ID \ --python-version 3 Waiting for [projects/qwiklabs-gcp-04-9a8c247344cc/locations/us-central1/environments/data-pipeline-composer] to be created with [projects/qwiklabs-gcp-04-9a8c247344cc/locati ons/us-central1/operations/4e089d42-2a1b-4dbe-84fd-5856811a1679]...failed. ERROR: (gcloud.composer.environments.create) Error creating [projects/qwiklabs-gcp-04-9a8c247344cc/locations/us-central1/environments/data-pipeline-composer]: Operation [projects/qwiklabs-gcp-04-9a8c247344cc/locations/us-central1/operations/4e089d42-2a1b-4dbe-84fd-5856811a1679] failed: CREATE operation failed. Errors in: [Web server]; Error messages: Failed to deploy the Airflow web server. This might be a temporary issue. You can retry the operation later. If the issue persists, it might be caused by problems with permissions or network configuration. For more information, see https://cloud.google.com/composer/docs/troubleshooting-environment-creation. An internal error occurred while processing task /app-engine-flex/flex_await_healthy/flex_await_healthy>2022-11-25T10:08:29.744Z310160.in.0: Your deployment has failed to become healthy in the allotted time and therefore was rolled back. If you believe this was an error, try adjusting the 'app_start_timeout_sec' setting in the 'readiness_check' section. student_03_f4c9967d291c@cloudshell:~/ci-cd-for-data-processing-workflow/env-setup (qwiklabs-gcp-04-9a8c247344cc)$ (qwiklabs-gcp-02-03e22725a907)$ gcloud composer environments create $COMPOSER_ENV_NAME \ --location $COMPOSER_REGION \ --zone $COMPOSER_ZONE_ID \ --python-version 3 Waiting for [projects/qwiklabs-gcp-02-03e22725a907/locations/us-central1/environments/data-pipeline-composer] to be created with [projects/qwiklabs-gcp-02-03e22725a907/locations/us-central1/o perations/02396047-249e-41a3-b80a-4f4e8d974c6b]...failed. ERROR: (gcloud.composer.environments.create) Error creating [projects/qwiklabs-gcp-02-03e22725a907/locations/us-central1/environments/data-pipeline-composer]: Operation [projects/qwiklabs-gcp-02-03e22725a907/locations/us-central1/operations/02396047-249e-41a3-b80a-4f4e8d974c6b] failed: CREATE operation failed. Errors in: [Web server]; Error messages: Failed to deploy the Airflow web server. This might be a temporary issue. You can retry the operation later. If the issue persists, it might be caused by problems with permissions or network configuration. For more information, see https://cloud.google.com/composer/docs/troubleshooting-environment-creation. An internal error occurred while processing task /app-engine-flex/flex_await_healthy/flex_await_healthy>2022-11-27T01:24:45.468Z54794.jc.1: Your deployment has failed to become healthy in the allotted time and therefore was rolled back. If you believe this was an error, try adjusting the 'app_start_timeout_sec' setting in the 'readiness_check' section. student_03_09c9de2485de@cloudshell:~/ci-cd-for-data-processing-workflow/env-setup (qwiklabs-gcp-02-03e22725a907)$ -- (qwiklabs-gcp-02-03e22725a907)$ gcloud composer environments create $COMPOSER_ENV_NAME \ --location $COMPOSER_REGION \ --zone $COMPOSER_ZONE_ID \ --python-version 3 Waiting for [projects/qwiklabs-gcp-02-03e22725a907/locations/us-central1/environments/data-pipeline-composer] to be created with [projects/qwiklabs-gcp-02-03e22725a907/locations/us-central1/o perations/67734c7a-3685-415a-8b74-a5b3eaf51f09]...failed. ERROR: (gcloud.composer.environments.create) Error creating [projects/qwiklabs-gcp-02-03e22725a907/locations/us-central1/environments/data-pipeline-composer]: Operation [projects/qwiklabs-gcp-02-03e22725a907/locations/us-central1/operations/67734c7a-3685-415a-8b74-a5b3eaf51f09] failed: CREATE operation failed. Errors in: [Web server]; Error messages: Failed to deploy the Airflow web server. This might be a temporary issue. You can retry the operation later. If the issue persists, it might be caused by problems with permissions or network configuration. For more information, see https://cloud.google.com/composer/docs/troubleshooting-environment-creation. An internal error occurred while processing task /app-engine-flex/flex_await_healthy/flex_await_healthy>2022-11-27T02:08:28.283Z54901.jf.2: Your deployment has failed to become healthy in the allotted time and therefore was rolled back. If you believe this was an error, try adjusting the 'app_start_timeout_sec' setting in the 'readiness_check' section. student_03_09c9de2485de@cloudshell:~/ci-cd-for-data-processing-workflow/env-setup (qwiklabs-gcp-02-03e22725a907)$ -- CREATE operation on this environment failed 10 minutes ago with the following error message: CREATE operation failed. Errors in: [Web server]; Error messages: Failed to deploy the Airflow web server. This might be a temporary issue. You can retry the operation later. If the issue persists, it might be caused by problems with permissions or network configuration. For more information, see https://cloud.google.com/composer/docs/troubleshooting-environment-creation. An internal error occurred while processing task /app-engine-flex/flex_await_healthy/flex_await_healthy>2022-11-27T02:08:28.283Z54901.jf.2: Your deployment has failed to become healthy in the allotted time and therefore was rolled back. If you believe this was an error, try adjusting the 'app_start_timeout_sec' setting in the 'readiness_check' section.

Kano T. · Sprawdzono około 3 lata temu

good lab

Amit J. · Sprawdzono około 3 lata temu

Nikolaos K. · Sprawdzono około 3 lata temu

Errors chmod +x set_composer_variables.sh ./set_composer_variables.sh kubeconfig entry generated for us-central1-data-pipeline-c-40b4f095-gke. Executing within the following Kubernetes cluster namespace: composer-1-20-0-airflow-1-10-15-40b4f095 [2022-12-07 15:49:02,061] {configuration.py:732} INFO - Reading the config from /etc/airflow/airflow.cfg [2022-12-07 15:49:02,207] {configuration.py:732} INFO - Reading the config from /etc/airflow/airflow.cfg 15 of 15 variables successfully updated. ERROR: gcloud crashed (TypeError): 'NoneType' object is not callable can not complete

Rodrigo A. · Sprawdzono około 3 lata temu

Another failed lab environment. Can't get past Task 5. "Step #6 - "set-composer-jar-ref": ERROR: gcloud crashed (TypeError): 'NoneType' object is not callable"

Brian S. · Sprawdzono około 3 lata temu

Getting error in creating cloud build pipelines

Rahul D. · Sprawdzono około 3 lata temu

Nikolaos K. · Sprawdzono około 3 lata temu

Build not work. ERROR: gcloud crashed (TypeError): 'NoneType' object is not callable

Juan Luis H. · Sprawdzono około 3 lata temu

please fix soon

Shabaz S. · Sprawdzono około 3 lata temu

Getting error in creating cloud build pipelines

Rahul D. · Sprawdzono około 3 lata temu

Roger V. · Sprawdzono około 3 lata temu

Actually broken. Task 5 fails due to NoneType error in step 6 of the pipeline workflow. Fix your tools so people trying to learn don't have to spend the entire limited lab time troubleshooting

Adrian F. · Sprawdzono około 3 lata temu

Eilidh M. · Sprawdzono około 3 lata temu

There are issues gcloud build, it is failing when executing kubernetes after step 6 "set-composer-jar-ref". I could not complete the lab because of the continuous failure

Ali M. · Sprawdzono około 3 lata temu

Pratap K. · Sprawdzono około 3 lata temu

Lab is broken

Victor S. · Sprawdzono około 3 lata temu

Something is wrong with the gcloud Cloud Build containers so the lab fails

Brendan O. · Sprawdzono około 3 lata temu

build failed no matter how many times it was run

Brock M. · Sprawdzono około 3 lata temu