Created attachment 1491619 [details]
logs and screenshots

Description of problem:
I've been investigating issues with our provisioning test cases failing on timeout [0].
However, executing provisioning by itself always succeeds, so I tried to find which tests have been executed before this provision test.

I found that executing quota tests [1] on a clean appliance can lead to a state in which provision request done by Administration is stuck in Pending Approval.

These quota tests create a new user, assign the user to EvmGroup-super_administrator group, set tenant project quotas and try to provision a vm as the created user. First I thought there are some leftovers after these tests, but I triple-checked and haven't found any. 

Attached relevant screenshots as well as complete automation.log, evm.log, rhevm.log, production.log and api.log.

Executed this command to reproduce:
miq-runtest cfme/tests/infrastructure/test_project_quota.py cfme/tests/infrastructure test_provisioning_dialog.py::test_change_cpu_ram

This resulted in a state where Administrator user has created a provision request, which is stuck in Pending Approval.
I'll keep the appliance for some time to allow for further investigation.

[0] https://github.com/ManageIQ/integration_tests/blob/cfa6ac2f346f006b1af57ccca26c7cda71887a02/cfme/tests/infrastructure/test_provisioning_dialog.py#L117
[1] https://github.com/ManageIQ/integration_tests/blob/master/cfme/tests/infrastructure/test_project_quota.py


Version-Release number of selected component (if applicable):
Version 5.9.5.0.20180927190514_e161d8f

How reproducible:
75%

Steps to Reproduce:
1. miq-runtest cfme/tests/infrastructure/test_child_tenant.py cfme/tests/infrastructure/test_project_quota.py cfme/tests/infrastructure/test_provisioning_dialog.py::test_change_cpu_ram


Actual results:
This resulted in a state where Administrator user has created a provision request, which is stuck in Pending Approval.

Expected results:
Provision request should be auto approved.

Additional info: