Repository navigation
PagerdutyNotifier breaks due to out-dated apache-airflow-providers-pagerduty vesrion #48984
Closed as not planned
Description
Apache Airflow Provider(s)
pagerduty
Versions of Apache Airflow Providers
apache-airflow-providers-pagerduty 4.0
Apache Airflow version
2.10.5
Operating System
Ubuntu
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
What happened
A change in Airflow 2.10.4 (remove create_event method) break PagerdutyEventsHook and PagerdutyNotifier on top of it.
The fix is made and release with apache-airflow-providers-pagerduty>=4.0.1. However, airflow 2.10.5 constraint file still pin version to 4.0.0.
As a a result, PagerdutyEventsHook fail with error
AttributeError: 'PagerdutyEventsHook' object has no attribute 'create_event'
What you think should happen instead
Update airflow 2.10.4 and 2.10.5 constraint file to use apache-airflow-providers-pagerduty 4.0.1.
How to reproduce
Trigger an alert with PagerdutyNotifier.
Anything else
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
boring-cyborg commentedon Apr 8, 2025
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
eladkal commentedon Apr 9, 2025
This is not a bug.
Constraints files are created at release time and never being updated after (unless there is a very good reason). You can always set your own constraints.
https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html#using-your-own-constraints
hongyiw-oai commentedon Apr 9, 2025
According to Airflow’s docs, constraint files exist to ensure reliable and reproducible installs.
Yes, users can override them — but they shouldn't have to, or the constraints lose their reliability. If a default constraint breaks a core provider due to a known issue, that is a problem worth fixing IMHO.
@eladkal Could we please reopen the issue? I am happy to raise a PR.