[jira] [Commented] (AMBARI-21757) Allow for keytab regeneration to be filtered for hosts
[ https://issues.apache.org/jira/browse/AMBARI-21757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16305210#comment-16305210 ] wangyaoxin commented on AMBARI-21757: - Hi [~echekanskiy] , the patch has some problem . If regenerate keytab for host1, ambari-qa-clus...@example.com or hdfs-clus...@example.com will be affected, but the smokeuser.headless.keytab or hdfs.headless.keytab on other hosts will not created. cased password incorrect while getting initial credentials. > Allow for keytab regeneration to be filtered for hosts > -- > > Key: AMBARI-21757 > URL: https://issues.apache.org/jira/browse/AMBARI-21757 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0, 2.6.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0, 2.6.0 > > Attachments: AMBARI-21757-trunk-2.patch, AMBARI-21757-trunk-3.patch, > AMBARI-21757-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21208) Upgrade PreUpgradeCheck NullPointerException
[ https://issues.apache.org/jira/browse/AMBARI-21208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-21208: Attachment: AMBARI-21208.patch > Upgrade PreUpgradeCheck NullPointerException > - > > Key: AMBARI-21208 > URL: https://issues.apache.org/jira/browse/AMBARI-21208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: upgrade > Fix For: trunk > > Attachments: AMBARI-21208.patch > > > java.lang.NullPointerException > at > org.apache.ambari.server.state.stack.UpgradePack.getPrerequisiteChecks(UpgradePack.java:151) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21208) Upgrade PreUpgradeCheck NullPointerException
[ https://issues.apache.org/jira/browse/AMBARI-21208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-21208: Description: java.lang.NullPointerException at org.apache.ambari.server.state.stack.UpgradePack.getPrerequisiteChecks(UpgradePack.java:151) was: 08 Jun 2017 15:57:56,845 ERROR [ambari-client-thread-4595] ReadHandler:102 - Caught a runtime exception executing a query java.lang.NullPointerException at org.apache.ambari.server.state.stack.UpgradePack.getPrerequisiteChecks(UpgradePack.java:149) at org.apache.ambari.server.checks.UpgradeCheckRegistry.getFilteredUpgradeChecks(UpgradeCheckRegistry.java:68) at org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:189) > Upgrade PreUpgradeCheck NullPointerException > - > > Key: AMBARI-21208 > URL: https://issues.apache.org/jira/browse/AMBARI-21208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: upgrade > Fix For: trunk > > > java.lang.NullPointerException > at > org.apache.ambari.server.state.stack.UpgradePack.getPrerequisiteChecks(UpgradePack.java:151) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21208) Upgrade PreUpgradeCheck NullPointerException
[ https://issues.apache.org/jira/browse/AMBARI-21208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-21208: Description: 08 Jun 2017 15:57:56,845 ERROR [ambari-client-thread-4595] ReadHandler:102 - Caught a runtime exception executing a query java.lang.NullPointerException at org.apache.ambari.server.state.stack.UpgradePack.getPrerequisiteChecks(UpgradePack.java:149) at org.apache.ambari.server.checks.UpgradeCheckRegistry.getFilteredUpgradeChecks(UpgradeCheckRegistry.java:68) at org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:189) was: 08 Jun 2017 15:57:56,845 ERROR [ambari-client-thread-4595] ReadHandler:102 - Caught a runtime exception executing a query java.lang.NullPointerException at org.apache.ambari.server.state.stack.UpgradePack.getPrerequisiteChecks(UpgradePack.java:149) at org.apache.ambari.server.checks.UpgradeCheckRegistry.getFilteredUpgradeChecks(UpgradeCheckRegistry.java:68) at org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:189) at org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966) at org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141) at org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529) at org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:398) at org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222) at org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) at org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) at org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) at org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) at org.apache.ambari.server.api.services.PreUpgradeCheckService.getPreUpgradeChecks(PreUpgradeCheckService.java:61) > Upgrade PreUpgradeCheck NullPointerException > - > > Key: AMBARI-21208 > URL: https://issues.apache.org/jira/browse/AMBARI-21208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: upgrade > Fix For: trunk > > > 08 Jun 2017 15:57:56,845 ERROR [ambari-client-thread-4595] ReadHandler:102 - > Caught a runtime exception executing a query > java.lang.NullPointerException > at > org.apache.ambari.server.state.stack.UpgradePack.getPrerequisiteChecks(UpgradePack.java:149) > at > org.apache.ambari.server.checks.UpgradeCheckRegistry.getFilteredUpgradeChecks(UpgradeCheckRegistry.java:68) > at > org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:189) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21208) Upgrade PreUpgradeCheck NullPointerException
[ https://issues.apache.org/jira/browse/AMBARI-21208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-21208: Description: 08 Jun 2017 15:57:56,845 ERROR [ambari-client-thread-4595] ReadHandler:102 - Caught a runtime exception executing a query java.lang.NullPointerException at org.apache.ambari.server.state.stack.UpgradePack.getPrerequisiteChecks(UpgradePack.java:149) at org.apache.ambari.server.checks.UpgradeCheckRegistry.getFilteredUpgradeChecks(UpgradeCheckRegistry.java:68) at org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:189) at org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966) at org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141) at org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529) at org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:398) at org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222) at org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) at org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) at org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) at org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) at org.apache.ambari.server.api.services.PreUpgradeCheckService.getPreUpgradeChecks(PreUpgradeCheckService.java:61) > Upgrade PreUpgradeCheck NullPointerException > - > > Key: AMBARI-21208 > URL: https://issues.apache.org/jira/browse/AMBARI-21208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: upgrade > Fix For: trunk > > > 08 Jun 2017 15:57:56,845 ERROR [ambari-client-thread-4595] ReadHandler:102 - > Caught a runtime exception executing a query > java.lang.NullPointerException > at > org.apache.ambari.server.state.stack.UpgradePack.getPrerequisiteChecks(UpgradePack.java:149) > at > org.apache.ambari.server.checks.UpgradeCheckRegistry.getFilteredUpgradeChecks(UpgradeCheckRegistry.java:68) > at > org.apache.ambari.server.controller.internal.PreUpgradeCheckResourceProvider.getResources(PreUpgradeCheckResourceProvider.java:189) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl$ExtendedResourceProviderWrapper.queryForResources(ClusterControllerImpl.java:966) > at > org.apache.ambari.server.controller.internal.ClusterControllerImpl.getResources(ClusterControllerImpl.java:141) > at > org.apache.ambari.server.api.query.QueryImpl.doQuery(QueryImpl.java:529) > at > org.apache.ambari.server.api.query.QueryImpl.queryForResources(QueryImpl.java:398) > at > org.apache.ambari.server.api.query.QueryImpl.execute(QueryImpl.java:222) > at > org.apache.ambari.server.api.handlers.ReadHandler.handleRequest(ReadHandler.java:77) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:145) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:126) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:90) > at > org.apache.ambari.server.api.services.PreUpgradeCheckService.getPreUpgradeChecks(PreUpgradeCheckService.java:61) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21208) Upgrade PreUpgradeCheck NullPointerException
[ https://issues.apache.org/jira/browse/AMBARI-21208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-21208: Labels: upgrade (was: ) > Upgrade PreUpgradeCheck NullPointerException > - > > Key: AMBARI-21208 > URL: https://issues.apache.org/jira/browse/AMBARI-21208 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: upgrade > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21208) Upgrade PreUpgradeCheck NullPointerException
wangyaoxin created AMBARI-21208: --- Summary: Upgrade PreUpgradeCheck NullPointerException Key: AMBARI-21208 URL: https://issues.apache.org/jira/browse/AMBARI-21208 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: wangyaoxin Assignee: wangyaoxin Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin resolved AMBARI-18892. - Resolution: Fixed > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892_01.patch, AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902627#comment-15902627 ] wangyaoxin commented on AMBARI-20356: - Hi [~afernandez] Thank you so much for reviewing my patch on reviewboard, and could you commit the patch ? Thanks > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-20356.patch, ambari.png > > > ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java > > "the results of the request a a Tree structure" should be "the results of the > request as a Tree structure" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18414) rolling restart services user login audit log show error
[ https://issues.apache.org/jira/browse/AMBARI-18414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18414: Affects Version/s: (was: trunk) 2.4.0 > rolling restart services user login audit log show error > - > > Key: AMBARI-18414 > URL: https://issues.apache.org/jira/browse/AMBARI-18414 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: rolling restart.png > > > when rolling restart service, audit log will show info about user login > ,and remoteIp is 127.0.0.1 > 2016-09-18T18:07:30.604+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(29) > 2016-09-18T18:07:30.604+0800, User(admin), Operation(CUSTOM_COMMAND > DATANODE), Details(RESTART HDFS/DATANODE), Status(QUEUED), RequestId(29), > TaskId(127), Hostname(hostname) > 2016-09-18T18:07:30.610+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:30.610+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) > 2016-09-18T18:07:35.680+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:35.680+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) > 2016-09-18T18:07:40.692+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:40.692+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-18414) rolling restart services user login audit log show error
[ https://issues.apache.org/jira/browse/AMBARI-18414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin reassigned AMBARI-18414: --- Assignee: wangyaoxin > rolling restart services user login audit log show error > - > > Key: AMBARI-18414 > URL: https://issues.apache.org/jira/browse/AMBARI-18414 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: rolling restart.png > > > when rolling restart service, audit log will show info about user login > ,and remoteIp is 127.0.0.1 > 2016-09-18T18:07:30.604+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(29) > 2016-09-18T18:07:30.604+0800, User(admin), Operation(CUSTOM_COMMAND > DATANODE), Details(RESTART HDFS/DATANODE), Status(QUEUED), RequestId(29), > TaskId(127), Hostname(hostname) > 2016-09-18T18:07:30.610+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:30.610+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) > 2016-09-18T18:07:35.680+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:35.680+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) > 2016-09-18T18:07:40.692+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:40.692+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15902626#comment-15902626 ] wangyaoxin commented on AMBARI-18892: - Hi [~rlevas] Thank you so much for reviewing my patch on reviewboard, and could you commit the patch ? Thanks > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892_01.patch, AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-20356: Description: ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java "the results of the request a a Tree structure" should be "the results of the request as a Tree structure" > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-20356.patch, ambari.png > > > ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java > > "the results of the request a a Tree structure" should be "the results of the > request as a Tree structure" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-20356: Attachment: ambari.png > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-20356.patch, ambari.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-20356: Attachment: AMBARI-20356.patch > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-20356.patch, ambari.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20356) description incorrect for result class
[ https://issues.apache.org/jira/browse/AMBARI-20356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-20356: Component/s: ambari-server > description incorrect for result class > --- > > Key: AMBARI-20356 > URL: https://issues.apache.org/jira/browse/AMBARI-20356 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20356) description incorrect for result class
wangyaoxin created AMBARI-20356: --- Summary: description incorrect for result class Key: AMBARI-20356 URL: https://issues.apache.org/jira/browse/AMBARI-20356 Project: Ambari Issue Type: Improvement Reporter: wangyaoxin Assignee: wangyaoxin Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898926#comment-15898926
]
wangyaoxin commented on AMBARI-19079:
-
Hi [~rlevas]
The OS is not LinuxONE, but its core is identical with Redhat’s/Centos’s,
therefore HDP and Ambari can run on PPC properly.
HDP needs repack on PPC. For instance,Hadoop code will import jar packages from
JDK; since IBM jar packages and Sun jar packages contain different content,
recompilation is required within IBM JDK.
It would be simple to edit configuration:only needs adding one configuration
into Kerberos. For example, jdk_type, sunor ibm, and –kt.
eg: hbase_master_jaas.conf.j2
{% if java_type == "sun" %}
Client {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
storeKey=true
useTicketCache=false
keyTab="{{master_keytab_path}}"
principal="{{master_jaas_princ}}";
};
{% endif %}
{% if java_type == "ibm" %}
Client {
com.ibm.security.auth.module.Krb5LoginModule required
useKeytab="{{master_keytab_path}}"
principal="{{master_jaas_princ}}"
credsType=both
debug=true;
};
{% endif %}
PPC JDK has two self-contained commands, klist and kinit. The usages of them
are indentical with the ones of Kerberos. eg: kinit -kt (I once mentioned it
must be kint -A -k -t, that was wrong, -kt is also allowed)
It has been completed before that deploying Ambari on PPC platform with
supporting Kerberos. If it is considered that supporting Ambari with kerberos
enabled on PPC platform, I will attach the patch afterwards. My pleasure to
discuss subjects on Kerberos with you, thanks for your patience andtime!
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15898647#comment-15898647 ] wangyaoxin commented on AMBARI-18892: - Hi [~rlevas] Thanks , I have attached a new patch . > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892_01.patch, AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18892: Attachment: AMBARI-18892_01.patch > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892_01.patch, AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18892: Attachment: (was: AMBARI-18892_01.patch) > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18892: Attachment: AMBARI-18892_01.patch > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892_01.patch, AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15897359#comment-15897359
]
wangyaoxin commented on AMBARI-19079:
-
Hi [~rlevas]
Kerberos client packages are self-contained on IBM PPC platform. For instance,
they can be installed directly by "yum install", but there are few constraints:
1.HDP must provide versions that support PPC machine, in other words, HDP needs
repack within JDK environment on PPC machine;
2. Several configurations of service components need to be edited, such as
HBase, Metrics. For example, kind of com.sun needs to be edited as com.ibm.
3. Kinit's path in Ambari needs to be set as configurable, because IBM JDK
contains self-matching Kinit,applying Kinit of Kerberos will cause conflict.
However, for x86 PC, it is fine to keep using Kinit under Kerberos path.
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18892: Attachment: AMBARI-18892.patch > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18892: Attachment: (was: AMBARI-18892.patch) > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18892: Attachment: AMBARI-18892.patch > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-18892.patch, storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wangyaoxin updated AMBARI-19079:
Fix Version/s: (was: 2.5.0)
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893969#comment-15893969
]
wangyaoxin edited comment on AMBARI-19079 at 3/3/17 9:22 AM:
-
Has it ever be considered that supporting Ambari deployment on IBM PPC?
was (Author: forestsissi):
Has it ever be considered that deploying Ambari on IBM Power machine?
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk, 2.5.0
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15893969#comment-15893969
]
wangyaoxin commented on AMBARI-19079:
-
Has it ever be considered that deploying Ambari on IBM Power machine?
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk, 2.5.0
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18892: Fix Version/s: (was: 2.5.0) 3.0.0 > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 3.0.0 > > Attachments: storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15723988#comment-15723988
]
wangyaoxin commented on AMBARI-19079:
-
Hi [~rlevas] ,Thank you ,I see and I'll give a new description of the problem:
If we use ppc(power machine), after enable kerberos, when excute :hdfs dfs -ls
/ ,the wrong message is:
javax.security.sasl.SaslException: Failure to initialize security context
[Caused by org.ietf.jgss.GSSException, major code: 13, minor code: 0
it might just because the ibm jdk don't support the kerberos client kinit, and
we have to use the {ibm_home/jre/bin/kinit to create tickets manual;
and another problem is the templates files of hbase metrics and zookeeper ,like
zookeeper_jass.conf.j2 (com.sun.security.auth.module.Krb5LoginModule required)
sun isn't configurable
This cause problem when we use IBM Jdk to directly turn on Kerberos, that
requires to change configurations at back-end. Therefore I raised the question,
is it necessary for ambari supporting an automatic start of Kerberos operated
by ibm?
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk, 2.5.0
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15722563#comment-15722563
]
wangyaoxin commented on AMBARI-19079:
-
Hi Robert if we use the ibm jdk,it should use the jdk's kinit ,eg:
/usr/java-ppc64-71/jre/bin/kinit -A -k -t
/etc/security/keytabs/hdfs.headless.keytab hdfs/ambari@REALM, not the
/usr/bin/kinit -kt or /usr/java-ppc64-71/jre/bin/kinit -kt, it will errors like
java.lang.IllegalArgumentException: Too many args
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk, 2.5.0
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15721827#comment-15721827
]
wangyaoxin commented on AMBARI-19079:
-
Hi [~rlevas][~afernandez] ,May I suggest that , I think it will be better
if the -kt is configurable
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk, 2.5.0
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wangyaoxin updated AMBARI-19079:
Description:
If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool Kinit
({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be better to
add two configurations item in kerberos-env for kt and java type, for example,
cmd_type and java_type .
was:If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be better
to add two configurations item in kerberos-env for kt and java type, for
example, cmd_type and java_type .
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk, 2.5.0
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19079) The kerberos -kt should be free configuration
[
https://issues.apache.org/jira/browse/AMBARI-19079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wangyaoxin updated AMBARI-19079:
Description: If JDK is not SUN, such as IBM JDK, then must initialize it
with JDK tool Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it
would be better to add two configurations item in kerberos-env for kt and java
type, for example, cmd_type and java_type . (was: If JDK is not SUN, such as
IBM JDK, then must initialize it with JDK tool Kinit ({jdk_home}/jre/bin/kinit
-A -k -t); therefore I sense it would be better to add a configuration item in
kerberos-env for kt, for example, cmd_type.)
> The kerberos -kt should be free configuration
> -
>
> Key: AMBARI-19079
> URL: https://issues.apache.org/jira/browse/AMBARI-19079
> Project: Ambari
> Issue Type: Improvement
>Reporter: wangyaoxin
>Assignee: wangyaoxin
> Fix For: trunk, 2.5.0
>
>
> If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool
> Kinit ({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be
> better to add two configurations item in kerberos-env for kt and java type,
> for example, cmd_type and java_type .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-19079) The kerberos -kt should be free configuration
wangyaoxin created AMBARI-19079:
---
Summary: The kerberos -kt should be free configuration
Key: AMBARI-19079
URL: https://issues.apache.org/jira/browse/AMBARI-19079
Project: Ambari
Issue Type: Improvement
Reporter: wangyaoxin
Assignee: wangyaoxin
Fix For: trunk, 2.5.0
If JDK is not SUN, such as IBM JDK, then must initialize it with JDK tool Kinit
({jdk_home}/jre/bin/kinit -A -k -t); therefore I sense it would be better to
add a configuration item in kerberos-env for kt, for example, cmd_type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18944) Improve remoteIp in audit log
[ https://issues.apache.org/jira/browse/AMBARI-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714479#comment-15714479 ] wangyaoxin commented on AMBARI-18944: - Hi [~oleewere] ,[~rlevas] [~adoroszlai] [~jonathan.hurley], Thank you so much for reviewing my patch on reviewboard, and could you be so kind as to commit the patch for me please? Thanks in advance. > Improve remoteIp in audit log > - > > Key: AMBARI-18944 > URL: https://issues.apache.org/jira/browse/AMBARI-18944 > Project: Ambari > Issue Type: Improvement >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18944.patch, AMBARI-18944_01.patch, > AMBARI-18944_02.patch > > > Mutil-agent were configured in some production environments, RemoteIp > therefore will obtain mutilple IP addresses, like > (RemoteIp(172.16.0.66,172.16.193.56),)which causes errors in log output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18944) Improve remoteIp in audit log
[ https://issues.apache.org/jira/browse/AMBARI-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18944: Attachment: AMBARI-18944_02.patch > Improve remoteIp in audit log > - > > Key: AMBARI-18944 > URL: https://issues.apache.org/jira/browse/AMBARI-18944 > Project: Ambari > Issue Type: Improvement >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18944.patch, AMBARI-18944_01.patch, > AMBARI-18944_02.patch > > > Mutil-agent were configured in some production environments, RemoteIp > therefore will obtain mutilple IP addresses, like > (RemoteIp(172.16.0.66,172.16.193.56),)which causes errors in log output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15714431#comment-15714431 ] wangyaoxin commented on AMBARI-18441: - Hi [~afernandez] [~jonathan.hurley] , Thank you so much for reviewing my patch on reviewboard, and could you be so kind as to commit the patch for me please? Thanks in advance. > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18411-03.patch, AMBARI-18441-01.patch, > AMBARI-18441-02.patch, AMBARI-18441.patch, upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18441: Attachment: AMBARI-18411-03.patch > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18411-03.patch, AMBARI-18441-01.patch, > AMBARI-18441-02.patch, AMBARI-18441.patch, upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18944) Improve remoteIp in audit log
[ https://issues.apache.org/jira/browse/AMBARI-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18944: Attachment: AMBARI-18944_01.patch > Improve remoteIp in audit log > - > > Key: AMBARI-18944 > URL: https://issues.apache.org/jira/browse/AMBARI-18944 > Project: Ambari > Issue Type: Improvement >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18944.patch, AMBARI-18944_01.patch > > > Mutil-agent were configured in some production environments, RemoteIp > therefore will obtain mutilple IP addresses, like > (RemoteIp(172.16.0.66,172.16.193.56),)which causes errors in log output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18781) ambari server StackOverflowError in IBM PPC64
[ https://issues.apache.org/jira/browse/AMBARI-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin reopened AMBARI-18781: - > ambari server StackOverflowError in IBM PPC64 > - > > Key: AMBARI-18781 > URL: https://issues.apache.org/jira/browse/AMBARI-18781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > Attachments: AMBARI-18781.patch > > > 02 Nov 2016 09:27:22,301 INFO [qtp-client-85] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:27:25,360 INFO [qtp-client-125] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:28:32,681 WARN [qtp-client-85] ServletHandler:538 - > javax.servlet.ServletException: java.lang.StackOverflowError > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:182) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18781) ambari server StackOverflowError in IBM PPC64
[ https://issues.apache.org/jira/browse/AMBARI-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18781: Status: Patch Available (was: Reopened) > ambari server StackOverflowError in IBM PPC64 > - > > Key: AMBARI-18781 > URL: https://issues.apache.org/jira/browse/AMBARI-18781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wuhui > Fix For: trunk > > Attachments: AMBARI-18781.patch > > > 02 Nov 2016 09:27:22,301 INFO [qtp-client-85] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:27:25,360 INFO [qtp-client-125] PersistKeyValueService:82 - > Looking for keyName CLUSTER_CURRENT_STATUS > 02 Nov 2016 09:28:32,681 WARN [qtp-client-85] ServletHandler:538 - > javax.servlet.ServletException: java.lang.StackOverflowError > at > com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:420) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:540) > at > com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:715) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118) > at > org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:103) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:113) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:54) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:45) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.apache.ambari.server.security.authorization.AmbariAuthorizationFilter.doFilter(AmbariAuthorizationFilter.java:182) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) > at > org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:150) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-8840) Keytabs need to be created to include the encryption type of AES256 CTS mode with HMAC SHA1-96
[
https://issues.apache.org/jira/browse/AMBARI-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15689201#comment-15689201
]
wangyaoxin commented on AMBARI-8840:
Similiar situation on cluster upgrade from ambari 1.7 to 2.1.1, change the
spnego.keytab to 640 ,but it is not work
klist -e -k /etc/security/keytabs/hdfs.headless.keytab, without the
aes256-cts-hmac-sha1-96
my last solution is : ambari-server restart and ambari-agent restart (each
nodes), Regenerate keytabs , it works .maytab the problem of JCE
> Keytabs need to be created to include the encryption type of AES256 CTS mode
> with HMAC SHA1-96
> --
>
> Key: AMBARI-8840
> URL: https://issues.apache.org/jira/browse/AMBARI-8840
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.0.0, 2.1.0
> Environment: Red Hat Enterprise Linux Server release 6.6 (Santiago)
> [root@hdtest253 etc]# java -version
> java version "1.7.0_79"
> OpenJDK Runtime Environment (rhel-2.5.5.3.el6_6-x86_64 u79-b14)
> OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Labels: kerberos, keytabs
> Fix For: 2.1.0
>
> Attachments: hadoop-hdfs-journalnode-hdtest253.svl.ibm.com.log
>
>
> During automated keytab generation, an entry with the following encryption
> type must be added else certain services will fail to start up or properly
> when Kerberos is enabled:
> {code}AES256 CTS mode with HMAC SHA1-96{code}
> For example, NAMENODE will fail with the following errors:
> {code}
> 2014-12-19 21:45:56,101 WARN server.AuthenticationFilter
> (AuthenticationFilter.java:doFilter(551)) - Authentication exception:
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES256 CTS mode with HMAC SHA1-96)
> org.apache.hadoop.security.authentication.client.AuthenticationException:
> GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid
> argument (400) - Cannot find key of appropriate type to decrypt AP REP -
> AES256 CTS mode with HMAC SHA1-96)
> at
> org.apache.hadoop.security.authentication.server.KerberosAuthenticationHandler.authenticate(KerberosAuthenticationHandler.java:399)
> at
> org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:507)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.apache.hadoop.http.HttpServer2$QuotingInputFilter.doFilter(HttpServer2.java:1224)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at org.apache.hadoop.http.NoCacheFilter.doFilter(NoCacheFilter.java:45)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1212)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:399)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> Caused by: GSSException: Failure unspecified at GSS-API level (Mechanism
> level: Invalid argument (400) - Cannot find key of appropriate type to
> decrypt AP REP - AES256 CTS mode with HMAC SHA1-96)
> at
> sun.security.jgss.krb5.Krb5Context.acceptSecContext(Krb5Context.java:788)
> at
>
[jira] [Updated] (AMBARI-18944) Improve remoteIp in audit log
[ https://issues.apache.org/jira/browse/AMBARI-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18944: Status: Patch Available (was: Open) > Improve remoteIp in audit log > - > > Key: AMBARI-18944 > URL: https://issues.apache.org/jira/browse/AMBARI-18944 > Project: Ambari > Issue Type: Improvement >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18944.patch > > > Mutil-agent were configured in some production environments, RemoteIp > therefore will obtain mutilple IP addresses, like > (RemoteIp(172.16.0.66,172.16.193.56),)which causes errors in log output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18944) Improve remoteIp in audit log
[ https://issues.apache.org/jira/browse/AMBARI-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18944: Attachment: AMBARI-18944.patch > Improve remoteIp in audit log > - > > Key: AMBARI-18944 > URL: https://issues.apache.org/jira/browse/AMBARI-18944 > Project: Ambari > Issue Type: Improvement >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18944.patch > > > Mutil-agent were configured in some production environments, RemoteIp > therefore will obtain mutilple IP addresses, like > (RemoteIp(172.16.0.66,172.16.193.56),)which causes errors in log output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18944) Improve remoteIp in audit log
[ https://issues.apache.org/jira/browse/AMBARI-18944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18944: Description: Mutil-agent were configured in some production environments, RemoteIp therefore will obtain mutilple IP addresses, like (RemoteIp(172.16.0.66,172.16.193.56),)which causes errors in log output. (was: Mutil-agent were configured in some production environments, RemoteIp therefore will obtain mutilple IP addresses, which causes errors in log output.) > Improve remoteIp in audit log > - > > Key: AMBARI-18944 > URL: https://issues.apache.org/jira/browse/AMBARI-18944 > Project: Ambari > Issue Type: Improvement >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 2.5.0 > > > Mutil-agent were configured in some production environments, RemoteIp > therefore will obtain mutilple IP addresses, like > (RemoteIp(172.16.0.66,172.16.193.56),)which causes errors in log output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18441: Attachment: AMBARI-18441-02.patch > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18441-01.patch, AMBARI-18441-02.patch, > AMBARI-18441.patch, upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
[ https://issues.apache.org/jira/browse/AMBARI-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18892: Attachment: storm.png > storm DRPC_SERVER kerberos configs duplicate > - > > Key: AMBARI-18892 > URL: https://issues.apache.org/jira/browse/AMBARI-18892 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.4.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk, 2.5.0 > > Attachments: storm.png > > > when ambari enables kerberos, add storm service ,nimbus_keytab and > nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18892) storm DRPC_SERVER kerberos configs duplicate
wangyaoxin created AMBARI-18892: --- Summary: storm DRPC_SERVER kerberos configs duplicate Key: AMBARI-18892 URL: https://issues.apache.org/jira/browse/AMBARI-18892 Project: Ambari Issue Type: Improvement Affects Versions: trunk, 2.4.1 Reporter: wangyaoxin Assignee: wangyaoxin Fix For: trunk, 2.5.0 when ambari enables kerberos, add storm service ,nimbus_keytab and nimbus_principal_name will duplicate -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18441: Attachment: AMBARI-18441-01.patch > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18441-01.patch, AMBARI-18441.patch, upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18441: Status: Patch Available (was: Open) > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18441.patch, upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18441: Attachment: AMBARI-18441.patch > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-18441.patch, upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18441) upgrade ambari to 2.1.1 error
wangyaoxin created AMBARI-18441: --- Summary: upgrade ambari to 2.1.1 error Key: AMBARI-18441 URL: https://issues.apache.org/jira/browse/AMBARI-18441 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: wangyaoxin Assignee: wangyaoxin Attachments: upgrade.png ambari upgrade to 2.1.1, if the first time failed , excute ambari-server upgrade again will error duplicate key value violates unique constraint "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18441: Attachment: upgrade.png > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18441: Affects Version/s: 2.1.1 > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18441) upgrade ambari to 2.1.1 error
[ https://issues.apache.org/jira/browse/AMBARI-18441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18441: Fix Version/s: 2.5.0 trunk > upgrade ambari to 2.1.1 error > - > > Key: AMBARI-18441 > URL: https://issues.apache.org/jira/browse/AMBARI-18441 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: trunk, 2.5.0 > > Attachments: upgrade.png > > > ambari upgrade to 2.1.1, if the first time failed , excute ambari-server > upgrade again will error duplicate key value violates unique constraint > "pk_hostcomponentstate" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18414) rolling restart services user login audit log show error
[ https://issues.apache.org/jira/browse/AMBARI-18414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18414: Component/s: ambari-server > rolling restart services user login audit log show error > - > > Key: AMBARI-18414 > URL: https://issues.apache.org/jira/browse/AMBARI-18414 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin > Fix For: 2.5.0 > > Attachments: rolling restart.png > > > when rolling restart service, audit log will show info about user login > ,and remoteIp is 127.0.0.1 > 2016-09-18T18:07:30.604+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(29) > 2016-09-18T18:07:30.604+0800, User(admin), Operation(CUSTOM_COMMAND > DATANODE), Details(RESTART HDFS/DATANODE), Status(QUEUED), RequestId(29), > TaskId(127), Hostname(hostname) > 2016-09-18T18:07:30.610+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:30.610+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) > 2016-09-18T18:07:35.680+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:35.680+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) > 2016-09-18T18:07:40.692+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:40.692+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18414) rolling restart services user login audit log show error
[ https://issues.apache.org/jira/browse/AMBARI-18414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18414: Description: when rolling restart service, audit log will show info about user login ,and remoteIp is 127.0.0.1 2016-09-18T18:07:30.604+0800, User(admin), Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), RequestId(29) 2016-09-18T18:07:30.604+0800, User(admin), Operation(CUSTOM_COMMAND DATANODE), Details(RESTART HDFS/DATANODE), Status(QUEUED), RequestId(29), TaskId(127), Hostname(hostname) 2016-09-18T18:07:30.610+0800, User(null), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Failed), Reason(Authentication required) 2016-09-18T18:07:30.610+0800, User(internal), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Success) 2016-09-18T18:07:35.680+0800, User(null), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Failed), Reason(Authentication required) 2016-09-18T18:07:35.680+0800, User(internal), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Success) 2016-09-18T18:07:40.692+0800, User(null), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Failed), Reason(Authentication required) 2016-09-18T18:07:40.692+0800, User(internal), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Success) was: 2016-09-18T18:07:30.604+0800, User(admin), Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), RequestId(29) 2016-09-18T18:07:30.604+0800, User(admin), Operation(CUSTOM_COMMAND DATANODE), Details(RESTART HDFS/DATANODE), Status(QUEUED), RequestId(29), TaskId(127), Hostname(hostname) 2016-09-18T18:07:30.610+0800, User(null), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Failed), Reason(Authentication required) 2016-09-18T18:07:30.610+0800, User(internal), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Success) 2016-09-18T18:07:35.680+0800, User(null), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Failed), Reason(Authentication required) 2016-09-18T18:07:35.680+0800, User(internal), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Success) 2016-09-18T18:07:40.692+0800, User(null), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Failed), Reason(Authentication required) 2016-09-18T18:07:40.692+0800, User(internal), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Success) > rolling restart services user login audit log show error > - > > Key: AMBARI-18414 > URL: https://issues.apache.org/jira/browse/AMBARI-18414 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: wangyaoxin > Fix For: 2.5.0 > > Attachments: rolling restart.png > > > when rolling restart service, audit log will show info about user login > ,and remoteIp is 127.0.0.1 > 2016-09-18T18:07:30.604+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(29) > 2016-09-18T18:07:30.604+0800, User(admin), Operation(CUSTOM_COMMAND > DATANODE), Details(RESTART HDFS/DATANODE), Status(QUEUED), RequestId(29), > TaskId(127), Hostname(hostname) > 2016-09-18T18:07:30.610+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:30.610+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) > 2016-09-18T18:07:35.680+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:35.680+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) > 2016-09-18T18:07:40.692+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:40.692+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18414) rolling restart services user login audit log show error
wangyaoxin created AMBARI-18414: --- Summary: rolling restart services user login audit log show error Key: AMBARI-18414 URL: https://issues.apache.org/jira/browse/AMBARI-18414 Project: Ambari Issue Type: Bug Affects Versions: trunk Reporter: wangyaoxin Fix For: 2.5.0 Attachments: rolling restart.png 2016-09-18T18:07:30.604+0800, User(admin), Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), RequestId(29) 2016-09-18T18:07:30.604+0800, User(admin), Operation(CUSTOM_COMMAND DATANODE), Details(RESTART HDFS/DATANODE), Status(QUEUED), RequestId(29), TaskId(127), Hostname(hostname) 2016-09-18T18:07:30.610+0800, User(null), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Failed), Reason(Authentication required) 2016-09-18T18:07:30.610+0800, User(internal), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Success) 2016-09-18T18:07:35.680+0800, User(null), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Failed), Reason(Authentication required) 2016-09-18T18:07:35.680+0800, User(internal), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Success) 2016-09-18T18:07:40.692+0800, User(null), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Failed), Reason(Authentication required) 2016-09-18T18:07:40.692+0800, User(internal), RemoteIp(127.0.0.1), Operation(User login), Roles( ), Status(Success) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18414) rolling restart services user login audit log show error
[ https://issues.apache.org/jira/browse/AMBARI-18414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18414: Attachment: rolling restart.png > rolling restart services user login audit log show error > - > > Key: AMBARI-18414 > URL: https://issues.apache.org/jira/browse/AMBARI-18414 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk >Reporter: wangyaoxin > Fix For: 2.5.0 > > Attachments: rolling restart.png > > > 2016-09-18T18:07:30.604+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(29) > 2016-09-18T18:07:30.604+0800, User(admin), Operation(CUSTOM_COMMAND > DATANODE), Details(RESTART HDFS/DATANODE), Status(QUEUED), RequestId(29), > TaskId(127), Hostname(hostname) > 2016-09-18T18:07:30.610+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:30.610+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) > 2016-09-18T18:07:35.680+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:35.680+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) > 2016-09-18T18:07:40.692+0800, User(null), RemoteIp(127.0.0.1), Operation(User > login), Roles( > ), Status(Failed), Reason(Authentication required) > 2016-09-18T18:07:40.692+0800, User(internal), RemoteIp(127.0.0.1), > Operation(User login), Roles( > ), Status(Success) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Attachment: AMBARI-18374_03.patch > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: 2.5.0 > > Attachments: AMBARI-18374.patch, AMBARI-18374_01.patch, > AMBARI-18374_02.patch, AMBARI-18374_03.patch, c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null > 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), > Operation(Request from server), RequestType(POST), > url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 > Accepted), Command(RESTART), Cluster name(null) > 2016-09-13T17:29:22.042+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(15) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17518) improve resourcemanager HA description
[ https://issues.apache.org/jira/browse/AMBARI-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17518: Resolution: Fixed Status: Resolved (was: Patch Available) > improve resourcemanager HA description > -- > > Key: AMBARI-17518 > URL: https://issues.apache.org/jira/browse/AMBARI-17518 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17518.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Attachment: AMBARI-18374_02.patch > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: 2.5.0 > > Attachments: AMBARI-18374.patch, AMBARI-18374_01.patch, > AMBARI-18374_02.patch, c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null > 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), > Operation(Request from server), RequestType(POST), > url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 > Accepted), Command(RESTART), Cluster name(null) > 2016-09-13T17:29:22.042+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(15) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Attachment: (was: AMBARI-18374_02.patch) > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: 2.5.0 > > Attachments: AMBARI-18374.patch, AMBARI-18374_01.patch, c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null > 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), > Operation(Request from server), RequestType(POST), > url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 > Accepted), Command(RESTART), Cluster name(null) > 2016-09-13T17:29:22.042+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(15) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Attachment: AMBARI-18374_02.patch > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Fix For: 2.5.0 > > Attachments: AMBARI-18374.patch, AMBARI-18374_01.patch, > AMBARI-18374_02.patch, c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null > 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), > Operation(Request from server), RequestType(POST), > url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 > Accepted), Command(RESTART), Cluster name(null) > 2016-09-13T17:29:22.042+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(15) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Attachment: AMBARI-18374_01.patch > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Attachments: AMBARI-18374.patch, AMBARI-18374_01.patch, c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null > 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), > Operation(Request from server), RequestType(POST), > url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 > Accepted), Command(RESTART), Cluster name(null) > 2016-09-13T17:29:22.042+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(15) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Attachment: (was: AMBARI-18374-1.patch) > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Attachments: AMBARI-18374.patch, c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null > 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), > Operation(Request from server), RequestType(POST), > url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 > Accepted), Command(RESTART), Cluster name(null) > 2016-09-13T17:29:22.042+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(15) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Attachment: AMBARI-18374-1.patch > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Attachments: AMBARI-18374-1.patch, AMBARI-18374.patch, c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null > 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), > Operation(Request from server), RequestType(POST), > url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 > Accepted), Command(RESTART), Cluster name(null) > 2016-09-13T17:29:22.042+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(15) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17518) improve resourcemanager HA description
[ https://issues.apache.org/jira/browse/AMBARI-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487492#comment-15487492 ] wangyaoxin commented on AMBARI-17518: - Hi [~akovalenko] , [~ncole] Thank you for review my patch and ship it , I have to trouble you to commit the patch ! > improve resourcemanager HA description > -- > > Key: AMBARI-17518 > URL: https://issues.apache.org/jira/browse/AMBARI-17518 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17518.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Status: Patch Available (was: Open) > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Attachments: AMBARI-18374.patch, c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null > 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), > Operation(Request from server), RequestType(POST), > url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 > Accepted), Command(RESTART), Cluster name(null) > 2016-09-13T17:29:22.042+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(15) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Attachment: AMBARI-18374.patch > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Attachments: AMBARI-18374.patch, c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null > 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), > Operation(Request from server), RequestType(POST), > url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 > Accepted), Command(RESTART), Cluster name(null) > 2016-09-13T17:29:22.042+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(15) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Description: when rolling restart services ( eg:DataNode ) ,cluster name in audit log show null 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), Operation(Request from server), RequestType(POST), url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 Accepted), Command(RESTART), Cluster name(null) 2016-09-13T17:29:22.042+0800, User(admin), Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), RequestId(15) was:when rolling restart services ( eg:DataNode ) ,cluster name in audit log show null > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Attachments: c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null > 2016-09-13T17:29:22.033+0800, User(admin), RemoteIp(127.0.0.1), > Operation(Request from server), RequestType(POST), > url(http://localhost:8080/api/v1/clusters/amabri/requests), ResultStatus(202 > Accepted), Command(RESTART), Cluster name(null) > 2016-09-13T17:29:22.042+0800, User(admin), > Operation(_PARSE_.ROLLING-RESTART.DATANODE.1.1), Status(IN_PROGRESS), > RequestId(15) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Attachment: d.png > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Attachments: c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18374) rolling restart datanode cluster name show null
[ https://issues.apache.org/jira/browse/AMBARI-18374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18374: Attachment: c.png > rolling restart datanode cluster name show null > > > Key: AMBARI-18374 > URL: https://issues.apache.org/jira/browse/AMBARI-18374 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Labels: ambari-server > Attachments: c.png, d.png > > > when rolling restart services ( eg:DataNode ) ,cluster name in audit log show > null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18374) rolling restart datanode cluster name show null
wangyaoxin created AMBARI-18374: --- Summary: rolling restart datanode cluster name show null Key: AMBARI-18374 URL: https://issues.apache.org/jira/browse/AMBARI-18374 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: trunk Reporter: wangyaoxin Assignee: wangyaoxin when rolling restart services ( eg:DataNode ) ,cluster name in audit log show null -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15477199#comment-15477199 ] wangyaoxin edited comment on AMBARI-17728 at 9/12/16 1:13 PM: -- Hi [~afernandez], [~jluniya] ,[~smnaha] , thank you for review my patch and ship it from the reviewboard , I have to trouble you to commit the patch! Thank you ! was (Author: forestsissi): Hi [~jluniya] ,[~smnaha] , trouble you to commit the patch!Thank you ! > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728-2.patch, > AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15477199#comment-15477199 ] wangyaoxin edited comment on AMBARI-17728 at 9/12/16 8:35 AM: -- Hi [~jluniya] ,[~smnaha] , trouble you to commit the patch!Thank you ! was (Author: forestsissi): Have been shiped from ReviewBoard > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728-2.patch, > AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15477199#comment-15477199 ] wangyaoxin edited comment on AMBARI-17728 at 9/9/16 2:40 PM: - Have been shiped from ReviewBoard was (Author: forestsissi): Have been shiped ! > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728-2.patch, > AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448750#comment-15448750 ] wangyaoxin edited comment on AMBARI-17728 at 9/1/16 12:09 AM: -- Hi ,[~afernandez], thank you for review my patch, I have to trouble you to commit the patch. Thank you! was (Author: forestsissi): Hi ,[~afernandez], thank you for review my patch, I have to trouble you to commit the patch. Thank you! > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728-2.patch, > AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448750#comment-15448750 ] wangyaoxin edited comment on AMBARI-17728 at 8/30/16 11:08 AM: --- Hi ,[~afernandez], thank you for review my patch, I have to trouble you to commit the patch. Thank you! was (Author: forestsissi): Hi ,[~alejandro.villa], thank you for review my patch, I have to trouble you to commit the patch. Thank you! > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728-2.patch, > AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15448750#comment-15448750 ] wangyaoxin commented on AMBARI-17728: - Hi ,[~alejandro.villa], thank you for review my patch, I have to trouble you to commit the patch. Thank you! > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728-2.patch, > AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17728: Component/s: ambari-server > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728-2.patch, > AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17728: Attachment: AMBARI-17728-2.patch > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728-2.patch, > AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432399#comment-15432399 ] wangyaoxin commented on AMBARI-17728: - [~afernandez] I have fixed the exit 0 problem, and attached a new patch AMBARI-17728-1.patch . I am appreciated for your kind-hearted offer, thank you ! > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17728: Attachment: AMBARI-17728-1.patch > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728-1.patch, AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17728) Error message does not deliver when executing ambari-server command as a non-root user
[ https://issues.apache.org/jira/browse/AMBARI-17728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17728: Assignee: wangyaoxin > Error message does not deliver when executing ambari-server command as a > non-root user > -- > > Key: AMBARI-17728 > URL: https://issues.apache.org/jira/browse/AMBARI-17728 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17728.patch > > > non-root user: like hdfs > excute : ambari-server stop > show : Using python /usr/bin/python2.6 Stopping ambari-server > intent to: You can't perform this operation as non-sudoer user. Please, > re-login or configure sudo access for this user -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17546) Host Namenode Rebalance HDFS failed
[ https://issues.apache.org/jira/browse/AMBARI-17546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17546: Assignee: wangyaoxin > Host Namenode Rebalance HDFS failed > --- > > Key: AMBARI-17546 > URL: https://issues.apache.org/jira/browse/AMBARI-17546 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.1.1 >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: 27c1ae6cdac7fd2fc6906689d50cb4da.png, > 594db9768b707ec62cd336f4d2aa445c.png, AMBARI-17546.patch > > > the host view ,excute namenode rebalance HDFS, json none lead fail . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17518) improve resourcemanager HA description
[ https://issues.apache.org/jira/browse/AMBARI-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17518: Assignee: wangyaoxin > improve resourcemanager HA description > -- > > Key: AMBARI-17518 > URL: https://issues.apache.org/jira/browse/AMBARI-17518 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: wangyaoxin >Assignee: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17518.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17668) optimize log description of ambari agent stop
[ https://issues.apache.org/jira/browse/AMBARI-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427743#comment-15427743 ] wangyaoxin commented on AMBARI-17668: - [~afernandez] [~Kuldeepm]I have fixed the extra space problem, and attached a new patch AMBARI-17668-1.patch ,but i don't have the authority to commit,so i will trouble you to commit the patch. Thank you ! > optimize log description of ambari agent stop > - > > Key: AMBARI-17668 > URL: https://issues.apache.org/jira/browse/AMBARI-17668 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Affects Versions: trunk >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17668-1.patch, AMBARI-17668.patch > > > excute ambari agent ，going to execute kill -9，but none output log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17668) optimize log description of ambari agent stop
[ https://issues.apache.org/jira/browse/AMBARI-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17668: Attachment: AMBARI-17668-1.patch > optimize log description of ambari agent stop > - > > Key: AMBARI-17668 > URL: https://issues.apache.org/jira/browse/AMBARI-17668 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Affects Versions: trunk >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17668-1.patch, AMBARI-17668.patch > > > excute ambari agent ，going to execute kill -9，but none output log -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18001) operationStatus and taskStatus audit log should contain remoteIp message
[ https://issues.apache.org/jira/browse/AMBARI-18001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18001: Affects Version/s: (was: 2.4.0) > operationStatus and taskStatus audit log should contain remoteIp message > - > > Key: AMBARI-18001 > URL: https://issues.apache.org/jira/browse/AMBARI-18001 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-18001.patch, AMBARI-18001_01.patch > > > OperationStatusAuditEvent and TaskStatusAuditEvent auditlog message should > contain the remoteip info, store in the pg table host_role_command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18001) operationStatus and taskStatus audit log should contain remoteIp message
[ https://issues.apache.org/jira/browse/AMBARI-18001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18001: Attachment: AMBARI-18001_01.patch > operationStatus and taskStatus audit log should contain remoteIp message > - > > Key: AMBARI-18001 > URL: https://issues.apache.org/jira/browse/AMBARI-18001 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-18001.patch, AMBARI-18001_01.patch > > > OperationStatusAuditEvent and TaskStatusAuditEvent auditlog message should > contain the remoteip info, store in the pg table host_role_command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18001) operationStatus and taskStatus audit log should contain remoteIp message
[ https://issues.apache.org/jira/browse/AMBARI-18001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18001: Status: Patch Available (was: Open) > operationStatus and taskStatus audit log should contain remoteIp message > - > > Key: AMBARI-18001 > URL: https://issues.apache.org/jira/browse/AMBARI-18001 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-18001.patch > > > OperationStatusAuditEvent and TaskStatusAuditEvent auditlog message should > contain the remoteip info, store in the pg table host_role_command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18001) operationStatus and taskStatus audit log should contain remoteIp message
[ https://issues.apache.org/jira/browse/AMBARI-18001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18001: Summary: operationStatus and taskStatus audit log should contain remoteIp message (was: operation and task audit log should contain remoteip message) > operationStatus and taskStatus audit log should contain remoteIp message > - > > Key: AMBARI-18001 > URL: https://issues.apache.org/jira/browse/AMBARI-18001 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-18001.patch > > > OperationStatusAuditEvent and TaskStatusAuditEvent auditlog message should > contain the remoteip info, store in the pg table host_role_command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18001) operation and task audit event should contain remoteip message
[ https://issues.apache.org/jira/browse/AMBARI-18001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18001: Description: OperationStatusAuditEvent and TaskStatusAuditEvent auditlog message should contain the remoteip info, store in the pg table host_role_command > operation and task audit event should contain remoteip message > -- > > Key: AMBARI-18001 > URL: https://issues.apache.org/jira/browse/AMBARI-18001 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-18001.patch > > > OperationStatusAuditEvent and TaskStatusAuditEvent auditlog message should > contain the remoteip info, store in the pg table host_role_command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18001) operation and task audit log should contain remoteip message
[ https://issues.apache.org/jira/browse/AMBARI-18001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18001: Summary: operation and task audit log should contain remoteip message (was: operation and task audit event should contain remoteip message) > operation and task audit log should contain remoteip message > - > > Key: AMBARI-18001 > URL: https://issues.apache.org/jira/browse/AMBARI-18001 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-18001.patch > > > OperationStatusAuditEvent and TaskStatusAuditEvent auditlog message should > contain the remoteip info, store in the pg table host_role_command -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18001) operation and task audit event should contain remoteip message
[ https://issues.apache.org/jira/browse/AMBARI-18001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-18001: Attachment: AMBARI-18001.patch > operation and task audit event should contain remoteip message > -- > > Key: AMBARI-18001 > URL: https://issues.apache.org/jira/browse/AMBARI-18001 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.4.0 >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-18001.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18001) operation and task audit event should contain remoteip message
wangyaoxin created AMBARI-18001: --- Summary: operation and task audit event should contain remoteip message Key: AMBARI-18001 URL: https://issues.apache.org/jira/browse/AMBARI-18001 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: trunk, 2.4.0 Reporter: wangyaoxin Fix For: trunk -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17518) improve resourcemanager HA description
[ https://issues.apache.org/jira/browse/AMBARI-17518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangyaoxin updated AMBARI-17518: Affects Version/s: trunk > improve resourcemanager HA description > -- > > Key: AMBARI-17518 > URL: https://issues.apache.org/jira/browse/AMBARI-17518 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: wangyaoxin > Fix For: trunk > > Attachments: AMBARI-17518.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
