[
https://issues.apache.org/jira/browse/AMBARI-21713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16128713#comment-16128713
]
Hudson commented on AMBARI-21713:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7892 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7892/])
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=fc8dd78e145c45db1128b49f66be5aa1919b852f])
* (edit)
ambari-agent/src/test/python/resource_management/TestPackagesAnalyzer.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
>
> Attachments: AMBARI-21713-UT.patch
>
>
> 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)
