Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
@chrismeyersfsu and I observed daphne giving tracebacks when accessing logging settings.
Originally, configure tower in tower settings was not a suspect because daphne is not multi-process. We've had issues with configure tower in tower settings and multi-process before. The trouble with that is that Daphne is multi-threaded.
We created a situation locally that showed to show that multiple threads accessing settings can cause a daphne error traceback along the lines of:
ISSUE TYPE
COMPONENT NAME
AWX VERSION
ADDITIONAL INFORMATION
This addition, while proved on our end, is somewhat of a hypothesis. We're hoping this fixes things but will be equally, if not more, pleased if a community member catches something we missed.