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/07/05 12:22:31 UTC
[GitHub] [airflow] harvetech opened a new issue #16813: UrlParse not defined Failed to create a workload
harvetech opened a new issue #16813:
URL: https://github.com/apache/airflow/issues/16813
Dear all, I am trying to install airflow on a Kubernetes cluster managed by the open Telekom Deutschland. I am using the chart available here but I am getting an error at` line 162` in `webserver-deployment.yaml `that urlParse is not defined. Can somebody please guide me on what should I do?
--
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] potiuk closed issue #16813: UrlParse not defined Failed to create a workload
Posted by GitBox <gi...@apache.org>.
potiuk closed issue #16813:
URL: https://github.com/apache/airflow/issues/16813
--
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] potiuk commented on issue #16813: UrlParse not defined Failed to create a workload
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #16813:
URL: https://github.com/apache/airflow/issues/16813#issuecomment-874178660
The description is far too vague - you have not provided details on how your deployment look like nor what you have done so far to analyse the problem. The chart is used and tested in production so it's unlikely we will be able to help without knowing more about your deployment, configuration, changes, which versions of which charts, images, airflow, and with what configuration you used. There is a good reason we provide template for issues of different kind (especially Bug has a lot of information to be filled in).
Also, unless you have a concrete bug and reproduction path, it's better to open a discussion for ti (see Discussions list at the top) rather than issue. I am closing this for now, can you please open it in discussion and provide more context? Otherwise I am afraid not much can be done. I am closing this one as invalid, and kindly ask you to open discussion and provide more details there.
--
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] potiuk closed issue #16813: UrlParse not defined Failed to create a workload
Posted by GitBox <gi...@apache.org>.
potiuk closed issue #16813:
URL: https://github.com/apache/airflow/issues/16813
--
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] potiuk commented on issue #16813: UrlParse not defined Failed to create a workload
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #16813:
URL: https://github.com/apache/airflow/issues/16813#issuecomment-874178660
The description is far too vague - you have not provided details on how your deployment look like nor what you have done so far to analyse the problem. The chart is used and tested in production so it's unlikely we will be able to help without knowing more about your deployment, configuration, changes, which versions of which charts, images, airflow, and with what configuration you used. There is a good reason we provide template for issues of different kind (especially Bug has a lot of information to be filled in).
Also, unless you have a concrete bug and reproduction path, it's better to open a discussion for ti (see Discussions list at the top) rather than issue. I am closing this for now, can you please open it in discussion and provide more context? Otherwise I am afraid not much can be done. I am closing this one as invalid, and kindly ask you to open discussion and provide more details there.
--
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