Fix to ensure that asyncio uses SaltLoggingClass

Fixes the salt logging implementation to check asyncio is using the
SaltLoggingClass if it has already been imported. If it uses the
standard logging.Logger() class then extra fields in the log format such
as %(jid)s will cause an exception when asyncio logs anything.

Author: barneysowood

changelog/68400.fixed.md

@@ -0,0 +1 @@
+Fixes issue with asyncio logger not using SaltLoggingClass and causing exceptions when "%(jid)s" is used in a log format.

salt/_logging/impl.py

@@ -559,6 +559,13 @@ def shutdown_temp_handler():
         logging.root.addHandler(get_temp_handler())
 
 
+# Override asyncio logger class if asyncio is already imported
+if "asyncio" in sys.modules:
+    asyncio_logger = logging.getLogger("asyncio")
+    if not isinstance(asyncio_logger, SaltLoggingClass):
+        asyncio_logger.__class__ = SaltLoggingClass
+
+
 # Now that we defined the default logging logger class, we can instantiate our logger
 # DO NOT MOVE THIS
 log = logging.getLogger(__name__)

tests/pytests/unit/_logging/test_asyncio_logger.py

@@ -0,0 +1,19 @@
+"""
+Tests to ensure asyncio logger uses SaltLoggingClass
+"""
+
+import logging
+
+
+def test_asyncio_logger_saltloggingclass():
+    """
+    Test that the asyncio logger is an instance of SaltLoggingClass
+
+    It is imported before salt._logging so we need to ensure it is overridden
+    """
+
+    asyncio_logger = logging.getLogger("asyncio")
+
+    import salt._logging.impl
+
+    assert isinstance(asyncio_logger, salt._logging.impl.SaltLoggingClass)