[jira] [Commented] (AMBARI-19386) ATLAS service check should run against metadata server host
[ https://issues.apache.org/jira/browse/AMBARI-19386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15821034#comment-15821034 ] Vishal Suvagia commented on AMBARI-19386: - committed on [branch-2.5|https://github.com/apache/ambari/commit/20380d69270ab64933855dd1668305b14f39e91c] and [trunk|https://github.com/apache/ambari/commit/4975864796b9a301f4e0ee0b36673f41cb0f1b21] > ATLAS service check should run against metadata server host > --- > > Key: AMBARI-19386 > URL: https://issues.apache.org/jira/browse/AMBARI-19386 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19386.patch > > > Atlas service check fails as its hard coded to run check against the same > host where service check is running. It should instead run check against > ATLAS metadata server host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19386) ATLAS service check should run against metadata server host
[ https://issues.apache.org/jira/browse/AMBARI-19386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820326#comment-15820326 ] Hudson commented on AMBARI-19386: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6416 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6416/]) AMBARI-19386 : ATLAS service check should explicitly run against (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4975864796b9a301f4e0ee0b36673f41cb0f1b21]) * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/service_check.py > ATLAS service check should run against metadata server host > --- > > Key: AMBARI-19386 > URL: https://issues.apache.org/jira/browse/AMBARI-19386 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19386.patch > > > Atlas service check fails as its hard coded to run check against the same > host where service check is running. It should instead run check against > ATLAS metadata server host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-19386) ATLAS service check should run against metadata server host
[ https://issues.apache.org/jira/browse/AMBARI-19386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15820312#comment-15820312 ] Hudson commented on AMBARI-19386: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #694 (See [https://builds.apache.org/job/Ambari-branch-2.5/694/]) AMBARI-19386 : ATLAS service check should explicitly run against (mugdha: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=20380d69270ab64933855dd1668305b14f39e91c]) * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/params.py * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.1.0.2.3/package/scripts/service_check.py > ATLAS service check should run against metadata server host > --- > > Key: AMBARI-19386 > URL: https://issues.apache.org/jira/browse/AMBARI-19386 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: Vishal Suvagia >Assignee: Vishal Suvagia > Fix For: 2.5.0 > > Attachments: AMBARI-19386.patch > > > Atlas service check fails as its hard coded to run check against the same > host where service check is running. It should instead run check against > ATLAS metadata server host. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
