Symptoms

After a software upgrade, daemons may revert to logging at the INFORMATIONAL log level, regardless of what is actually configured. For example, the configuration may indicate that authentication manager has debug logging enabled, but it will not generate any debug logs.

Impact

System does not generate debug logs when expected.

Conditions

- F5OS system upgrade - A component has a non-default log severity configured.

Workaround

Set the log level to INFORMATIONAL and then set it back to the desired severity. For example, from the F5OS CLI: config system logging sw-components sw-component authd config severity INFORMATIONAL ; top ; commit system logging sw-components sw-component authd config severity DEBUG ; top ; commit

Fix Information

An order in which conditions are checked was changed to not skip updating the severities that the individual components use to know at what level they are logging.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips