chore: clarify non existence or not defined pod model file

[enchant3dmango]

Update ambiguous logging.

Related discussions:

• WARNING - Model file /opt/airflow/pod_templates/pod_template_file.yaml does not exist #35419
• KubernetesExecutor Warning: "Model file /opt/airflow/pod_templates/pod_template_file.yaml does not exist" #47135
• `{pod_generator.py:477} WARNING - Model file does not exist` output by every task #47166

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[shivshav]

@enchant3dmango Continuing the conversation from this discussion, I tried running the main branch from your fork (https://github.com/enchant3dmango/airflow/tree/main) to check things out and ran into what seem like an unrelated issue so am not able to verify things

Ultimately, it's scheduler and webserver spitting out some combinations of these errors

Unable to load the config, contains a configuration error.
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/logging/config.py", line 400, in resolve
    found = getattr(found, frag)
            ^^^^^^^^^^^^^^^^^^^^
AttributeError: partially initialized module 'airflow' has no attribute 'sdk' (most likely due to a circular import)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/logging/config.py", line 402, in resolve
    self.importer(used)
ModuleNotFoundError: No module named 'airflow.sdk'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/logging/config.py", line 561, in configure
    filters[name] = self.configure_filter(filters[name])
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/logging/config.py", line 698, in configure_filter
    result = self.configure_custom(config)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/logging/config.py", line 479, in configure_custom
    c = self.resolve(c)
        ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/logging/config.py", line 407, in resolve
    raise v from e
ValueError: Cannot resolve 'airflow.sdk.execution_time.secrets_masker.SecretsMasker': No module named 'airflow.sdk'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/airflow/.local/bin/airflow", line 5, in <module>
    from airflow.__main__ import main
  File "/home/airflow/.local/lib/python3.11/site-packages/airflow/__init__.py", line 78, in <module>
    settings.initialize()
  File "/home/airflow/.local/lib/python3.11/site-packages/airflow/settings.py", line 629, in initialize
    LOGGING_CLASS_PATH = configure_logging()
                         ^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/airflow/logging_config.py", line 74, in configure_logging
    raise e
  File "/home/airflow/.local/lib/python3.11/site-packages/airflow/logging_config.py", line 69, in configure_logging
    dictConfig(logging_config)
  File "/usr/local/lib/python3.11/logging/config.py", line 823, in dictConfig
    dictConfigClass(config).configure()
  File "/usr/local/lib/python3.11/logging/config.py", line 563, in configure
    raise ValueError('Unable to configure '
ValueError: Unable to configure filter 'mask_secrets'

I should note, this happens on a fresh Docker container with no custom configuration even mounted, and I was able to get the source version of 2.10.4 installed and working the same way, so I'm guessing something in main is off?

In any case, I think the combination of the clearer log message and setting it to log.info would be awesome for my use case. I don't wanna waste anyone else's time trying to debug my setup but am happy to continue trying to test if that's desirable 😄

[enchant3dmango]

@shivshav I've changed my mind. In that case, I think we can open another PR. Let's keep it like this for now.

[shivshav]

@shivshav I've changed my mind. In that case, I think we can open another PR. Let's keep it like this for now.

@enchant3dmango No worries! Sounds good with me, I appreciate all the help you've given so far so thank you for that 🙏🏾 I can take a look at figuring out the warning ➡️ info change