cccs-cat001 opened a new issue #14012:
URL: https://github.com/apache/airflow/issues/14012


   **Apache Airflow version**: 2.0.0
   
   
   **Kubernetes version (if you are using kubernetes)** (use `kubectl 
version`): 
   ```
   Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", 
GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", 
BuildDate:"2020-01-18T23:30:10Z", GoVersion:"go1.13.5", Compiler:"gc", 
Platform:"linux/amd64"}
   Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", 
GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", 
BuildDate:"2020-10-16T20:43:08Z", GoVersion:"go1.15.2", Compiler:"gc", 
Platform:"linux/amd64"}
   ```
   
   **Environment**:
   
   - **Cloud provider or hardware configuration**: Azure
   - **OS** (e.g. from /etc/os-release): 
   - **Kernel** (e.g. `uname -a`):
   - **Install tools**:
   - **Others**:
   
   **What happened**:
   
   The scheduler outputs logs saying it's changing the state of task_instances 
to None. As seen 
[here](https://apache-airflow.slack.com/files/U010X4RLD41/F01LRM0N5M2/image.png)
   
   **What you expected to happen**: Should it not be saying something proper 
like succeeded/failed/queued/scheduled/etc? 
   
   <!-- What do you think went wrong? -->
   
   **How to reproduce it**:
   From what I understand you can launch a new deployment of airflow with a dag 
being scheduled, and the scheduler will output this. 
   
   
   **Anything else we need to know**:
   
   <!--
   
   How often does this problem occur? Once? Every time etc?
   
   Any relevant logs to include? Put them here in side a detail tag:
   <details><summary>x.log</summary> lots of stuff </details>
   
   -->
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to