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 Providers that were prepared on March 23, 2022 #22480

Closed
8 of 16 tasks
potiuk opened this issue Mar 22, 2022 · 11 comments
Closed
8 of 16 tasks

Status of testing Providers that were prepared on March 23, 2022 #22480

potiuk opened this issue Mar 22, 2022 · 11 comments
Labels
kind:meta High-level information important to the community testing status Status of testing releases

Comments

@potiuk
Copy link
Member

potiuk commented Mar 22, 2022

Body

I have a kind request for all the contributors to the latest provider packages release.
Could you please help us to test the RC versions of the providers?

Let us know in the comment, whether the issue is addressed.

Those are providers that require testing as there were some substantial changes introduced:

Provider amazon: 3.2.0rc1

Provider apache.beam: 3.3.0rc1

Provider cncf.kubernetes: 3.1.2rc1

Provider databricks: 2.5.0rc1

Provider docker: 2.5.2rc1

Provider elasticsearch: 3.0.2rc1

Provider google: 6.7.0rc1

Provider postgres: 4.1.0rc1

Provider snowflake: 2.6.0rc1

The guidelines on how to test providers can be found in

Verify providers by contributors

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.
@potiuk potiuk added the kind:meta High-level information important to the community label Mar 22, 2022
@alexott
Copy link
Contributor

alexott commented Mar 23, 2022

I don't know if it makes sense to release Databricks provider after #22422 is merged?

@raphaelauv
Copy link
Contributor

#22385: @potiuk -> WORK

airlfow 2.1.4 with apache-airflow-providers-cncf-kubernetes==3.1.1

give

[2022-03-23 09:56:34,086] {taskinstance.py:1252} INFO - Exporting the following env vars:
AIRFLOW_CTX_DAG_OWNER=airflow
AIRFLOW_CTX_DAG_ID=kubernetes_dag
AIRFLOW_CTX_TASK_ID=task-one
AIRFLOW_CTX_EXECUTION_DATE=2022-03-14T00:00:00+00:00
AIRFLOW_CTX_DAG_RUN_ID=scheduled__2022-03-14T00:00:00+00:00
[2022-03-23 09:56:34,096] {kubernetes_pod.py:571} ERROR - 'NoneType' object has no attribute 'metadata'
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/airflow/providers/cncf/kubernetes/operators/kubernetes_pod.py", line 368, in execute
    self.pod_request_obj = self.build_pod_request_obj(context)
  File "/usr/local/lib/python3.9/site-packages/airflow/providers/cncf/kubernetes/operators/kubernetes_pod.py", line 524, in build_pod_request_obj
    labels = self._get_ti_pod_labels(context)
  File "/usr/local/lib/python3.9/site-packages/airflow/providers/cncf/kubernetes/operators/kubernetes_pod.py", line 286, in _get_ti_pod_labels
    run_id = getattr(ti, 'run_id') or context['run_id']
AttributeError: 'TaskInstance' object has no attribute 'run_id'

airflow 2.1.4 with apache-airflow-providers-cncf-kubernetes==3.1.2rc1

give

[2022-03-23 09:58:46,424] {taskinstance.py:1252} INFO - Exporting the following env vars:
AIRFLOW_CTX_DAG_OWNER=airflow
AIRFLOW_CTX_DAG_ID=kubernetes_dag
AIRFLOW_CTX_TASK_ID=task-one
AIRFLOW_CTX_EXECUTION_DATE=2022-03-13T00:00:00+00:00
AIRFLOW_CTX_DAG_RUN_ID=scheduled__2022-03-13T00:00:00+00:00
[2022-03-23 09:58:46,428] {kubernetes_pod.py:525} INFO - Creating pod airflow-test-pod.186f4469675a401aa74c57c002ee8be4 with labels: {'dag_id': 'kubernetes_dag', 'task_id': 'task-one', 'run_id': 'scheduled__2022-03-13T0000000000-eef165281', 'try_number': '2'}
[2022-03-23 09:58:46,485] {pod_manager.py:159} WARNING - Pod not yet started: airflow-test-pod.186f4469675a401aa74c57c002ee8be4
[2022-03-23 09:58:47,496] {pod_manager.py:159} WARNING - Pod not yet started: airflow-test-pod.186f4469675a401aa74c57c002ee8be4
[2022-03-23 09:58:48,517] {pod_manager.py:199} INFO - toto

@potiuk
Copy link
Member Author

potiuk commented Mar 23, 2022

I don't know if it makes sense to release Databricks provider after #22422 is merged?

This is a really a bugfix relase with all those things that were merged till yesterday (we have to re-release all packages due to #22380 . We will have another release in about two weeks with only changed providers. I am not sure how fast #22422 is going to be merged, but I do not want to wait with this release as it caused pain already to a number of people and I prefer to relave the pain ASAP.

Also there might be some bugs found in the new change that will make whole databricks provider to be removed from the release and I want to make sure "all" providers are released ASAP due to the#22380 bug.

@potiuk
Copy link
Member Author

potiuk commented Mar 23, 2022

#22385: @potiuk -> WORK

Thanks @raphaelauv! Glad to hear. Next to #22380 this one the one I want to have released asap :) (@alexott - this was also the reason I do not want to wait for any other merges).

@alexott
Copy link
Contributor

alexott commented Mar 23, 2022

Checked #22278 - works as expected

@vincbeck
Copy link
Contributor

#22351 Works!

@josh-fell
Copy link
Contributor

#22371 Looks good.

@pierrejeambrun
Copy link
Member

#22296 is mostly documentation and looks good. (The docker image was build locally and is working) 👍

@potiuk
Copy link
Member Author

potiuk commented Mar 25, 2022

Few more hourse do do more testing :)

@ulsc
Copy link
Contributor

ulsc commented Mar 25, 2022

#22219 works.

@potiuk
Copy link
Member Author

potiuk commented Mar 26, 2022

Thanks everyone. All providers are out !

@potiuk potiuk closed this as completed Mar 26, 2022
@potiuk potiuk added the testing status Status of testing releases label Mar 28, 2022
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

7 participants