Description of problem:
In v3.11.0-0.16.0, it is possible for a standard upgrade of logging to fail using parameters that would have otherwise worked in 3.10. 

After running an upgrade, fluentd pods will not launch due to the error:
creating: pods "logging-fluentd-" is forbidden: pods with system-cluster-critical priorityClass is not permitted in logging namespace. This is because the fluentd pods have "priorityClassName: system-cluster-critical" set, but do not exist in a privileged openshift-* namespace.  


Version-Release number of selected component (if applicable):
v3.11.0-0.16.0

How reproducible:
100%

Steps to Reproduce:
1. Configure logging to target the 'logging' namespace (anything other than openshift-*)
2. Install logging
3. Observe that fluentd will not start due to this feature of k8s: https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/  -> https://bugzilla.redhat.com/show_bug.cgi?id=1616171#c5

Actual results:
Fluentd pods fail to start. Logging will not function. 

Expected results:
The installer should fail if settings incompatible are selected for logging. Valid options:
1) openshift-* namespace configured and priorityClassName enabled.
2) non-openshift-* namespace configured, but priorityClassName disabled. 

If the installer is otherwise configured, it should error before it unintentionally cripples logging. 

Additional info:
If the user can prevent priorityClassName from being set by a setting in the inventory, documentation on the impact of this should be provided. 

Description of problem:

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag