You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Dmytro Grinenko (JIRA)" <ji...@apache.org> on 2017/08/15 11:54:00 UTC
[jira] [Commented] (AMBARI-21713) Python tests started under uid=0
and uid > 0 works differently
[ https://issues.apache.org/jira/browse/AMBARI-21713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16127121#comment-16127121 ]
Dmytro Grinenko commented on AMBARI-21713:
------------------------------------------
Committed:
bbd751130f..845aaa3f0c branch-feature-AMBARI-21450 -> branch-feature-AMBARI-21450
f206e95711..12b6caad61 trunk -> trunk
> 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)