Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status of testing of Apache Airflow 2.5.2rc2 #30028

Closed
32 of 64 tasks
pierrejeambrun opened this issue Mar 10, 2023 · 19 comments
Closed
32 of 64 tasks

Status of testing of Apache Airflow 2.5.2rc2 #30028

pierrejeambrun opened this issue Mar 10, 2023 · 19 comments
Labels
kind:meta High-level information important to the community testing status Status of testing releases

Comments

@pierrejeambrun
Copy link
Member

pierrejeambrun commented Mar 10, 2023

We have a kind request for all the contributors to the latest Apache Airflow RC 2.5.2rc2.

Could you please help us to test the RC versions of Airflow?

Please let us know in the comment if the issue is addressed in the latest RC.

Thanks to all who contributed to the release (probably not a complete list!):
@Gollum999 @snjypl @auvipy @amoghrajesh @antonio-antuan @bharat99k @vchiapaikeo @SamWheating @jose-workpath @tseruga @akrava @Josersanvil @Thomas-McKanna @ashb @SoxMax @bdsoha @vedantlodha @lewijw @hussein-awala @arjunanan6 @dependabot[bot] @yangguoaws @kaxil @Limess @surabathini @jedcunningham @dstandish @pshrivastava27 @ecerulm @ttben @casra-developers @josh-fell @duke8585 @ephraimbuddy @michaelmicheal @farhan0syakir @okayhooni @lorenzomagni @bbovenzi @kolfild26 @potiuk @aliotta @alejandrofm @cosinequanon @enriqueayala @uranusjr @vincbeck @Taragolis

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.
@pierrejeambrun pierrejeambrun added the kind:meta High-level information important to the community label Mar 10, 2023
@eladkal eladkal added the testing status Status of testing releases label Mar 10, 2023
@auvipy
Copy link
Contributor

auvipy commented Mar 11, 2023

how should I report?

@amoghrajesh
Copy link
Contributor

@pierrejeambrun what is the best way to test this?

@pierrejeambrun
Copy link
Member Author

pierrejeambrun commented Mar 11, 2023

@auvipy you can directly report in this issue your findings. And if the change (PR) you tested is working as expected or not. (Or any other issue you noticed in the release candidate)

@amoghrajesh The easiest way is to install the release candidate in a fresh virtualenv, then run airflow in standalone mode and test changes there. (If you have a dev environment for airflow you can also upgrade there and see if everything is working as expected)

@vchiapaikeo
Copy link
Contributor

#29410 is still looking good.

We did see an unrelated issue from #29821 but that seems to be a user error on our end that we need to correct. Thank you @hussein-awala for that fix!

image

image

@amoghrajesh
Copy link
Contributor

amoghrajesh commented Mar 12, 2023

#29756 looks good on the RC build. Performed small multiple tests, one snippet attached to this comment. @pierrejeambrun

RC_testing.mov

@potiuk
Copy link
Member

potiuk commented Mar 12, 2023

To be continued (have to hurry now)

@potiuk
Copy link
Member

potiuk commented Mar 12, 2023

^Xroot@f8d4a86cf3ef:~/airflow# ls -la airflow.cfg
-rw------- 1 root root 51764 Mar 12 11:36 airflow.cfg
⌁ ⌂23.88 [jarek:~/airflow] [airflow-astroid] % ls -la standalone_admin_password.txt
-rw-------  1 jarek  staff  16 Mar 12 12:48 standalone_admin_password.txt

Screenshot 2023-03-12 at 12 58 17

> airflow config get-value celery broker_url
redis://redis:6379/0

rather than exit 1 and:

> airflow config get-value celery broker_url
The section [celery] is not found in config.
  • Update min version of python-deamon to fix containerd file limits #29916 - I've checked that python-daemon installed is 3.0.1 which is good (also to note 3.0.0 that fixed the problem had been yanked by the maintainer as it did not work without setuptools (and it uses packaging now instead). But that should keep the fix released in 3.0.0. @antonio-antuan maybe you could check if the 2.5.2.rc1 fixes the memory issue in your setup (I have no access to my test machine I set it up for testin and travelling for the next few days).

@potiuk
Copy link
Member

potiuk commented Mar 12, 2023

All looks good for my fixes - except the two issues where it "looks" good but I cannot test it easily and I would love to get confirmation :)

@hussein-awala
Copy link
Member

I've tested #29076, #29212, #29451, #29606, #29821 and they all look good.

@BMFH
Copy link
Contributor

BMFH commented Mar 12, 2023

I've checked #29054. It works fine.

@Josersanvil
Copy link
Contributor

Tested #29791 in the 2.5.2rc1 docker tag and it looks good 🙂

@josh-fell
Copy link
Contributor

#29399 and #29545 look good!

@bbovenzi
Copy link
Contributor

#29066, #29703, #29367, #29042, and #29600 look good

@SamWheating
Copy link
Contributor

Tested #29860 in breeze after pulling the 2.5.2rc1 tag, looks like it works as expected.

Tried to create a DAGRun from an inactive DAG, and got a 404 rather than a 500:

curl -X POST localhost:8080/api/v1/dags/data_warehouse_dag_o259owoo3s/dagRuns -d '{"dag_run_id":"string2","logical_date":"2019-08-24T14:15:24Z","execution_date":"2019-08-24T14:15:24Z","conf":{},"note":"strings"}'  -H 'Content-Type: application/json'

{
  "detail": "DAG with dag_id: 'data_warehouse_dag_o259owoo3s' not found",
  "status": 404,
  "title": "DAG not found", 
  "type": "https://airflow.apache.org/docs/apache-airflow/2.5.2/stable-rest-api-ref.html#section/Errors/NotFound"                       
}

@pierrejeambrun
Copy link
Member Author

A bug was found in rc1 that necessitate an rc2 (constraints). I think we can safely assume that what was tested for rc1 is still working in rc2. Feel free to do more testing. The issue has been updated to target 2.5.2rc2

@pierrejeambrun pierrejeambrun changed the title Status of testing of Apache Airflow 2.5.2rc1 Status of testing of Apache Airflow 2.5.2rc2 Mar 13, 2023
@akrava
Copy link
Contributor

akrava commented Mar 14, 2023

Tested #29454 in 2.5.2rc2, looks good.

@okayhooni
Copy link
Contributor

okayhooni commented Mar 14, 2023

Tested #29056 (minor fix for handling error on cluster policy itself) and looks good.
image

But i think it's better to use repr(e) than str(e) for showing error class name on web UI message.

self.import_errors[dag.fileloc] = str(e) -> self.import_errors[dag.fileloc] = repr(e)

could I modify this line now?

@pierrejeambrun
Copy link
Member Author

Thanks to everyone that helped testing 2.5.2rc1 and 2.5.2rc2. 🙏

Closing as 2.5.2 has been released based on 2.5.2rc2 🎉

@josh-fell
Copy link
Contributor

🎉 Thanks for organizing @pierrejeambrun!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:meta High-level information important to the community testing status Status of testing releases
Projects
None yet
Development

No branches or pull requests