[ 
https://issues.apache.org/jira/browse/AIRFLOW-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662848#comment-16662848
 ] 

Agustin Lucchetti commented on AIRFLOW-3224:
--------------------------------------------

The 1.10 release is currently broken because flask-appbuilder 1.12.x now 
requires a higher version of flask-login ({{Flask-Login<0.5,>=0.3}}) that 
conflicts with the version defined by airflow ({{flask-login==0.2.11}}), and 
the setup.py requirement definition for the flask-appbuilder package is not 
restrictive enought to force flask-appbuilder to 1.11.x 
(flask-appbuilder>=1.11.1, < 2.0.0) . This bug is not related to kubernetes.

This is fixed on master by this PR: 
[https://github.com/apache/incubator-airflow/pull/3937/commits/7bdea186ee84ed794f4245cd0573322a60c7d041]

> Flask Errors when Installing Airflow 1.10 in Kubernetes
> -------------------------------------------------------
>
>                 Key: AIRFLOW-3224
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3224
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: celery, dependencies, kubernetes, scheduler, webapp
>    Affects Versions: 1.10.0
>            Reporter: Brooke
>            Priority: Blocker
>
> I am currently working on deploying Apache Airflow 1.10.0 to a Kubernetes 
> cluster. I am running into some dependency issues with Flask.
> If I use the current version of flask-login (0.4.1), I receive this error:
> {{apache-airflow 1.10.0 has requirement flask-login==0.2.11, but you'll have 
> flask-login 0.4.1 which is incompatible.}}
> With this error, the UI won't render, and instead, I see a text bomb followed 
> by many flask-appbuilder/flask-login warnings.
> If I use the Airflow's requirement of flask-login (0.2.11), I receive this 
> error:

> {{flask-appbuilder 1.12.0 has requirement Flask-Login<0.5,>=0.3, but you'll 
> have flask-login 0.2.11 which is incompatible.}}
> With this error, the UI renders with Airflow 1.9 features and CeleryExecutor 
> won't work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to