Issue 1:
Apache Airflow version:

2.2.0.dev0 (possible older versions too)

OS:

Linux Debian 11

(BTW Here we have a typo in comment inside bug report template in .github/ISSUE_TEMPLATE/bug_report.md: cat /etc/oss-release <- double 's'.)

Apache Airflow Provider versions: -

Deployment:

Docker-compose 1.25.0

What happened:

The issue is related to Airflow UI and it shows duplicated notifications when removing all the tags from the input after filtering DAGs.

What you expected to happen:

The notifications should not be duplicated.

How to reproduce it:

In the main view, above the list of the DAGs (just below the top bar menu), there is a place where notifications appear. Suppose that there are 2 notifications (no matter which). Now try to search DAGs by tag using 'Filter DAGs by tag' input and use a valid tag. After the filtering is done, clear the input either by clicking on 'x' next to the tag or on the 'x' near the right side of the input. Notice that the notifications are duplicated and now you have 4 instead of 2 (each one is displayed twice). The input id is s2id_autogen1.

This bug happens only if all the tags are removed from the filtering input. If you remove the tag while there is still another one in the input, the bug will not appear. Also, it is not present while searching DAGs by name using the input 'Search DAGs'.

After search, before removing tags from input:

Duplicated notifications after removing tag from input:

Are you willing to submit a PR?

I can try.

Issue 2:
Apache Airflow version: 2.0.0

Environment:

OS (e.g. from /etc/os-release): RHEL7

Python: 3.8.6

Executor: CeleryExecutor

Workers: 4 worker nodes

logs dir: /opt/airflow/logs/

What happened:

Scenario: Assume there are four workers labeled host_a, host_b, host_c, and host_d. The webserver and scheduler are running on another host host_z. When a task is ran for the first time it executes on host_a and the log file is created locally on that host. If the same task is cleared and ran again, it may execute on another host such as host_b. When navigating back to 1.log after looking at 2.log the webserver replaces hostname from host_a to host_b leading to the log file not being found.

Task runs for first time 1.log is created on host_a

*** Log file does not exist: /opt/airflow/logs/dag_foo/task_bar/2021-05-10T15:54:44.662671+00:00/1.log
*** Fetching from: http://hosta.domain.com:8793/log/dag_foo/task_bar/2021-05-10T15:54:44.662671+00:00/1.log
....

Manually clear and run task again 2.log created on host_b

*** Log file does not exist: /opt/airflow/logs/dag_foo/task_bar/2021-05-10T15:54:44.662671+00:00/2.log
*** Fetching from: http://hostb.domain.com:8793/log/dag_foo/task_bar/2021-05-10T15:54:44.662671+00:00/2.log
.... rest of log

Navigate back to 1.log. Host has been replaced from host_a to host_b hostb.domain.com:8793

*** Log file does not exist: /opt/airflow/logs/dag_foo/task_bar/2021-05-10T15:54:44.662671+00:00/1.log
*** Fetching from: http://hostb.domain.com:8793/log/dag_foo/task_bar/2021-05-10T15:54:44.662671+00:00/1.log
*** Failed to fetch log file from worker. 404 Client Error: NOT FOUND for url: http://hosta.domain.com:8793/log/dag_foo/task_bar/2021-05-10T15:54:44.662671+00:00/1.log

What you expected to happen:

Webserver should remember where a task ran.