[
https://issues.apache.org/jira/browse/AMBARI-21713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127317#comment-16127317
]
Hudson commented on AMBARI-21713:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #12 (See
[https://builds.apache.org/job/Ambari-branch-2.6/12/])
AMBARI-21713 Python tests started under uid=0 and uid > 0 works (hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=15bf0fa27d7bf85729c75d3d8ee6b29c6372bc4b])
* (edit) ambari-server/src/test/python/stacks/utils/RMFTestCase.py
* (edit)
ambari-common/src/main/python/resource_management/libraries/functions/packages_analyzer.py
* (edit) ambari-server/src/test/python/TestMpacks.py
> Python tests started under uid=0 and uid > 0 works differently
> --------------------------------------------------------------
>
> Key: AMBARI-21713
> URL: https://issues.apache.org/jira/browse/AMBARI-21713
> Project: Ambari
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Dmytro Grinenko
> Assignee: Dmytro Grinenko
> Priority: Critical
> Fix For: trunk
>
>
> The cause is sudo.py and same meaning modules, which implements different
> logic depends on user uid. Coz of that us tests covering only uid > 0 logic
> and starting them from root (on VM or docker) causing them to fail
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
