Github user arunmahadevan commented on the issue:
https://github.com/apache/storm/pull/2721
@revans2 , i have refactored the code so that we check for "user.name" in
the normal container and the result of `getWorkerUser` in the
RunAsUserContainer.
The `getWorkerUser` is used in other places to set the user in the workers
local state and apparently used to do some authorization checks in the log
viewer. I did not want to affect that behavior so I introduced a new function
to return the OS user that the worker is expected to run as that invokes the
`getWorkerUser` in the run as container.
This issue happens in posix environment as well and most of the users dont
set the `supervisor.run.worker.as.user` config but run storm in secure mode.
---
