You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/10/21 11:34:57 UTC
[GitHub] [airflow] priyadarshan1995 opened a new issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
priyadarshan1995 opened a new issue #19129:
URL: https://github.com/apache/airflow/issues/19129
### Apache Airflow version
2.0.2
### Operating System
Linux
### Versions of Apache Airflow Providers
apache-airflow-providers-snowflake==2.2.0
### Deployment
MWAA
### Deployment details
We updated the version of airflow-snowflake-providers to a stable version. WE got the below error:
```
Something bad has happened.
Please consider letting us know by creating a bug report using GitHub.
Python version: 3.7.10
Airflow version: 2.0.2
Node: redact
-------------------------------------------------------------------------------
Error! Please contact server admin.
```
### What happened
We updated the version of airflow-snowflake-providers to a stable version (2.2.0) and redeployed the MWAA instance. After that we arent able to access the airflow UI.
### What you expected to happen
We are not sure.
### How to reproduce
WE added apache-airflow-providers-snowflake in the requirements.txt file
version:2.2.0
### Anything else
_No response_
### Are you willing to submit PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
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
[GitHub] [airflow] uranusjr commented on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948533065
Do you get anything in server logs?
--
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
[GitHub] [airflow] boring-cyborg[bot] commented on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948522944
Thanks for opening your first issue here! Be sure to follow the issue template!
--
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
[GitHub] [airflow] mik-laj commented on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj commented on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948598234
apache-airflow-providers-snowflake==2.2.0 requires Airflow 2.1.0, so you can't use it on MWAA. See: https://airflow.apache.org/docs/apache-airflow-providers-snowflake/stable/index.html#pip-requirements
--
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
[GitHub] [airflow] mik-laj commented on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj commented on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948678464
I'm afraid this is not a problem with Apache Airflow, but with the MWAA which makes many modifications to the webserver to add IAM support. Many users use this provider and encounter no similar problems. Unfortunately, based on your reproduction instruction, it is impossible to reproduce this problem on Vanilla Airflow, so we cannot help.
I would like to add that Snowflake Provider should already be installed in the MWAA environment, but based on the application of several people, this is not true.
https://docs.aws.amazon.com/mwaa/latest/userguide/connections-packages.html
Only MAMA knows what is actually installed in the webserver and how their modifications affect the behavior of the application.
If you have problems that only affect MWAA then you should contact AWS technical support who have more insight and are able to fix the problem.
--
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
[GitHub] [airflow] mik-laj edited a comment on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj edited a comment on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948678464
I'm afraid this is not a problem with Apache Airflow, but with the MWAA which makes many modifications to the webserver to add IAM support. Many users use this provider and encounter no similar problems. Unfortunately, based on your reproduction instruction, it is impossible to reproduce this problem on Vanilla Airflow, so we cannot help.
I would like to add that Snowflake Provider should already be installed in the MWAA environment, but based on the feedback of several people, this is not true.
https://docs.aws.amazon.com/mwaa/latest/userguide/connections-packages.html
Only MAMA knows what is actually installed in the webserver and how their modifications affect the behavior of the application.
If you have problems that only affect MWAA then you should contact AWS technical support who have more insight and are able to fix the problem.
--
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
[GitHub] [airflow] mik-laj commented on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj commented on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948697429
I would like to add that the standard procedure from which to start troubleshooting is updating packages to the latest versions. Only the latest versions are updated and all bug fixes are included. The 6-month-old version of Airflow may contain bugs that are not found in newer versions.
--
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
[GitHub] [airflow] mik-laj commented on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj commented on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948734512
@uranusjr AWS Support should then provide technical support. Google provides technical support for each version [2 years](https://cloud.google.com/composer/docs/concepts/versioning/composer-versions#version_support_dates) after its release to Cloud Composer, and they are then responsible for backporting some patches if the community does not provide patches for a given version.
For example, Google released `composer-1.17.3-airflow-1.10.12` on October 18, 2021, which contains various fixes for bugs reported by their users.
The community is not free technical support for issues that are not directly related to our project. If Google / AWS builds a closed source project that contains various changes/customizations of the source code, we are simply not technically able to help, and in particular to reproduce the bug
--
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
[GitHub] [airflow] uranusjr commented on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948704527
Last time I checked 2.0.2 _is_ the latest MWAA users can get, so 🤷♂️
--
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
[GitHub] [airflow] mik-laj edited a comment on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj edited a comment on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948678464
I'm afraid this is not a problem with Apache Airflow, but with the MWAA which makes many modifications to the webserver to add IAM support. Many users use this provider and encounter no similar problems. Unfortunately, based on your reproduction instruction, it is impossible to reproduce this problem on Vanilla Airflow, so we cannot help.
I would like to add that Snowflake Provider should already be installed in the MWAA environment, but based on the feedback of several people, this is not true.
https://docs.aws.amazon.com/mwaa/latest/userguide/connections-packages.html
Only MAMA knows what is actually installed in the webserver and how their modifications affect the behavior of the application.
If you have problems that only affect MWAA then you should contact AWS technical support who have more insight and are able to troubleshoot and fix the problem.
--
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
[GitHub] [airflow] uranusjr edited a comment on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
uranusjr edited a comment on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948746086
Yeah I fully support that only AWS should be responsible for looking into this, not the community. I'm just responding to the six-month-old part since MWAA customers are stuck (and it's also not the community's fault, it's their choice to use old software from AWS, so if there's any problem they can only blame AWS and whoever made them use MWAA).
--
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
[GitHub] [airflow] mik-laj edited a comment on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj edited a comment on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948678464
I'm afraid this is not a problem with Apache Airflow, but with the MWAA which makes many modifications to the webserver to add IAM support. Many users use this provider and encounter no similar problems. Unfortunately, based on your reproduction instruction, it is impossible to reproduce this problem on Vanilla Airflow, so we cannot help.
I would like to add that Snowflake Provider should already be installed in the MWAA environment, but based on the feedback of several people, this is not true.
https://docs.aws.amazon.com/mwaa/latest/userguide/connections-packages.html
Only MAMA team knows what is actually installed in the webserver and how their modifications affect the behavior of the application.
If you have problems that only affect MWAA then you should contact AWS technical support who have more insight and are able to troubleshoot and fix the problem.
--
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
[GitHub] [airflow] mik-laj commented on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj commented on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948735173
@uranusjr AWS Support should then provide technical support. Google provides technical support for each version [2 years](https://cloud.google.com/composer/docs/concepts/versioning/composer-versions#version_support_dates) after its release to Cloud Composer, and they are then responsible for backporting some patches if the community does not provide patches for a given version.
For example, Google released `composer-1.17.3-airflow-1.10.12` on October 18, 2021, which contains various fixes for bugs reported by their users.
The community is not free technical support for issues that are not directly related to our project. If Google / AWS builds a closed source project that contains various changes/customizations of the source code, we are simply not technically able to help, and in particular to reproduce the bug
--
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
[GitHub] [airflow] uranusjr commented on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
uranusjr commented on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948746086
Yeah I fully support that only AWS should be responsible for looking into this, not the community. I'm just responding to the six-month-old part since MWAA customers have no choices (and it's also not the community's fault, it's their choice to use old software).
--
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
[GitHub] [airflow] priyadarshan1995 commented on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
priyadarshan1995 commented on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948652339
Even with version apache-airflow-providers-snowflake-1.3.0 we are getting the same error still.
The other packages we used are below
```
Successfully installed PyJWT-1.7.1 PyYAML-5.4.1 asn1crypto-1.4.0 azure-common-1.1.27 azure-core-1.16.0 azure-storage-blob-12.8.1 boto-2.49.0 boto3-1.17.54 botocore-1.20.54 certifi-2021.5.30 cffi-1.14.6 chardet-4.0.0 charset-normalizer-2.0.1 cryptography-3.4.7 greenlet-1.1.0 ibm-db-3.0.4 ibm-db-sa-0.3.6 idna-2.10 importlib-metadata-1.7.0 isodate-0.6.0 jmespath-0.10.0 msrest-0.6.21 ndg-httpsclient-0.5.1 oauthlib-3.1.1 oscrypto-1.2.1 psycopg2-binary-2.8.6 pyOpenSSL-20.0.1 pyasn1-0.4.8 pycparser-2.20 pycryptodomex-3.10.1 python-dateutil-2.8.2 pytz-2021.1 requests-2.26.0 requests-oauthlib-1.3.0 s3transfer-0.4.2 setuptools-57.1.0 six-1.16.0 snowflake-connector-python-2.4.6 snowflake-sqlalchemy-1.2.4 typing-extensions-3.10.0.0 urllib3-1.26.5 watchtower-0.7.3 zipp-3.5.0
```
--
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
[GitHub] [airflow] mik-laj edited a comment on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj edited a comment on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948598234
apache-airflow-providers-snowflake==2.2.0 requires Airflow 2.1.0, so you can't use it on MWAA/Airflow 2.0.2. See: https://airflow.apache.org/docs/apache-airflow-providers-snowflake/stable/index.html#pip-requirements
--
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
[GitHub] [airflow] mik-laj closed issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj closed issue #19129:
URL: https://github.com/apache/airflow/issues/19129
--
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
[GitHub] [airflow] mik-laj removed a comment on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
mik-laj removed a comment on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948735173
@uranusjr AWS Support should then provide technical support. Google provides technical support for each version [2 years](https://cloud.google.com/composer/docs/concepts/versioning/composer-versions#version_support_dates) after its release to Cloud Composer, and they are then responsible for backporting some patches if the community does not provide patches for a given version.
For example, Google released `composer-1.17.3-airflow-1.10.12` on October 18, 2021, which contains various fixes for bugs reported by their users.
The community is not free technical support for issues that are not directly related to our project. If Google / AWS builds a closed source project that contains various changes/customizations of the source code, we are simply not technically able to help, and in particular to reproduce the bug
--
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
[GitHub] [airflow] priyadarshan1995 edited a comment on issue #19129: After updating the the airflow provider , unable to access Airflow UI (MWAA)
Posted by GitBox <gi...@apache.org>.
priyadarshan1995 edited a comment on issue #19129:
URL: https://github.com/apache/airflow/issues/19129#issuecomment-948652339
@mik-laj Even with version apache-airflow-providers-snowflake-1.3.0 we are getting the same error still.
The other packages we used are below
```
Successfully installed PyJWT-1.7.1 PyYAML-5.4.1 asn1crypto-1.4.0 azure-common-1.1.27 azure-core-1.16.0 azure-storage-blob-12.8.1 boto-2.49.0 boto3-1.17.54 botocore-1.20.54 certifi-2021.5.30 cffi-1.14.6 chardet-4.0.0 charset-normalizer-2.0.1 cryptography-3.4.7 greenlet-1.1.0 ibm-db-3.0.4 ibm-db-sa-0.3.6 idna-2.10 importlib-metadata-1.7.0 isodate-0.6.0 jmespath-0.10.0 msrest-0.6.21 ndg-httpsclient-0.5.1 oauthlib-3.1.1 oscrypto-1.2.1 psycopg2-binary-2.8.6 pyOpenSSL-20.0.1 pyasn1-0.4.8 pycparser-2.20 pycryptodomex-3.10.1 python-dateutil-2.8.2 pytz-2021.1 requests-2.26.0 requests-oauthlib-1.3.0 s3transfer-0.4.2 setuptools-57.1.0 six-1.16.0 snowflake-connector-python-2.4.6 snowflake-sqlalchemy-1.2.4 typing-extensions-3.10.0.0 urllib3-1.26.5 watchtower-0.7.3 zipp-3.5.0
```
Can we reopen this issue?
--
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