New commit detected on ManageIQ/manageiq/fine: https://github.com/ManageIQ/manageiq/commit/b4ad2e25234fd7ef984a682296f9fca6444fe0e1 commit b4ad2e25234fd7ef984a682296f9fca6444fe0e1 Author: Nick Carboni <ncarboni> AuthorDate: Thu May 25 13:53:09 2017 -0400 Commit: Satoe Imaishi <simaishi> CommitDate: Mon Jun 12 11:26:03 2017 -0400 Merge pull request #15232 from jrafanie/hack_current_user Hack: set current_user since raw_scan_job_create now expects it (cherry picked from commit 87061966261086b377c85cf09302938ab7be3029) https://bugzilla.redhat.com/show_bug.cgi?id=1460754 spec/models/job_proxy_dispatcher_spec.rb | 1 + spec/models/job_spec.rb | 1 + 2 files changed, 2 insertions(+)
New commit detected on ManageIQ/manageiq/fine: https://github.com/ManageIQ/manageiq/commit/8bbc28d9fb7086a98ade7ac7011b3f1fb5fa73d0 commit 8bbc28d9fb7086a98ade7ac7011b3f1fb5fa73d0 Author: Federico Simoncelli <federico.simoncelli> AuthorDate: Thu May 25 10:25:42 2017 -0400 Commit: Satoe Imaishi <simaishi> CommitDate: Mon Jun 12 11:26:03 2017 -0400 Merge pull request #24 from moolitayer/set_user Set container scanning user (cherry picked from commit ad7cdce010b6aeb21eb2d082c0655afd084db511) https://bugzilla.redhat.com/show_bug.cgi?id=1460754 .../manageiq/providers/kubernetes/container_manager_mixin.rb | 1 + .../providers/kubernetes/container_manager/scanning/job_spec.rb | 9 +++++++-- .../manageiq/providers/kubernetes/container_manager_spec.rb | 2 ++ 3 files changed, 10 insertions(+), 2 deletions(-)
Verified. User name displayed is now the username of the logged in user e.g. admin
Created attachment 1293808 [details] screenshot showing same user Moving this back to Dev. Steps taken: Define user (admin2) Run scan View Tasks Actual result: user=admin Expected result: user=admin2 Did the above steps with user=testuser2 and still: user=admin Screenshot attached.
Thanks Einat! It took be some time to figure out what is happening. Check policy prevent checks if a policy wants to cancel the scan and then executes the scan if needed. So we get the Admin user from automate which actually calls for the scan. I will send the user as argument
BTW this isn't the original bug described here but something a little different. (user != system, but always equals 'admin')
https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/54
New commit detected on ManageIQ/manageiq/fine: https://github.com/ManageIQ/manageiq/commit/48e7f137969c479d0b40ffdeac2b1a8a52817a75 commit 48e7f137969c479d0b40ffdeac2b1a8a52817a75 Author: Federico Simoncelli <federico.simoncelli> AuthorDate: Wed Jul 5 12:10:35 2017 +0200 Commit: Satoe Imaishi <simaishi> CommitDate: Fri Aug 4 13:51:08 2017 -0400 Merge pull request #54 from moolitayer/ssa_user Pass userid before going to automation (cherry picked from commit e0e4b5f427aec60e28a15cafd07345f48fcdee25) https://bugzilla.redhat.com/show_bug.cgi?id=1460754 .../providers/kubernetes/container_manager_mixin.rb | 11 ++++++----- .../kubernetes/container_manager/scanning/job_spec.rb | 18 ++++++++++++++++-- 2 files changed, 22 insertions(+), 7 deletions(-)
https://github.com/ManageIQ/manageiq/pull/15734
https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/24 https://github.com/ManageIQ/manageiq/pull/15232 Are both in fine
The user problem that was always admin is solved. But the Owner is still empty. Mooli as discussed, please provide info on how to ensure owner field has value
I'm not sure what owner means or if it has a meaning in this context. Loic any idea?
Owner is the process owner and Owner message is the what is this process is doing. Like "external proxy" "collecting data" .. Using "owner" is confusing here.. for Container Analysis, it can remain empty.
The user problem that was always admin is solved. According to Loic it OK that "owner" can remain empty.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3005