stephsamson opened a new issue #16895:
URL: https://github.com/apache/airflow/issues/16895


   <!--
   
   Welcome to Apache Airflow!  For a smooth issue process, try to answer the 
following questions.
   Don't worry if they're not all applicable; just try to include what you can 
:-)
   
   If you need to include code snippets or logs, please put them in fenced code
   blocks.  If they're super-long, please use the details tag like
   <details><summary>super-long log</summary> lots of stuff </details>
   
   Please delete these comment blocks before submitting the issue.
   
   -->
   
   <!--
   
   IMPORTANT!!!
   
   PLEASE CHECK "SIMILAR TO X EXISTING ISSUES" OPTION IF VISIBLE
   NEXT TO "SUBMIT NEW ISSUE" BUTTON!!!
   
   PLEASE CHECK IF THIS ISSUE HAS BEEN REPORTED PREVIOUSLY USING SEARCH!!!
   
   Please complete the next sections or the issue will be closed.
   These questions are the first thing we need to know to understand the 
context.
   
   -->
   
   **Apache Airflow version**: 2.0.2
   
   
   **Kubernetes version (if you are using kubernetes)** (use `kubectl 
version`): v1.19.10
   
   **Environment**: GKE
   
   - **Cloud provider or hardware configuration**: GCP
   - **OS** (e.g. from /etc/os-release): Debian GNU/Linux 10 (buster)
   - **Kernel** (e.g. `uname -a`): x86_64 GNU/Linux
   - **Install tools**: Helm
   - **Others**:
   
   **What happened**: Configured `values.yaml` to enable remote logging for 
task pods (running KubernetesExecutor)
   with Google Stackdriver [using docs 
here](https://airflow.apache.org/docs/apache-airflow-providers-google/stable/logging/stackdriver.html)
 but running `airflow show` shows the `task_logging_handler` to still be 
`FileTaskHandler` instead of the `StackdriverHandler`.
   
   Relevant `values.yaml` section below:
   
   ```
   ...
   config:
     core:
       executor: KubernetesExecutor
     logging:
       remote_logging: "True"
       remote_base_log_folder: stackdriver://airflow
   ....
   ```
   
   When I check my configmap, these are the results:
   
   ```
   Data
   ====
   airflow.cfg:
   ----
   ...
   [logging]
   colored_console_log = False
   remote_base_log_folder = stackdriver://airflow
   remote_logging = True
   ...
   ```
   
   But when I exec into a scheduler or webserver pod and check the values there 
with `airflow config list`, I get:
   
   ```
   [logging]
   base_log_folder = /opt/airflow/logs
   remote_logging = False
   remote_log_conn_id =
   google_key_path =
   remote_base_log_folder = stackdriver://airflow
   ```
   
   or `airflow config get-value logging remote_logging`, I get `False`.
   
   **What you expected to happen**:
   
   `airflow config get-value logging remote_logging` should return `True`.
   
   **How to reproduce it**:
   
   In your `values.yaml`, add the following section:
   
   ```
   config:
     core:
       executor: KubernetesExecutor
     logging:
       remote_logging: "True"
       remote_base_log_folder: stackdriver://airflow
   ```
   
   Then run ` helm install --generate-name airflow apache-airflow/airflow 
--namespace airflow --debug -f values.yaml`
   


-- 
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: [email protected]

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


Reply via email to