[GitHub] [airflow] potiuk commented on issue #26479: Error in database table "task_fail" while DAGs failed due to some errors in dags.

[GitBox <gi...@apache.org>]

potiuk commented on issue #26479:
URL: https://github.com/apache/airflow/issues/26479#issuecomment-1260603277

   Looks like your database is from old airllow version. I believe your migration job did not run. Likely you have installed upgraded airlfow in some way that provented migration from happening or you killed the job or smth. You need to make sure the migration job runs and this usually happens during instalation. You can look up several issues  here where in some K8S dpeloyments using `--wait` caused problems as `--wait` does not allow the migration job to run and you should likely reinstall aiflow from scratch. This should be no problem as long as your database is remote, you should be able to nuke and reinstall airflow. Then you can use `airflow db` commands to verify if migrations have been applied correctly - see migrations here (https://airflow.apache.org/docs/apache-airflow/stable/migrations-ref.html) and you should be able to verify if the migrations are applied by looking into alembic/DB migration status. 
   
   However If you somehow messed with your DB and manually modified it (which is likely) or if you broke migrations in the middle at some point, the only way to recover is to restore the DB to the moment it was not broken or possibly recreate the DB from scratch.
   
   Also it is not helpful at all to see the whole of your configuration, hard to say what/how/when was modified. You are the only person to know what changes have been applied in what sequence. 
   
   Also some other potential customisations (plugins/settings etc) that might cause the problem. In case you have some modifications you applied, and any custom code added, I suggest to make a "bisect" approach - -start from plain Airlfow chart, image, no code of yours added except simple DAGs, see that it works and add your customisations one-by-one. We are pretty sure stock airflow does not have the problem you have, so some customisation of yours could have solved it.
   
   Convert it into discussion until you do some experimenting witth the above.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org