Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airflow.incubator.apache.org
Date: Tue, 10 May 2016 14:23:12 +0000 (UTC)
From: "nirav pranami (JIRA)" <jira@apache.org>
To: commits@airflow.incubator.apache.org
Message-ID: <JIRA.12965838.1462638816000.153472.1462890192840@Atlassian.JIRA>
In-Reply-To: <JIRA.12965838.1462638816000@Atlassian.JIRA>
References: <JIRA.12965838.1462638816000@Atlassian.JIRA> <JIRA.12965838.1462638816564@arcas>
Subject: [jira] [Updated] (AIRFLOW-67) Problem with SSHExecuteOperator
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 10 May 2016 14:23:17 -0000


     [ https://issues.apache.org/jira/browse/AIRFLOW-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nirav pranami updated AIRFLOW-67:
---------------------------------
    Description: 
Dear Airflow Maintainers,

Before I tell you about my issue, let me describe my Airflow environment:

Airflow version: 1.7.0
Airflow components: CeleryExecutor
Python Version: 2.7.6
Operating System: Centos
Description of Issue

Now that you know a little about me, let me tell you about the issue I am having:
I am not able to see a new dag I wrote on the web-UI. The dag shows up in the *airflow list_dags* output.
I am able to see all other dags that I wrote previously.
The new dag however is not click-able and has the below info.
{quote}
This DAG isn't available in the web server's DagBag object. It shows up in this list because the scheduler marked it as active in the metadata database.
{quote}
I had similar experience with a dag I published before this one. But, that one became available after about a day.


  was:
Dear Airflow Maintainers,

Before I tell you about my issue, let me describe my Airflow environment:

Airflow version: 1.7.0
Airflow components: CeleryExecutor
Python Version: 2.7.6
Operating System: Centos
Description of Issue

Now that you know a little about me, let me tell you about the issue I am having:
I am not able to see a new dag I wrote on the web-UI. The dag shows up in the airflow *list_dags* output.
I am able to see all other dags that I wrote previously.
The new dag however is not click-able and has the below info.
{quote}
This DAG isn't available in the web server's DagBag object. It shows up in this list because the scheduler marked it as active in the metadata database.
{quote}
I had similar experience with a dag I published before this one. But, that one became available after about a day.


> Problem with SSHExecuteOperator
> -------------------------------
>
>                 Key: AIRFLOW-67
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-67
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: nirav pranami
>
> Dear Airflow Maintainers,
> Before I tell you about my issue, let me describe my Airflow environment:
> Airflow version: 1.7.0
> Airflow components: CeleryExecutor
> Python Version: 2.7.6
> Operating System: Centos
> Description of Issue
> Now that you know a little about me, let me tell you about the issue I am having:
> I am not able to see a new dag I wrote on the web-UI. The dag shows up in the *airflow list_dags* output.
> I am able to see all other dags that I wrote previously.
> The new dag however is not click-able and has the below info.
> {quote}
> This DAG isn't available in the web server's DagBag object. It shows up in this list because the scheduler marked it as active in the metadata database.
> {quote}
> I had similar experience with a dag I published before this one. But, that one became available after about a day.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)