[
https://issues.apache.org/jira/browse/AMBARI-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202057#comment-14202057
]
Hadoop QA commented on AMBARI-8203:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12680167/AMBARI-8203_1.7.0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/546//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/546//console
This message is automatically generated.
> Add Service service accounts look incorrect
> -------------------------------------------
>
> Key: AMBARI-8203
> URL: https://issues.apache.org/jira/browse/AMBARI-8203
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 1.7.0
>
> Attachments: AMBARI-8203.patch, AMBARI-8203_1.7.0.patch
>
>
> 1) install cluster with a subset of services
> 2) customize service accounts
> 3) users and groups get created with those custom names
> PROBLEM #1: it's creating the nagios group but it's not putting nagios in the
> group (it puts nagios in hadoop group). Why are we creating this group if we
> are not using it?
> {code}
> nagiosXX:x:503:
> usersXX:x:504:ambari-qaXX,oozieXX
> hadoopXX:x:505:nagiosXX,hdfsXX,mapredXX,zookeeperXX,yarnXX
> nobodyXX:x:506:nobodyXX
> {code}
> 4. Go to add service. Select to add some services.
> 5. On the Misc tab, you can customize the accounts and hadoop group and smoke
> user are showing on that form as well.
> PROBLEM #2: they show smoke user and hadoop group using the default names,
> not the custom names so that's confusing
> PROBLEM #3: really, smoke user and hadoop group shouldn't be showing as
> editable since they are already created
> 6. Add the services and you'll find it didn't seem to create the new accounts
> but did create hdfs, yarn and mapred groups + users.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
