beascar commented on issue #16176:
URL: https://github.com/apache/airflow/issues/16176#issuecomment-1346953842

   > Without any details while the migration job failed, I am afraid commenting 
on closed issue will not help. You need to see the logs of the job that failed 
and post it (ideally as a new issue as this might be completelty different 
issue).
   
   This are the command I'm using the check the logs of the failed job:
   
   ```
   $ kubectl describe job airflow-run-airflow-migrations
   Name:             airflow-run-airflow-migrations
   Namespace:        airflow
   Selector:         controller-uid=3a6f5bd7-2128-42be-a28d-7a50b215ff3f
   Labels:           chart=airflow-1.7.0
                     component=run-airflow-migrations
                     heritage=Helm
                     release=airflow
                     tier=airflow
   Annotations:      batch.kubernetes.io/job-tracking: 
                     helm.sh/hook: post-install,post-upgrade
                     helm.sh/hook-delete-policy: 
before-hook-creation,hook-succeeded
                     helm.sh/hook-weight: 1
   Parallelism:      1
   Completions:      1
   Completion Mode:  NonIndexed
   Start Time:       Mon, 12 Dec 2022 09:44:39 -0700
   Pods Statuses:    1 Active (0 Ready) / 0 Succeeded / 0 Failed
   Pod Template:
     Labels:           component=run-airflow-migrations
                       controller-uid=3a6f5bd7-2128-42be-a28d-7a50b215ff3f
                       job-name=airflow-run-airflow-migrations
                       release=airflow
                       tier=airflow
     Service Account:  airflow-migrate-database-job
     Containers:
      run-airflow-migrations:
       Image:      apache/airflow:2.4.1
       Port:       <none>
       Host Port:  <none>
       Args:
         bash
         -c
         exec \
         airflow db upgrade
       Environment:
         PYTHONUNBUFFERED:                     1
         AIRFLOW__CORE__FERNET_KEY:            <set to the key 'fernet-key' in 
secret 'airflow-fernet-key'>                      Optional: false
         AIRFLOW__CORE__SQL_ALCHEMY_CONN:      <set to the key 'connection' in 
secret 'airflow-airflow-metadata'>                Optional: false
         AIRFLOW__DATABASE__SQL_ALCHEMY_CONN:  <set to the key 'connection' in 
secret 'airflow-airflow-metadata'>                Optional: false
         AIRFLOW_CONN_AIRFLOW_DB:              <set to the key 'connection' in 
secret 'airflow-airflow-metadata'>                Optional: false
         AIRFLOW__WEBSERVER__SECRET_KEY:       <set to the key 
'webserver-secret-key' in secret 'airflow-webserver-secret-key'>  Optional: 
false
         AIRFLOW__CELERY__BROKER_URL:          <set to the key 'connection' in 
secret 'airflow-broker-url'>                      Optional: false
       Mounts:
         /opt/airflow/airflow.cfg from config (ro,path="airflow.cfg")
     Volumes:
      config:
       Type:      ConfigMap (a volume populated by a ConfigMap)
       Name:      airflow-airflow-config
       Optional:  false
   Events:
     Type    Reason            Age    From            Message
     ----    ------            ----   ----            -------
     Normal  SuccessfulCreate  7m16s  job-controller  Created pod: 
airflow-run-airflow-migrations-wtlzd
   
   $ kubectl logs airflow-run-airflow-migrations-wtlzd
   Error from server (BadRequest): container "run-airflow-migrations" in pod 
"airflow-run-airflow-migrations-wtlzd" is waiting to start: trying and failing 
to pull image
   ```
   
   Looks like my issue is similar to the one described above by @Abhinav1598... 
but unsure which image is the one that is causing the failure.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to