Created attachment 1172801 [details] screenshot Description of problem: Authorization provider: <UNKNOWN> was granted permission for Role CpuProfileOperator on Cpu Profile <UNKNOWN>, by admin@internal-authz when creating new cluster. When creating new cluster in rhev 4, we get 4 new events in the event log : - User/Group Everyone, Namespace *, Authorization provider: <UNKNOWN> was granted permission for Role CpuProfileOperator on Cpu Profile <UNKNOWN>, by admin@internal-authz. - User/Group admin, Namespace *, Authorization provider: internal-authz was granted permission for Role CpuProfileCreator on Cpu Profile <UNKNOWN>, by admin@internal-authz. - CPU Profile CLUSTER3 was successfully added (User: admin@internal-authz). - Cluster CLUSTER3 was added by admin@internal-authz Version-Release number of selected component (if applicable): 4.0.0.6-0.1.el7ev How reproducible: 100 Steps to Reproduce: 1. Create new cluster Actual results: Authorization provider: <UNKNOWN> was granted permission for Role CpuProfileOperator on Cpu Profile <UNKNOWN>, by admin@internal-authz when creating new cluster. Expected results: <UNKNOWN> should be changed
All patches are merged and there should be no risk around stability in those patches, so moving to 4.0.2
This bug was fixed and is slated to be in the upcoming version. As we are focusing our testing at this phase on severe bugs, this bug was closed without going through its verification step. If you think this bug should be verified by QE, please set its severity to high and move it back to ON_QA