Ansible Tower Upgrade Issues

Hello folks,

we apologize for the inconvenience caused by disappearance of the Notification tab after upgrade of Ansible Tower from v3.2.3 to v3.3.4. The issue is caused by the regression of an old bug in Ansible Tower. We have raised this issue with Red Hat support, they are working on the fix v3.4.2, but there is no confirmed solution for v3.3.x, though with your help we have identified some workarounds.

Why did we upgrade?
Because of the deprecation of Google+ Sign-in API by Google, we had to upgrade to either v3.3.4 or v3.4.1, in order to retain ability to authenticate Tower users using Google Single Sign-on.

We did not wish to upgrade to version 3.4.1 this year as it requires a much more complex upgrade procedure and because it was more likely to introduce disruptions to you - end users. We cannot roll back to 3.2.x because RedHat is refusing to provide Google+ API fix to that version as it has already entered the End of Life (EOL) stage.

What are our options?
At this point our only solutions are to either continue using the workarounds or upgrade to v3.4.2 when Red Hat releases the fix. Red Hat has not committed to fixing this issue in v3.3.x, even though it is still under full support, which means we may be forced to do another upgrade if workaround is causing you too much trouble. Note: upgrade to 3.4.2 will lead to further disruptions and would force us to upgrade the underlying version of Ansible from 2.5 to 2.7, which means you will need to ensure your current playbooks and roles are compatible with Ansible 2.7. We would like your feedback on which option you would prefer.

Once again we apologize for the inconvenience and possible future disruptions (even though they are beyond our control).

References:
Ansible Tower bug: https://github.com/ansible/awx/issues/2949
Workarounds: https://29022131.atlassian.net/wiki/x/wqczP
Survey Form: https://goo.gl/forms/hZ7LCMyz7xPsZU0Z2