[jira] [Resolved] (AMBARI-25056) Fix typo in setup-ldap docs
[
https://issues.apache.org/jira/browse/AMBARI-25056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-25056.
-
Resolution: Fixed
> Fix typo in setup-ldap docs
> ---
>
> Key: AMBARI-25056
> URL: https://issues.apache.org/jira/browse/AMBARI-25056
> Project: Ambari
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.8.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Minor
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Fixing a typo in the doc:
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/security/ldap/index.md
> where a non-interactive mode key is incorrectly set as {{ldap-manage-servic}}
> where as it should be {{ldap-manage-services}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25056) Fix typo in setup-ldap docs
[
https://issues.apache.org/jira/browse/AMBARI-25056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-25056:
Priority: Trivial (was: Minor)
> Fix typo in setup-ldap docs
> ---
>
> Key: AMBARI-25056
> URL: https://issues.apache.org/jira/browse/AMBARI-25056
> Project: Ambari
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.8.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Trivial
> Fix For: 2.8.0
>
>
> Fixing a typo in the doc:
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/security/ldap/index.md
> where a non-interactive mode key is incorrectly set as {{ldap-manage-servic}}
> where as it should be {{ldap-manage-services}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25056) Fix typo in setup-ldap docs
[
https://issues.apache.org/jira/browse/AMBARI-25056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-25056:
Priority: Minor (was: Trivial)
> Fix typo in setup-ldap docs
> ---
>
> Key: AMBARI-25056
> URL: https://issues.apache.org/jira/browse/AMBARI-25056
> Project: Ambari
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.8.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Minor
> Fix For: 2.8.0
>
>
> Fixing a typo in the doc:
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/security/ldap/index.md
> where a non-interactive mode key is incorrectly set as {{ldap-manage-servic}}
> where as it should be {{ldap-manage-services}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25056) Fix typo in setup-ldap docs
[
https://issues.apache.org/jira/browse/AMBARI-25056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-25056:
Description:
Fixing a typo in the doc:
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/security/ldap/index.md
where a non-interactive mode key is incorrectly set as {{ldap-manage-servic}}
where as it should be {{ldap-manage-services}}
was:
Fixing a typo in the doc:
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/security/ldap/index.md
where a non-interactive mode key is incorrectly set as {{-ldap-manage-servic}}
where as it should be {{--ldap-manage-services}}
> Fix typo in setup-ldap docs
> ---
>
> Key: AMBARI-25056
> URL: https://issues.apache.org/jira/browse/AMBARI-25056
> Project: Ambari
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.8.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Minor
> Fix For: 2.8.0
>
>
> Fixing a typo in the doc:
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/security/ldap/index.md
> where a non-interactive mode key is incorrectly set as {{ldap-manage-servic}}
> where as it should be {{ldap-manage-services}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25056) Fix typo in setup-ldap docs
[
https://issues.apache.org/jira/browse/AMBARI-25056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-25056:
Description:
Fixing a typo in the doc:
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/security/ldap/index.md
where a non-interactive mode key is incorrectly set as {{-ldap-manage-servic}}
where as it should be {{--ldap-manage-services}}
was:
Fixing a typo in the doc:
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/security/ldap/index.md
where a non-interactive mode key is incorrectly set as {{--ldap-manage-servic}}
where as it should be {{--ldap-manage-services}}
> Fix typo in setup-ldap docs
> ---
>
> Key: AMBARI-25056
> URL: https://issues.apache.org/jira/browse/AMBARI-25056
> Project: Ambari
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.8.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Minor
> Fix For: 2.8.0
>
>
> Fixing a typo in the doc:
> https://github.com/apache/ambari/blob/trunk/ambari-server/docs/security/ldap/index.md
> where a non-interactive mode key is incorrectly set as
> {{-ldap-manage-servic}} where as it should be {{--ldap-manage-services}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25056) Fix typo in setup-ldap docs
Srikanth Janardhan created AMBARI-25056:
---
Summary: Fix typo in setup-ldap docs
Key: AMBARI-25056
URL: https://issues.apache.org/jira/browse/AMBARI-25056
Project: Ambari
Issue Type: Bug
Components: documentation
Affects Versions: 2.8.0
Reporter: Srikanth Janardhan
Assignee: Srikanth Janardhan
Fix For: 2.8.0
Fixing a typo in the doc:
https://github.com/apache/ambari/blob/trunk/ambari-server/docs/security/ldap/index.md
where a non-interactive mode key is incorrectly set as {{--ldap-manage-servic}}
where as it should be {{--ldap-manage-services}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24603) Hard to scroll components list in Host details -> Logs page when there are > 15 components in host
[ https://issues.apache.org/jira/browse/AMBARI-24603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan resolved AMBARI-24603. - Resolution: Fixed > Hard to scroll components list in Host details -> Logs page when there are > > 15 components in host > -- > > Key: AMBARI-24603 > URL: https://issues.apache.org/jira/browse/AMBARI-24603 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 11.26.05 PM.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > > When there are lot of components installed in a host, it is hard to scroll > list of all components in Host Details -> Logs Page. > Fix: to add a scroller. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24572) Cluster name is not aligned with background ops
[ https://issues.apache.org/jira/browse/AMBARI-24572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan resolved AMBARI-24572. - Resolution: Fixed > Cluster name is not aligned with background ops > > > Key: AMBARI-24572 > URL: https://issues.apache.org/jira/browse/AMBARI-24572 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 10.49.00 PM.png > > Time Spent: 2h 40m > Remaining Estimate: 0h > > When the cluster name is long, the cluster name overflows to the next line, > even though there is a lot of gap to accomodate the cluster name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24603) Hard to scroll components list in Host details -> Logs page when there are > 15 components in host
[ https://issues.apache.org/jira/browse/AMBARI-24603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan updated AMBARI-24603: Fix Version/s: (was: 2.8.0) 2.7.3 > Hard to scroll components list in Host details -> Logs page when there are > > 15 components in host > -- > > Key: AMBARI-24603 > URL: https://issues.apache.org/jira/browse/AMBARI-24603 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 11.26.05 PM.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > > When there are lot of components installed in a host, it is hard to scroll > list of all components in Host Details -> Logs Page. > Fix: to add a scroller. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24572) Cluster name is not aligned with background ops
[ https://issues.apache.org/jira/browse/AMBARI-24572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan updated AMBARI-24572: Fix Version/s: (was: 2.8.0) 2.7.3 > Cluster name is not aligned with background ops > > > Key: AMBARI-24572 > URL: https://issues.apache.org/jira/browse/AMBARI-24572 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-09-06 at 10.49.00 PM.png > > Time Spent: 2h 40m > Remaining Estimate: 0h > > When the cluster name is long, the cluster name overflows to the next line, > even though there is a lot of gap to accomodate the cluster name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24864) Delete host confirm popup does not contain all master components
[ https://issues.apache.org/jira/browse/AMBARI-24864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan updated AMBARI-24864: Description: # Navigate to host with one or more masters # Click Delete Host from the Host Actions menu Observed: All the masters are not mentioned in the popup. This is a frontend bug !Screen Shot 2018-11-05 at 2.47.04 PM.png! was: # Navigate to host with one or more masters # Click Delete Host from the Host Actions menu Observed: All the masters are not mentioned in the popup. This is a frontend bug > Delete host confirm popup does not contain all master components > > > Key: AMBARI-24864 > URL: https://issues.apache.org/jira/browse/AMBARI-24864 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Srikanth Janardhan >Assignee: Andrii Tkach >Priority: Major > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-11-05 at 2.47.04 PM.png > > > # Navigate to host with one or more masters > # Click Delete Host from the Host Actions menu > Observed: All the masters are not mentioned in the popup. This is a frontend > bug > !Screen Shot 2018-11-05 at 2.47.04 PM.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24864) Delete host confirm popup does not contain all master components
[ https://issues.apache.org/jira/browse/AMBARI-24864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan updated AMBARI-24864: Attachment: Screen Shot 2018-11-05 at 2.47.04 PM.png > Delete host confirm popup does not contain all master components > > > Key: AMBARI-24864 > URL: https://issues.apache.org/jira/browse/AMBARI-24864 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Srikanth Janardhan >Assignee: Andrii Tkach >Priority: Major > Fix For: 2.7.3 > > Attachments: Screen Shot 2018-11-05 at 2.47.04 PM.png > > > # Navigate to host with one or more masters > # Click Delete Host from the Host Actions menu > Observed: All the masters are not mentioned in the popup. This is a frontend > bug -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24864) Delete host confirm popup does not contain all master components
Srikanth Janardhan created AMBARI-24864: --- Summary: Delete host confirm popup does not contain all master components Key: AMBARI-24864 URL: https://issues.apache.org/jira/browse/AMBARI-24864 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.3 Reporter: Srikanth Janardhan Assignee: Andrii Tkach Fix For: 2.7.3 # Navigate to host with one or more masters # Click Delete Host from the Host Actions menu Observed: All the masters are not mentioned in the popup. This is a frontend bug -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24863) [PERF] Install 250 components request failed when adding hosts
Srikanth Janardhan created AMBARI-24863:
---
Summary: [PERF] Install 250 components request failed when adding
hosts
Key: AMBARI-24863
URL: https://issues.apache.org/jira/browse/AMBARI-24863
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.3
Reporter: Srikanth Janardhan
Fix For: 2.7.3
Attachments: ambari-server-500hosts-addHosts.log
Install components failed on more than 70 hosts out of 250 hosts that were
being added
Ambari server log: [^ambari-server-500hosts-addHosts.log]
{code:title=BGOps logs}
stderr:
Command aborted. Reason: 'Server considered task failed and automatically
aborted it'
stdout:
Command aborted. Reason: 'Server considered task failed and automatically
aborted it'
Command failed after 1 tries
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24697) [Intermittent] Client installation failures when parallel_execution enabled
[
https://issues.apache.org/jira/browse/AMBARI-24697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-24697:
Description:
Several client installation failing in a baked image setup due to timeout with
Ambari-2.7.3.0-6
{code:title=Infra Solr Client Install failed}
stderr:
Python script has been killed due to timeout after waiting 2400 secs
stdout:
2018-09-26 04:30:05,749 - Stack Feature Version Info: Cluster Stack=3.0,
Command Stack=None, Command Version=None -> 3.0
2018-09-26 04:30:05,769 - Using hadoop conf dir:
/usr/hdp/current/hadoop-client/conf
2018-09-26 04:30:05,773 - Group['cstm-users'] {}
2018-09-26 04:30:05,776 - Group['cstm-kms'] {}
2018-09-26 04:30:05,777 - Group['cstm-ranger'] {}
2018-09-26 04:30:05,777 - Group['cstm-zeppelin'] {}
2018-09-26 04:30:05,778 - Group['hdfs'] {}
2018-09-26 04:30:05,778 - Group['cstm-livy'] {}
2018-09-26 04:30:05,779 - Group['hadoop'] {}
2018-09-26 04:30:05,779 - Group['cstm-knox'] {}
2018-09-26 04:30:05,779 - Group['cstm-spark'] {}
2018-09-26 04:30:05,782 - User['yarn-ats'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,786 - User['superset'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,790 - User['cstm-hive'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,794 - User['cstm-sqoop'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,797 - User['cstm-yarn'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,801 - User['cstm-tez'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None}
2018-09-26 04:30:05,805 - User['cstm-storm'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,809 - User['cstm-kafka'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,840 - Adding user User['cstm-kafka']
2018-09-26 04:30:05,945 - User['cstm-logsearch'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,946 - Adding user User['cstm-logsearch']
2018-09-26 04:30:06,283 - User['cstm-infra-solr'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:06,284 - Adding user User['cstm-infra-solr']
2018-09-26 04:30:06,491 - User['cstm-mr'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:06,492 - Adding user User['cstm-mr']
2018-09-26 04:30:06,732 - User['cstm-zeppelin'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-zeppelin', 'hadoop'], 'uid':
None}
2018-09-26 04:30:06,733 - Adding user User['cstm-zeppelin']
2018-09-26 04:30:07,044 - User['cstm-oozie'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None}
2018-09-26 04:30:07,045 - Adding user User['cstm-oozie']
2018-09-26 04:30:07,404 - User['cstm-kms'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-kms', 'hadoop'], 'uid': None}
2018-09-26 04:30:07,405 - Adding user User['cstm-kms']
2018-09-26 04:30:07,660 - User['cstm-ranger'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-ranger', 'hadoop'], 'uid': None}
2018-09-26 04:30:07,665 - User['cstm-ams'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:07,666 - Adding user User['cstm-ams']
2018-09-26 04:30:07,920 - User['cstm-atlas'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:07,920 - Adding user User['cstm-atlas']
2018-09-26 04:30:08,060 - User['cstm-knox'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'cstm-knox'], 'uid': None}
2018-09-26 04:30:08,062 - Modifying user cstm-knox
2018-09-26 04:30:08,263 - User['cstm-hbase'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:08,273 - User['cstm-hdfs'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
2018-09-26 04:30:08,274 - Adding user User['cstm-hdfs']
2018-09-26 04:30:08,435 - User['druid'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:08,437 - Modifying user druid
2018-09-26 04:30:08,610 - User['ambari-qa'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None}
2018-09-26 04:30:08,619 - User['cstm-zookeeper'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:08,620 - Adding user User['cstm-zookeeper']
2018-09-26 04:30:08,842 - User['cstm-livy'] {'gid': 'hadoop',
'fetch_no
[jira] [Created] (AMBARI-24697) [Intermittent] Client installation failures when parallel_execution enabled
Srikanth Janardhan created AMBARI-24697:
---
Summary: [Intermittent] Client installation failures when
parallel_execution enabled
Key: AMBARI-24697
URL: https://issues.apache.org/jira/browse/AMBARI-24697
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.2
Reporter: Srikanth Janardhan
Fix For: 2.7.2
Several client installation failing in a baked image setup due to timeout with
Ambari-2.7.3.0-6
{code:title=Infra Solr Client Install failed}
stderr:
Python script has been killed due to timeout after waiting 2400 secs
stdout:
2018-09-26 04:30:05,749 - Stack Feature Version Info: Cluster Stack=3.0,
Command Stack=None, Command Version=None -> 3.0
2018-09-26 04:30:05,769 - Using hadoop conf dir:
/usr/hdp/current/hadoop-client/conf
2018-09-26 04:30:05,773 - Group['cstm-users'] {}
2018-09-26 04:30:05,776 - Group['cstm-kms'] {}
2018-09-26 04:30:05,777 - Group['cstm-ranger'] {}
2018-09-26 04:30:05,777 - Group['cstm-zeppelin'] {}
2018-09-26 04:30:05,778 - Group['hdfs'] {}
2018-09-26 04:30:05,778 - Group['cstm-livy'] {}
2018-09-26 04:30:05,779 - Group['hadoop'] {}
2018-09-26 04:30:05,779 - Group['cstm-knox'] {}
2018-09-26 04:30:05,779 - Group['cstm-spark'] {}
2018-09-26 04:30:05,782 - User['yarn-ats'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,786 - User['superset'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,790 - User['cstm-hive'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,794 - User['cstm-sqoop'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,797 - User['cstm-yarn'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,801 - User['cstm-tez'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None}
2018-09-26 04:30:05,805 - User['cstm-storm'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,809 - User['cstm-kafka'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,840 - Adding user User['cstm-kafka']
2018-09-26 04:30:05,945 - User['cstm-logsearch'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:05,946 - Adding user User['cstm-logsearch']
2018-09-26 04:30:06,283 - User['cstm-infra-solr'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:06,284 - Adding user User['cstm-infra-solr']
2018-09-26 04:30:06,491 - User['cstm-mr'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:06,492 - Adding user User['cstm-mr']
2018-09-26 04:30:06,732 - User['cstm-zeppelin'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-zeppelin', 'hadoop'], 'uid':
None}
2018-09-26 04:30:06,733 - Adding user User['cstm-zeppelin']
2018-09-26 04:30:07,044 - User['cstm-oozie'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None}
2018-09-26 04:30:07,045 - Adding user User['cstm-oozie']
2018-09-26 04:30:07,404 - User['cstm-kms'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-kms', 'hadoop'], 'uid': None}
2018-09-26 04:30:07,405 - Adding user User['cstm-kms']
2018-09-26 04:30:07,660 - User['cstm-ranger'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-ranger', 'hadoop'], 'uid': None}
2018-09-26 04:30:07,665 - User['cstm-ams'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:07,666 - Adding user User['cstm-ams']
2018-09-26 04:30:07,920 - User['cstm-atlas'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:07,920 - Adding user User['cstm-atlas']
2018-09-26 04:30:08,060 - User['cstm-knox'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop', 'cstm-knox'], 'uid': None}
2018-09-26 04:30:08,062 - Modifying user cstm-knox
2018-09-26 04:30:08,263 - User['cstm-hbase'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:08,273 - User['cstm-hdfs'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
2018-09-26 04:30:08,274 - Adding user User['cstm-hdfs']
2018-09-26 04:30:08,435 - User['druid'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
2018-09-26 04:30:08,437 - Modifying user druid
2018-09-26 04:30:08,610 - User['ambari-qa'] {'gid': 'hadoop',
'fetch_nonlocal_groups': True, 'groups': ['cstm-users', 'hadoop'], 'uid': None}
2018-09-26 04:3
[jira] [Commented] (AMBARI-23933) YARN service check failure with no permission to submit jobs for ambari-qa user
[
https://issues.apache.org/jira/browse/AMBARI-23933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621841#comment-16621841
]
Srikanth Janardhan commented on AMBARI-23933:
-
Hi [~Dharaneesh], the root cause of this issue was that
hadoop.security.instrumentation.requires.admin was set to true. Please set it
to false if you're setting this property to true.
> YARN service check failure with no permission to submit jobs for ambari-qa
> user
> ---
>
> Key: AMBARI-23933
> URL: https://issues.apache.org/jira/browse/AMBARI-23933
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.7.0
>
>
> Service check for YARN failed:
> {code}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service_check.py",
> line 185, in
> ServiceCheck().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service_check.py",
> line 121, in service_check
> user=params.smokeuser,
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 308, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
> ambari...@example.com; yarn
> org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls
> -num_containers 1 -jar
> /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar
> -timeout 30 --queue default' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> 18/05/18 11:33:09 INFO distributedshell.Client: Initializing Client
> 18/05/18 11:33:09 INFO distributedshell.Client: Running Client
> 18/05/18 11:33:09 INFO client.AHSProxy: Connecting to Application History
> server at ctr-e138-1518143905142-317995-01-04.hwx.site/172.27.56.82:10200
> 18/05/18 11:33:09 INFO client.ConfiguredRMFailoverProxyProvider: Failing over
> to rm2
> 18/05/18 11:33:10 INFO distributedshell.Client: Got Cluster metric info from
> ASM, numNodeManagers=3
> 18/05/18 11:33:10 INFO distributedshell.Client: Got Cluster node info from ASM
> 18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=ctr-e138-1518143905142-317995-01-09.hwx.site:25454,
> nodeAddress=ctr-e138-1518143905142-317995-01-09.hwx.site:8042,
> nodeRackName=/default-rack, nodeNumContainers=1
> 18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=ctr-e138-1518143905142-317995-01-06.hwx.site:25454,
> nodeAddress=ctr-e138-1518143905142-317995-01-06.hwx.site:8042,
> nodeRackName=/default-rack, nodeNumContainers=0
> 18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=ctr-e138-1518143905142-317995-01-07.hwx.site:25454,
> nodeAddress=ctr-e138-1518143905142-317995-01-07.hwx.site:8042,
> nodeRackName=/default-rack, nodeNumContainers=0
> 18/05/18 11:33:10 INFO distributedshell.Client: Queue info,
> queueName=default, queueCurrentCapacity=0.02778, queueMaxCapacity=1.0,
> queueApplicationCount=0, queueChildQueueCount=0
> 18/05/18 11:33:10 INFO distributedshell.Client: Max mem capability of
> resources in this cluster 12288
> 18/05/18 11:33:10 INFO distributedshell.Client: Max virtual cores capability
> of resources in this cluster 1
> 18/05/18 11:33:10 WARN distributedshell.Client: AM Memory not specified, use
> 100 mb as AM memory
> 18/05/18 11:33:10 WARN distributedshell.Client: AM vcore not specified, use 1
> mb as AM vcores
> 18/05/18 11:33:10 WARN distributedshell.Client: AM Resource capability=
> 18/05/18 11:33:10 INFO distributedshell.Client: Copy App Master jar from
> local filesystem and add to local environment
> 18/05/18 11:33:11 INFO distributedshell.Client: Set the environment for the
> application master
> 18/05/18 11:33:11 INFO distributeds
[jira] [Created] (AMBARI-24603) Hard to scroll components list in Host details -> Logs page when there are > 15 components in host
Srikanth Janardhan created AMBARI-24603: --- Summary: Hard to scroll components list in Host details -> Logs page when there are > 15 components in host Key: AMBARI-24603 URL: https://issues.apache.org/jira/browse/AMBARI-24603 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.1 Reporter: Srikanth Janardhan Assignee: Srikanth Janardhan Fix For: 2.7.2 Attachments: Screen Shot 2018-09-06 at 11.26.05 PM.png When there are lot of components installed in a host, it is hard to scroll list of all components in Host Details -> Logs Page. Fix: to add a scroller. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24572) Cluster name is not aligned with background ops
[ https://issues.apache.org/jira/browse/AMBARI-24572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan updated AMBARI-24572: Attachment: Screen Shot 2018-09-06 at 10.49.00 PM.png > Cluster name is not aligned with background ops > > > Key: AMBARI-24572 > URL: https://issues.apache.org/jira/browse/AMBARI-24572 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Fix For: 2.7.2 > > Attachments: Screen Shot 2018-09-06 at 10.49.00 PM.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24572) Cluster name is not aligned with background ops
[ https://issues.apache.org/jira/browse/AMBARI-24572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan updated AMBARI-24572: Description: When the cluster name is long, the cluster name overflows to the next line, even though there is a lot of gap to accomodate the cluster name. > Cluster name is not aligned with background ops > > > Key: AMBARI-24572 > URL: https://issues.apache.org/jira/browse/AMBARI-24572 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Fix For: 2.7.2 > > Attachments: Screen Shot 2018-09-06 at 10.49.00 PM.png > > > When the cluster name is long, the cluster name overflows to the next line, > even though there is a lot of gap to accomodate the cluster name. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24572) Cluster name is not aligned with background ops
Srikanth Janardhan created AMBARI-24572: --- Summary: Cluster name is not aligned with background ops Key: AMBARI-24572 URL: https://issues.apache.org/jira/browse/AMBARI-24572 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.1 Reporter: Srikanth Janardhan Assignee: Srikanth Janardhan Fix For: 2.7.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24455) Spark service check failure after UI Deploy - non Secure with Ranger/KMS
Srikanth Janardhan created AMBARI-24455:
---
Summary: Spark service check failure after UI Deploy - non Secure
with Ranger/KMS
Key: AMBARI-24455
URL: https://issues.apache.org/jira/browse/AMBARI-24455
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.1
Reporter: Srikanth Janardhan
Fix For: 2.7.1
Spark Service check fails while UI Deploy:
{code}
stderr:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/service_check.py",
line 78, in service_check
Execute(cmd, user=params.smoke_user, path=[beeline_cmd],
timeout=CHECK_COMMAND_TIMEOUT_DEFAULT)
File "/usr/lib/ambari-agent/lib/resource_management/core/base.py", line 166,
in __init__
self.env.run()
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File "/usr/lib/ambari-agent/lib/resource_management/core/environment.py",
line 124, in run_action
provider_action()
File
"/usr/lib/ambari-agent/lib/resource_management/core/providers/system.py", line
263, in action_run
returns=self.resource.returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72,
in inner
result = function(command, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102,
in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy, returns=returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150,
in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 314,
in _call
raise ExecutionFailed(err_msg, code, out, err)
ExecutionFailed: Execution of '! /usr/hdp/current/spark2-client/bin/beeline -u
'jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default'
transportMode=binary -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused'
-e 'Invalid URL' -e 'Error: Could not open'' returned 1. Hortonworks
#
This is MOTD message, added for testing in qe infra
Error: Could not open client transport with JDBC Uri:
jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default:
java.net.ConnectException: Connection refused (Connection refused)
(state=08S01,code=0)
Error: Could not open client transport with JDBC Uri:
jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default:
java.net.ConnectException: Connection refused (Connection refused)
(state=08S01,code=0)
The above exception was the cause of the following exception:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/service_check.py",
line 88, in
SparkServiceCheck().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/SPARK2/package/scripts/service_check.py",
line 85, in service_check
raise Fail("Connection to all Spark thrift servers servers failed")
resource_management.core.exceptions.Fail: Connection to all Spark thrift
servers servers failed
stdout:
2018-08-10 05:22:29,576 - Using hadoop conf dir: /usr/hdp/3.0.1.0-73/hadoop/conf
2018-08-10 05:22:29,600 - Execute['curl -s -o /dev/null -w'%{http_code}'
--negotiate -u: -k
http://ctr-e138-1518143905142-432870-01-04.hwx.site:18081 | grep 200']
{'logoutput': True, 'tries': 5, 'user': 'ambari-qa', 'try_sleep': 3}
Hortonworks #
This is MOTD message, added for testing in qe infra
200
2018-08-10 05:22:29,794 - Execute['curl -s -o /dev/null -w'%{http_code}'
--negotiate -u: -k
http://ctr-e138-1518143905142-432870-01-04.hwx.site:8999/sessions | grep
200'] {'logoutput': True, 'tries': 3, 'user': 'ambari-qa', 'try_sleep': 1}
Hortonworks #
This is MOTD message, added for testing in qe infra
200
2018-08-10 05:22:29,843 - Execute['! /usr/hdp/current/spark2-client/bin/beeline
-u
'jdbc:hive2://ctr-e138-1518143905142-432870-01-04.hwx.site:10016/default'
transportMode=binary -e '' 2>&1| awk '{print}'|grep -i -e 'Connection refused'
-e 'Invalid URL' -e 'Error: Could not open''] {'path':
[u'/usr/hdp/current/spark2-client/bin/beeline'], 'user': 'ambari-qa',
'timeout': 60.0}
Command failed after 1 tries
{code}
I checked the schedule of commands and observed that Spark Thrift server start
is scheduled to run after Spark2 service check is executed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23409) Overflowing list of frozen hosts in Assign Slaves and Clients page
[ https://issues.apache.org/jira/browse/AMBARI-23409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan resolved AMBARI-23409. - Resolution: Done Assignee: Ishan Bhatt Fix Version/s: (was: 2.7.1) 2.7.0 > Overflowing list of frozen hosts in Assign Slaves and Clients page > -- > > Key: AMBARI-23409 > URL: https://issues.apache.org/jira/browse/AMBARI-23409 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Srikanth Janardhan >Assignee: Ishan Bhatt >Priority: Blocker > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-30 at 9.06.19 AM.png, Screen Shot > 2018-03-30 at 9.14.33 AM.png > > > When more than 10 hosts are present in a deployed cluster, the frozen hosts > column in assign slaves and clients page overflows the boundary and is not > scrollable. > Version: ambari-server-2.7.0.0-217 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23812) Ambari Metrics Collector going down in centos7
[ https://issues.apache.org/jira/browse/AMBARI-23812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan resolved AMBARI-23812. - Resolution: Done > Ambari Metrics Collector going down in centos7 > -- > > Key: AMBARI-23812 > URL: https://issues.apache.org/jira/browse/AMBARI-23812 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: 2.7.0 >Reporter: Srikanth Janardhan >Priority: Blocker > Fix For: 2.7.1 > > Attachments: metric_collector.zip > > > In ambari-2.7.0.0-477 and HDP-3.0.0.0-1315, ambari metrics goes down after > starting. I triggered a config change and restarted all services, post which > ambari metrics collector is down. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23902) YARN service check failure with no permission to submit jobs for ambari-qa user
[
https://issues.apache.org/jira/browse/AMBARI-23902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-23902.
-
Resolution: Done
> YARN service check failure with no permission to submit jobs for ambari-qa
> user
> ---
>
> Key: AMBARI-23902
> URL: https://issues.apache.org/jira/browse/AMBARI-23902
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.7.1
>
>
> Service check for YARN failed:
> {code}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service_check.py",
> line 185, in
> ServiceCheck().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service_check.py",
> line 121, in service_check
> user=params.smokeuser,
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 308, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
> ambari...@example.com; yarn
> org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls
> -num_containers 1 -jar
> /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar
> -timeout 30 --queue default' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> 18/05/18 11:33:09 INFO distributedshell.Client: Initializing Client
> 18/05/18 11:33:09 INFO distributedshell.Client: Running Client
> 18/05/18 11:33:09 INFO client.AHSProxy: Connecting to Application History
> server at ctr-e138-1518143905142-317995-01-04.hwx.site/172.27.56.82:10200
> 18/05/18 11:33:09 INFO client.ConfiguredRMFailoverProxyProvider: Failing over
> to rm2
> 18/05/18 11:33:10 INFO distributedshell.Client: Got Cluster metric info from
> ASM, numNodeManagers=3
> 18/05/18 11:33:10 INFO distributedshell.Client: Got Cluster node info from ASM
> 18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=ctr-e138-1518143905142-317995-01-09.hwx.site:25454,
> nodeAddress=ctr-e138-1518143905142-317995-01-09.hwx.site:8042,
> nodeRackName=/default-rack, nodeNumContainers=1
> 18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=ctr-e138-1518143905142-317995-01-06.hwx.site:25454,
> nodeAddress=ctr-e138-1518143905142-317995-01-06.hwx.site:8042,
> nodeRackName=/default-rack, nodeNumContainers=0
> 18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=ctr-e138-1518143905142-317995-01-07.hwx.site:25454,
> nodeAddress=ctr-e138-1518143905142-317995-01-07.hwx.site:8042,
> nodeRackName=/default-rack, nodeNumContainers=0
> 18/05/18 11:33:10 INFO distributedshell.Client: Queue info,
> queueName=default, queueCurrentCapacity=0.02778, queueMaxCapacity=1.0,
> queueApplicationCount=0, queueChildQueueCount=0
> 18/05/18 11:33:10 INFO distributedshell.Client: Max mem capability of
> resources in this cluster 12288
> 18/05/18 11:33:10 INFO distributedshell.Client: Max virtual cores capability
> of resources in this cluster 1
> 18/05/18 11:33:10 WARN distributedshell.Client: AM Memory not specified, use
> 100 mb as AM memory
> 18/05/18 11:33:10 WARN distributedshell.Client: AM vcore not specified, use 1
> mb as AM vcores
> 18/05/18 11:33:10 WARN distributedshell.Client: AM Resource capability=
> 18/05/18 11:33:10 INFO distributedshell.Client: Copy App Master jar from
> local filesystem and add to local environment
> 18/05/18 11:33:11 INFO distributedshell.Client: Set the environment for the
> application master
> 18/05/18 11:33:11 INFO distributedshell.Client: Setting up app master command
> 18/05/18 11:33:11 INFO distributedshell.Client: Completed setting up app
> master command {{JAVA_HOME}}/bin/java -Xmx100m
> org.apache.hadoop.yarn.applications.distributedshe
[jira] [Resolved] (AMBARI-23934) Next button not enabled in Enable Namenode HA Wizard
[
https://issues.apache.org/jira/browse/AMBARI-23934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-23934.
-
Resolution: Done
> Next button not enabled in Enable Namenode HA Wizard
>
>
> Key: AMBARI-23934
> URL: https://issues.apache.org/jira/browse/AMBARI-23934
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Myroslav Papirkovskyi
>Priority: Blocker
> Fix For: 2.7.1
>
>
> Next Button in Create Checkpoint page is not enabled while enabling Namenode
> HA.
> !Screen Shot 2018-05-18 at 10.48.50 PM.png|thumbnail!
> Commands executed:
> {code:bash}
> sjanardhan@HW15613 ~/Developer/backup/qe-ambariautomation # ssh -i
> ~/Documents/ok.txt r...@ctr-e138-1518143905142-318323-01-03.hwx.site
>
> The authenticity of host 'ctr-e138-1518143905142-318323-01-03.hwx.site
> (172.27.65.207)' can't be established.
> ECDSA key fingerprint is SHA256:gkYtB2sQzz5MPaeVeyHHMuvDK4h9ebp6b5krS3IP8eI.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added
> 'ctr-e138-1518143905142-318323-01-03.hwx.site,172.27.65.207' (ECDSA) to
> the list of known hosts.
> Last login: Fri May 18 01:56:54 2018
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> [root@ctr-e138-1518143905142-318323-01-03 ~]# sudo su cstm-hdfs -l -c
> 'hdfs dfsadmin -safemode enter'
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> Safe mode is ON
> [root@ctr-e138-1518143905142-318323-01-03 ~]# sudo su cstm-hdfs -l -c
> 'hdfs dfsadmin -saveNamespace'
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> Save namespace successful
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24267) Ambari Alerts are not triggered
Srikanth Janardhan created AMBARI-24267: --- Summary: Ambari Alerts are not triggered Key: AMBARI-24267 URL: https://issues.apache.org/jira/browse/AMBARI-24267 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Srikanth Janardhan Fix For: 2.7.0 Even when Namenodes, Datanodes/ entire services are down, there are no alerts in the Ambari UI. Most of the summary information in HDFS, YARN show as n/a. There are no errors in the JS console too. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24250) Create Checkpoint page stuck while Enabling HA on Namenode
Srikanth Janardhan created AMBARI-24250:
---
Summary: Create Checkpoint page stuck while Enabling HA on Namenode
Key: AMBARI-24250
URL: https://issues.apache.org/jira/browse/AMBARI-24250
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Robert Levas
Fix For: 2.7.0
Ambari UI stuck at Manual Steps Required: Create Checkpoint on NameNode page
while Enabling HA after performing the manual steps.
{code}
[root@ctr-e138-1518143905142-378399-01-04 ~]# sudo su cstm-hdfs -l -c 'hdfs
dfsadmin -safemode enter'
Hortonworks #
This is MOTD message, added for testing in qe infra
Safe mode is ON
[root@ctr-e138-1518143905142-378399-01-04 ~]# sudo su cstm-hdfs -l -c 'hdfs
dfsadmin -saveNamespace'
Hortonworks #
This is MOTD message, added for testing in qe infra
Save namespace successful
{code}
The stat result of file /etc/security/keytabs/ambari.server.keytab, looks like
the final change in the file occured at 2018-07-04 05:53:52.
{code:java}
[root@ctr-e138-1518143905142-395357-01-02 ~]# stat
/etc/security/keytabs/ambari.server.keytab
File: ‘/etc/security/keytabs/ambari.server.keytab’
Size: 333 Blocks: 8 IO Block: 4096 regular file
Device: fd12h/64786dInode: 16390172Links: 1
Access: (0400/-r) Uid: ( 1803/agentslava) Gid: ( 1803/agentslava)
Access: 2018-07-04 03:01:39.282093801 +
Modify: 2018-07-04 03:01:39.282093801 +
Change: 2018-07-04 05:53:52.333709142 +
Birth: -
{code}
>From the ambari server logs at the same time stamp:
{code:java}
2018-07-04 05:53:52,054 INFO [Server Action Executor Worker 586]
KerberosServerAction:411 - Processing identities...
2018-07-04 05:53:52,322 INFO [Server Action Executor Worker 586]
FinalizeKerberosServerAction:111 - Updated the owner of the keytab file at
/etc/security/keytabs/ambari.server.keytab to null
2018-07-04 05:53:52,323 INFO [Server Action Executor Worker 586]
FinalizeKerberosServerAction:125 - Updated the group of the keytab file at
/etc/security/keytabs/ambari.server.keytab to null
2018-07-04 05:53:52,337 INFO [Server Action Executor Worker 586]
FinalizeKerberosServerAction:142 - Updated the access mode of the keytab file
at /etc/security/keytabs/ambari.server.keytab to owner:'r' and group:'null'
2018-07-04 05:53:52,352 INFO [Server Action Executor Worker 586]
FinalizeKerberosServerAction:111 - Updated the owner of the keytab file at
/etc/security/keytabs/ams-monitor.keytab to cstm-ams
2018-07-04 05:53:52,371 INFO [Server Action Executor Worker 586]
FinalizeKerberosServerAction:125 - Updated the group of the keytab file at
/etc/security/keytabs/ams-monitor.keytab to hadoop
2018-07-04 05:53:52,387 INFO [Server Action Executor Worker 586]
FinalizeKerberosServerAction:142 - Updated the access mode of the keytab file
at /etc/security/keytabs/ams-monitor.keytab to owner:'r' and group:''
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24188) The button 'NEXT ->' should contain a special html tag 'data-qa'
[ https://issues.apache.org/jira/browse/AMBARI-24188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan resolved AMBARI-24188. - Resolution: Fixed > The button 'NEXT ->' should contain a special html tag 'data-qa' > > > Key: AMBARI-24188 > URL: https://issues.apache.org/jira/browse/AMBARI-24188 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > > To add data-qa attribute for kerberos wizards -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24188) The button 'NEXT ->' should contain a special html tag 'data-qa'
Srikanth Janardhan created AMBARI-24188: --- Summary: The button 'NEXT ->' should contain a special html tag 'data-qa' Key: AMBARI-24188 URL: https://issues.apache.org/jira/browse/AMBARI-24188 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Srikanth Janardhan Assignee: Srikanth Janardhan Fix For: 2.7.0 To add data-qa attribute for kerberos wizards -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24179) Ambari Metrics Service check fails after deleting a host
Srikanth Janardhan created AMBARI-24179:
---
Summary: Ambari Metrics Service check fails after deleting a host
Key: AMBARI-24179
URL: https://issues.apache.org/jira/browse/AMBARI-24179
Project: Ambari
Issue Type: Bug
Components: ambari-metrics
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Dmytro Sen
Fix For: 2.7.0
ambari metrics service check failed immediately after deleting a host:
{code:java}
stderr:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/service_check.py",
line 304, in
AMSServiceCheck().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/service_check.py",
line 184, in service_check
raise Fail("All metrics collectors are unavailable.")
resource_management.core.exceptions.Fail: All metrics collectors are
unavailable.
stdout:
2018-06-25 04:42:25,088 - Using hadoop conf dir:
/usr/hdp/3.0.0.0-1541/hadoop/conf
2018-06-25 04:42:25,095 - checked_call['hostid'] {}
2018-06-25 04:42:25,100 - checked_call returned (0, '1bac1213')
2018-06-25 04:42:25,102 - Ambari Metrics service check was started.
2018-06-25 04:42:25,121 - Generated metrics for host
ctr-e138-1518143905142-378410-01-09.hwx.site :
{
"metrics": [
{
"metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
"appid": "amssmoketestfake",
"hostname": "ctr-e138-1518143905142-378410-01-12.hwx.site",
"starttime": 1529901745000,
"metrics": {
"1529901745000": 0.602995821312,
"1529901746000": 1529901745000
}
}
]
}
2018-06-25 04:42:25,122 - Connecting (POST) to
ctr-e138-1518143905142-378410-01-09.hwx.site:6188/ws/v1/timeline/metrics/
2018-06-25 04:42:25,132 - Http response for host
ctr-e138-1518143905142-378410-01-09.hwx.site: 200 OK
2018-06-25 04:42:25,133 - Http data:
2018-06-25 04:42:25,133 - Metrics were saved.
2018-06-25 04:42:25,133 - Connecting (GET) to
ctr-e138-1518143905142-378410-01-09.hwx.site:6188/ws/v1/timeline/metrics?metricNames=AMBARI_METRICS.SmokeTest.FakeMetric&hostname=ctr-e138-1518143905142-378410-01-12.hwx.site&precision=seconds&grouped=false&startTime=1529901685000&appId=amssmoketestfake&endTime=1529901806000
2018-06-25 04:42:25,138 - Http response for host
ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
2018-06-25 04:42:25,138 - Http data: {"metrics":[]}
2018-06-25 04:42:25,138 - Metrics were retrieved from host
ctr-e138-1518143905142-378410-01-09.hwx.site
2018-06-25 04:42:25,139 - Values weren't stored yet. Retrying in 10 seconds.
2018-06-25 04:42:35,154 - Http response for host
ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
2018-06-25 04:42:35,154 - Http data: {"metrics":[]}
2018-06-25 04:42:35,154 - Metrics were retrieved from host
ctr-e138-1518143905142-378410-01-09.hwx.site
2018-06-25 04:42:35,155 - Values weren't stored yet. Retrying in 10 seconds.
2018-06-25 04:42:45,170 - Http response for host
ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
2018-06-25 04:42:45,170 - Http data: {"metrics":[]}
2018-06-25 04:42:45,171 - Metrics were retrieved from host
ctr-e138-1518143905142-378410-01-09.hwx.site
2018-06-25 04:42:45,171 - Values weren't stored yet. Retrying in 10 seconds.
2018-06-25 04:42:55,186 - Http response for host
ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
2018-06-25 04:42:55,186 - Http data: {"metrics":[]}
2018-06-25 04:42:55,187 - Metrics were retrieved from host
ctr-e138-1518143905142-378410-01-09.hwx.site
2018-06-25 04:42:55,187 - Values weren't stored yet. Retrying in 10 seconds.
2018-06-25 04:43:05,204 - Http response for host
ctr-e138-1518143905142-378410-01-09.hwx.site : 200 OK
2018-06-25 04:43:05,204 - Http data: {"metrics":[]}
2018-06-25 04:43:05,205 - Metrics were retrieved from host
ctr-e138-1518143905142-378410-01-09.hwx.site
2018-06-25 04:43:05,205 - Ambari Metrics service check failed on collector host
ctr-e138-1518143905142-378410-01-09.hwx.site. Reason : Values
0.602995821312 and 1529901745000 were not found in the response.
2018-06-25 04:43:05,207 - Exception while running function '>' for
'ctr-e138-1518143905142-378410-01-09.hwx.site'. Reason : Ambari Metrics
service check failed on collector host
ctr-e138-1518143905142-378410-01-09.hwx.site. Reason : Values
0.602995821312 and 1529901745000 were not found in the response.
Command failed after 1 tries
{code}
*Subsequent service check passed, though.*
The issue looks not related to the host deletion, seems like
[jira] [Created] (AMBARI-24176) Deleting a service fails to remove keytabs
Srikanth Janardhan created AMBARI-24176:
---
Summary: Deleting a service fails to remove keytabs
Key: AMBARI-24176
URL: https://issues.apache.org/jira/browse/AMBARI-24176
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Attila Magyar
Fix For: 2.7.0
while deleting Atlas service, faced this issue:
{code}
stderr:
Caught an exception while executing custom service command: : Command requires
configs with timestamp=1529647351404 but configs on agent have
timestamp=1529647350969; Command requires configs with timestamp=1529647351404
but configs on agent have timestamp=1529647350969
stdout:
Caught an exception while executing custom service command: : Command requires
configs with timestamp=1529647351404 but configs on agent have
timestamp=1529647350969; Command requires configs with timestamp=1529647351404
but configs on agent have timestamp=1529647350969
Command failed after 1 tries
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24122) In collapsed navigation view, the list of services is not scrollable
Srikanth Janardhan created AMBARI-24122: --- Summary: In collapsed navigation view, the list of services is not scrollable Key: AMBARI-24122 URL: https://issues.apache.org/jira/browse/AMBARI-24122 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Srikanth Janardhan Assignee: Srikanth Janardhan Fix For: 2.7.0 Attachments: scroll-collapsed-navigation-issues.mov With the new UI navigation, when a large number of services is installed, the list of services shown is not scrollable in collapsed navigation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24121) Duration for a failed BG Operation is incorrect
[
https://issues.apache.org/jira/browse/AMBARI-24121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-24121:
Description:
There are several failed install components and they report the incorrect
duration.
Example: Install Nodemanager failed and was executed only for a few seconds,
whereas in the Duration column, it shows 16 hours.
!Screen Shot 2018-06-15 at 12.12.38 PM.png!
Primarily because the output from the server has the end time as -1:
{noformat}
{
"itemTotal" : "10",
"items" : [
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 31,
"progress_percent" : 100.0,
"request_context" : "Install NFSGateway",
"request_status" : "FAILED",
"start_time" : 1528983750924,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 32,
"progress_percent" : 100.0,
"request_context" : "Install NodeManager",
"request_status" : "FAILED",
"start_time" : 1528983763421,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 33,
"progress_percent" : 100.0,
"request_context" : "Install YARN Client",
"request_status" : "FAILED",
"start_time" : 1528983776062,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : 1528985439608,
"id" : 34,
"progress_percent" : 100.0,
"request_context" : "Reinstall Failed Components",
"request_status" : "COMPLETED",
"start_time" : 1528985380177,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : 1528985625102,
"id" : 35,
"progress_percent" : 100.0,
"request_context" : "Reinstall Failed Components",
"request_status" : "COMPLETED",
"start_time" : 1528985594981,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : 1528986079631,
"id" : 36,
"progress_percent" : 100.0,
"request_context" : "put services into STARTED",
"request_status" : "COMPLETED",
"start_time" : 1528986013070,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : 1529043756536,
"id" : 37,
"progress_percent" : 100.0,
"request_context" : "Start Knox Gateway",
"request_status" : "FAILED",
"start_time" : 1529043756451,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 38,
"progress_percent" : 100.0,
"request_context" : "Install MapReduce2 Client",
"request_status" : "FAILED",
"start_time" : 1529044241508,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 39,
"progress_percent" : 100.0,
"request_context" : "Install Hive Client",
"request_status" : "FAILED",
"start_time" : 1529044679827,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 40,
"progress_percent" : 100.0,
"request_context" : "Install Metrics Collector",
"request_status" : "FAILED",
"start_time" : 1529045027390,
"user_name" : "admin"
}
}
]
}
{noformat}
was:
There are several failed install components and they report the incorrect
duration.
Example: Install Nodemanager failed and was executed only for a few seconds,
whereas in the Duration column, it shows 16 hours.
!Screen Shot 2018-06-15 at 12.12.38 PM.png!
Primarily because the output from the server is as follows:
{noformat}
{
"itemTotal" : "10",
"items" : [
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 31,
"progress_percent" : 100.0,
"request_context" : "Install NFSGateway",
"request_status" : "FAILED",
"start_time" : 1528983750924,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 32,
"progress_percent" : 100.0,
"request_context" : "Install NodeManager",
"request_status" : "FAILED",
"start_time" : 1528983763421,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 33,
"progress_percent" : 100.0,
"request_context" : "Install YARN Client",
[jira] [Created] (AMBARI-24121) Duration for a failed BG Operation is incorrect
Srikanth Janardhan created AMBARI-24121:
---
Summary: Duration for a failed BG Operation is incorrect
Key: AMBARI-24121
URL: https://issues.apache.org/jira/browse/AMBARI-24121
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Robert Levas
Fix For: 2.7.0
Attachments: Screen Shot 2018-06-15 at 12.12.38 PM.png
There are several failed install components and they report the incorrect
duration.
Example: Install Nodemanager failed and was executed only for a few seconds,
whereas in the Duration column, it shows 16 hours.
!Screen Shot 2018-06-15 at 12.12.38 PM.png!
Primarily because the output from the server is as follows:
{noformat}
{
"itemTotal" : "10",
"items" : [
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 31,
"progress_percent" : 100.0,
"request_context" : "Install NFSGateway",
"request_status" : "FAILED",
"start_time" : 1528983750924,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 32,
"progress_percent" : 100.0,
"request_context" : "Install NodeManager",
"request_status" : "FAILED",
"start_time" : 1528983763421,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 33,
"progress_percent" : 100.0,
"request_context" : "Install YARN Client",
"request_status" : "FAILED",
"start_time" : 1528983776062,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : 1528985439608,
"id" : 34,
"progress_percent" : 100.0,
"request_context" : "Reinstall Failed Components",
"request_status" : "COMPLETED",
"start_time" : 1528985380177,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : 1528985625102,
"id" : 35,
"progress_percent" : 100.0,
"request_context" : "Reinstall Failed Components",
"request_status" : "COMPLETED",
"start_time" : 1528985594981,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : 1528986079631,
"id" : 36,
"progress_percent" : 100.0,
"request_context" : "put services into STARTED",
"request_status" : "COMPLETED",
"start_time" : 1528986013070,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : 1529043756536,
"id" : 37,
"progress_percent" : 100.0,
"request_context" : "Start Knox Gateway",
"request_status" : "FAILED",
"start_time" : 1529043756451,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 38,
"progress_percent" : 100.0,
"request_context" : "Install MapReduce2 Client",
"request_status" : "FAILED",
"start_time" : 1529044241508,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 39,
"progress_percent" : 100.0,
"request_context" : "Install Hive Client",
"request_status" : "FAILED",
"start_time" : 1529044679827,
"user_name" : "admin"
}
},
{
"Requests" : {
"cluster_name" : "cl1",
"end_time" : -1,
"id" : 40,
"progress_percent" : 100.0,
"request_context" : "Install Metrics Collector",
"request_status" : "FAILED",
"start_time" : 1529045027390,
"user_name" : "admin"
}
}
]
}
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24070) SSL Connection logs missing as a side effect of AMBARI-23222
[ https://issues.apache.org/jira/browse/AMBARI-24070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan resolved AMBARI-24070. - Resolution: Fixed > SSL Connection logs missing as a side effect of AMBARI-23222 > > > Key: AMBARI-24070 > URL: https://issues.apache.org/jira/browse/AMBARI-24070 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.7.0 >Reporter: Srikanth Janardhan >Assignee: Srikanth Janardhan >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > Logging missed due to > https://github.com/apache/ambari/commit/54ba89133f61b8ad013d96f4f8d881844229abd9#diff-639c7b5dc2005f486841e0317a228e9aL63 > https://github.com/apache/ambari/commit/54ba89133f61b8ad013d96f4f8d881844229abd9#diff-639c7b5dc2005f486841e0317a228e9aL80 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24070) SSL Connection logs missing as a side effect of AMBARI-23222
Srikanth Janardhan created AMBARI-24070: --- Summary: SSL Connection logs missing as a side effect of AMBARI-23222 Key: AMBARI-24070 URL: https://issues.apache.org/jira/browse/AMBARI-24070 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.7.0 Reporter: Srikanth Janardhan Assignee: Srikanth Janardhan Fix For: 2.7.0 Logging missed due to https://github.com/apache/ambari/commit/54ba89133f61b8ad013d96f4f8d881844229abd9#diff-639c7b5dc2005f486841e0317a228e9aL63 https://github.com/apache/ambari/commit/54ba89133f61b8ad013d96f4f8d881844229abd9#diff-639c7b5dc2005f486841e0317a228e9aL80 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24057) Deploy button doesn't show in Review Page of Move Master Wizard
Srikanth Janardhan created AMBARI-24057:
---
Summary: Deploy button doesn't show in Review Page of Move Master
Wizard
Key: AMBARI-24057
URL: https://issues.apache.org/jira/browse/AMBARI-24057
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Fix For: 2.7.0
Attachments: Screen Shot 2018-06-08 at 2.42.37 PM.png
With ambari-2.7.0.0-657, noticed in the Review Page of Move Master Wizard for
Hive Metastore is stuck and doesn't enable the Deploy button to proceed further.
Steps:
# Add Hive Metastore to a host
# Select Move action in the Host Details page for Hive Metastore
# Navigate the wizard till the Review Page
Screenshot: !Screen Shot 2018-06-08 at 2.42.37 PM.png!
Javascript errors:
{code}
app.js:31203 Uncaught TypeError: Cannot read property 'tag' of undefined
at app.js:31203
at Array.forEach ()
at Class.getConfigUrlParams (app.js:31202)
at Class.onLoadConfigsTags (app.js:31187)
at Class.opt.success (app.js:183168)
at fire (vendor.js:1141)
at Object.fireWith [as resolveWith] (vendor.js:1252)
at done (vendor.js:8178)
at XMLHttpRequest.callback (vendor.js:8702)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23933) YARN service check failure with no permission to submit jobs for ambari-qa user
[
https://issues.apache.org/jira/browse/AMBARI-23933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-23933.
-
Resolution: Fixed
> YARN service check failure with no permission to submit jobs for ambari-qa
> user
> ---
>
> Key: AMBARI-23933
> URL: https://issues.apache.org/jira/browse/AMBARI-23933
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Dmitry Lysnichenko
>Priority: Blocker
> Fix For: 2.7.0
>
>
> Service check for YARN failed:
> {code}
> stderr:
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service_check.py",
> line 185, in
> ServiceCheck().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service_check.py",
> line 121, in service_check
> user=params.smokeuser,
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy, returns=returns)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line
> 308, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
> ambari...@example.com; yarn
> org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls
> -num_containers 1 -jar
> /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar
> -timeout 30 --queue default' returned 1. Hortonworks
> #
> This is MOTD message, added for testing in qe infra
> 18/05/18 11:33:09 INFO distributedshell.Client: Initializing Client
> 18/05/18 11:33:09 INFO distributedshell.Client: Running Client
> 18/05/18 11:33:09 INFO client.AHSProxy: Connecting to Application History
> server at ctr-e138-1518143905142-317995-01-04.hwx.site/172.27.56.82:10200
> 18/05/18 11:33:09 INFO client.ConfiguredRMFailoverProxyProvider: Failing over
> to rm2
> 18/05/18 11:33:10 INFO distributedshell.Client: Got Cluster metric info from
> ASM, numNodeManagers=3
> 18/05/18 11:33:10 INFO distributedshell.Client: Got Cluster node info from ASM
> 18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=ctr-e138-1518143905142-317995-01-09.hwx.site:25454,
> nodeAddress=ctr-e138-1518143905142-317995-01-09.hwx.site:8042,
> nodeRackName=/default-rack, nodeNumContainers=1
> 18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=ctr-e138-1518143905142-317995-01-06.hwx.site:25454,
> nodeAddress=ctr-e138-1518143905142-317995-01-06.hwx.site:8042,
> nodeRackName=/default-rack, nodeNumContainers=0
> 18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=ctr-e138-1518143905142-317995-01-07.hwx.site:25454,
> nodeAddress=ctr-e138-1518143905142-317995-01-07.hwx.site:8042,
> nodeRackName=/default-rack, nodeNumContainers=0
> 18/05/18 11:33:10 INFO distributedshell.Client: Queue info,
> queueName=default, queueCurrentCapacity=0.02778, queueMaxCapacity=1.0,
> queueApplicationCount=0, queueChildQueueCount=0
> 18/05/18 11:33:10 INFO distributedshell.Client: Max mem capability of
> resources in this cluster 12288
> 18/05/18 11:33:10 INFO distributedshell.Client: Max virtual cores capability
> of resources in this cluster 1
> 18/05/18 11:33:10 WARN distributedshell.Client: AM Memory not specified, use
> 100 mb as AM memory
> 18/05/18 11:33:10 WARN distributedshell.Client: AM vcore not specified, use 1
> mb as AM vcores
> 18/05/18 11:33:10 WARN distributedshell.Client: AM Resource capability=
> 18/05/18 11:33:10 INFO distributedshell.Client: Copy App Master jar from
> local filesystem and add to local environment
> 18/05/18 11:33:11 INFO distributedshell.Client: Set the environment for the
> application master
> 18/05/18 11:33:11 INFO distributedshell.Client: Setting up app master command
> 18/05/18 11:33:11 INFO distributedshell.Client: Completed setting up app
> master command {{JAVA_HOME}}/bin/java -Xmx100m
> org.apache.hadoop.yarn.applications.distributedshe
[jira] [Created] (AMBARI-23934) Next button not enabled in Enable Namenode HA Wizard
Srikanth Janardhan created AMBARI-23934:
---
Summary: Next button not enabled in Enable Namenode HA Wizard
Key: AMBARI-23934
URL: https://issues.apache.org/jira/browse/AMBARI-23934
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Myroslav Papirkovskyi
Fix For: 2.7.0
Next Button in Create Checkpoint page is not enabled while enabling Namenode HA.
!Screen Shot 2018-05-18 at 10.48.50 PM.png|thumbnail!
Commands executed:
{code:bash}
sjanardhan@HW15613 ~/Developer/backup/qe-ambariautomation # ssh -i
~/Documents/ok.txt r...@ctr-e138-1518143905142-318323-01-03.hwx.site
The authenticity of host 'ctr-e138-1518143905142-318323-01-03.hwx.site
(172.27.65.207)' can't be established.
ECDSA key fingerprint is SHA256:gkYtB2sQzz5MPaeVeyHHMuvDK4h9ebp6b5krS3IP8eI.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added
'ctr-e138-1518143905142-318323-01-03.hwx.site,172.27.65.207' (ECDSA) to the
list of known hosts.
Last login: Fri May 18 01:56:54 2018
Hortonworks #
This is MOTD message, added for testing in qe infra
Hortonworks #
This is MOTD message, added for testing in qe infra
[root@ctr-e138-1518143905142-318323-01-03 ~]# sudo su cstm-hdfs -l -c 'hdfs
dfsadmin -safemode enter'
Hortonworks #
This is MOTD message, added for testing in qe infra
Safe mode is ON
[root@ctr-e138-1518143905142-318323-01-03 ~]# sudo su cstm-hdfs -l -c 'hdfs
dfsadmin -saveNamespace'
Hortonworks #
This is MOTD message, added for testing in qe infra
Save namespace successful
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23933) YARN service check failure with no permission to submit jobs for ambari-qa user
Srikanth Janardhan created AMBARI-23933:
---
Summary: YARN service check failure with no permission to submit
jobs for ambari-qa user
Key: AMBARI-23933
URL: https://issues.apache.org/jira/browse/AMBARI-23933
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Dmitry Lysnichenko
Fix For: 2.7.0
Service check for YARN failed:
{code}
stderr:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service_check.py",
line 185, in
ServiceCheck().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service_check.py",
line 121, in service_check
user=params.smokeuser,
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72,
in inner
result = function(command, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102,
in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy, returns=returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150,
in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 308,
in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of
'/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
ambari...@example.com; yarn
org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls
-num_containers 1 -jar
/usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar
-timeout 30 --queue default' returned 1. Hortonworks #
This is MOTD message, added for testing in qe infra
18/05/18 11:33:09 INFO distributedshell.Client: Initializing Client
18/05/18 11:33:09 INFO distributedshell.Client: Running Client
18/05/18 11:33:09 INFO client.AHSProxy: Connecting to Application History
server at ctr-e138-1518143905142-317995-01-04.hwx.site/172.27.56.82:10200
18/05/18 11:33:09 INFO client.ConfiguredRMFailoverProxyProvider: Failing over
to rm2
18/05/18 11:33:10 INFO distributedshell.Client: Got Cluster metric info from
ASM, numNodeManagers=3
18/05/18 11:33:10 INFO distributedshell.Client: Got Cluster node info from ASM
18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
nodeId=ctr-e138-1518143905142-317995-01-09.hwx.site:25454,
nodeAddress=ctr-e138-1518143905142-317995-01-09.hwx.site:8042,
nodeRackName=/default-rack, nodeNumContainers=1
18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
nodeId=ctr-e138-1518143905142-317995-01-06.hwx.site:25454,
nodeAddress=ctr-e138-1518143905142-317995-01-06.hwx.site:8042,
nodeRackName=/default-rack, nodeNumContainers=0
18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
nodeId=ctr-e138-1518143905142-317995-01-07.hwx.site:25454,
nodeAddress=ctr-e138-1518143905142-317995-01-07.hwx.site:8042,
nodeRackName=/default-rack, nodeNumContainers=0
18/05/18 11:33:10 INFO distributedshell.Client: Queue info, queueName=default,
queueCurrentCapacity=0.02778, queueMaxCapacity=1.0,
queueApplicationCount=0, queueChildQueueCount=0
18/05/18 11:33:10 INFO distributedshell.Client: Max mem capability of resources
in this cluster 12288
18/05/18 11:33:10 INFO distributedshell.Client: Max virtual cores capability of
resources in this cluster 1
18/05/18 11:33:10 WARN distributedshell.Client: AM Memory not specified, use
100 mb as AM memory
18/05/18 11:33:10 WARN distributedshell.Client: AM vcore not specified, use 1
mb as AM vcores
18/05/18 11:33:10 WARN distributedshell.Client: AM Resource capability=
18/05/18 11:33:10 INFO distributedshell.Client: Copy App Master jar from local
filesystem and add to local environment
18/05/18 11:33:11 INFO distributedshell.Client: Set the environment for the
application master
18/05/18 11:33:11 INFO distributedshell.Client: Setting up app master command
18/05/18 11:33:11 INFO distributedshell.Client: Completed setting up app master
command {{JAVA_HOME}}/bin/java -Xmx100m
org.apache.hadoop.yarn.applications.distributedshell.ApplicationMaster
--container_type GUARANTEED --container_memory 10 --container_vcores 1
--num_containers 1 --priority 0 1>/AppMaster.stdout 2>/AppMaster.stderr
18/05/18 11:33:11 INFO hdfs.DFSClient: Created token for ambari-qa:
HDFS_DELEGATION_TOKEN owner=ambari...@example.com, renewer=cstm-yarn,
realUser=, issueDate=1526643191972, maxDate=1527247991972, sequenceNumber=27,
masterKeyId=4 on ha-hdfs:myclus
[jira] [Resolved] (AMBARI-23928) Database script issue when running MYSQL DDL scripts
[
https://issues.apache.org/jira/browse/AMBARI-23928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-23928.
-
Resolution: Fixed
> Database script issue when running MYSQL DDL scripts
>
>
> Key: AMBARI-23928
> URL: https://issues.apache.org/jira/browse/AMBARI-23928
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When running Ambari-DDL-MySQL-CREATE.sql file on Mysql with Ubuntu16, getting
> the following error:
> {code}
> root@ctr-e138-1518143905142-326354-01-06:~# mysql --user=ambaricustomuser
> --password=bigdatacustom < /tmp/createDB.sql
> mysql: [Warning] Using a password on the command line interface can be
> insecure.
> ERROR 1067 (42000) at line 330 in file: '/tmp/Ambari-DDL-MySQL-CREATE.sql':
> Invalid default value for 'update_time'
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23928) Database script issue when running MYSQL DDL scripts
Srikanth Janardhan created AMBARI-23928:
---
Summary: Database script issue when running MYSQL DDL scripts
Key: AMBARI-23928
URL: https://issues.apache.org/jira/browse/AMBARI-23928
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Srikanth Janardhan
Fix For: 2.7.0
When running Ambari-DDL-MySQL-CREATE.sql file on Mysql with Ubuntu16, getting
the following error:
{code}
root@ctr-e138-1518143905142-326354-01-06:~# mysql --user=ambaricustomuser
--password=bigdatacustom < /tmp/createDB.sql
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1067 (42000) at line 330 in file: '/tmp/Ambari-DDL-MySQL-CREATE.sql':
Invalid default value for 'update_time'
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23922) PERF 1.0 package not installed in the cluster
Srikanth Janardhan created AMBARI-23922:
---
Summary: PERF 1.0 package not installed in the cluster
Key: AMBARI-23922
URL: https://issues.apache.org/jira/browse/AMBARI-23922
Project: Ambari
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Fix For: 2.7.0
the PERF stack version is not installed on the agents
I attempted to reinstall the packages and got the following errors:
{code}
stderr:
Traceback (most recent call last):
File
"/home/perf-0001/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
line 493, in
InstallPackages().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/home/perf-0001/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py",
line 66, in actionexecute
command = 'ambari-python-wrap \{0} install \{1}'.format(stack_selector_path,
repository_version)
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter
'repository_version' was not found in configurations dictionary!
stdout:
Command failed after 1 tries
{code}
This effectively blocks EU on the PERF 1.0 cluster
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23902) YARN service check failure with no permission to submit jobs for ambari-qa user
Srikanth Janardhan created AMBARI-23902:
---
Summary: YARN service check failure with no permission to submit
jobs for ambari-qa user
Key: AMBARI-23902
URL: https://issues.apache.org/jira/browse/AMBARI-23902
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Dmitry Lysnichenko
Fix For: 2.7.0
Service check for YARN failed:
{code}
stderr:
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service_check.py",
line 185, in
ServiceCheck().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/YARN/package/scripts/service_check.py",
line 121, in service_check
user=params.smokeuser,
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 72,
in inner
result = function(command, **kwargs)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 102,
in checked_call
tries=tries, try_sleep=try_sleep,
timeout_kill_strategy=timeout_kill_strategy, returns=returns)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 150,
in _call_wrapper
result = _call(command, **kwargs_copy)
File "/usr/lib/ambari-agent/lib/resource_management/core/shell.py", line 308,
in _call
raise ExecutionFailed(err_msg, code, out, err)
resource_management.core.exceptions.ExecutionFailed: Execution of
'/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
ambari...@example.com; yarn
org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls
-num_containers 1 -jar
/usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar
-timeout 30 --queue default' returned 1. Hortonworks #
This is MOTD message, added for testing in qe infra
18/05/18 11:33:09 INFO distributedshell.Client: Initializing Client
18/05/18 11:33:09 INFO distributedshell.Client: Running Client
18/05/18 11:33:09 INFO client.AHSProxy: Connecting to Application History
server at ctr-e138-1518143905142-317995-01-04.hwx.site/172.27.56.82:10200
18/05/18 11:33:09 INFO client.ConfiguredRMFailoverProxyProvider: Failing over
to rm2
18/05/18 11:33:10 INFO distributedshell.Client: Got Cluster metric info from
ASM, numNodeManagers=3
18/05/18 11:33:10 INFO distributedshell.Client: Got Cluster node info from ASM
18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
nodeId=ctr-e138-1518143905142-317995-01-09.hwx.site:25454,
nodeAddress=ctr-e138-1518143905142-317995-01-09.hwx.site:8042,
nodeRackName=/default-rack, nodeNumContainers=1
18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
nodeId=ctr-e138-1518143905142-317995-01-06.hwx.site:25454,
nodeAddress=ctr-e138-1518143905142-317995-01-06.hwx.site:8042,
nodeRackName=/default-rack, nodeNumContainers=0
18/05/18 11:33:10 INFO distributedshell.Client: Got node report from ASM for,
nodeId=ctr-e138-1518143905142-317995-01-07.hwx.site:25454,
nodeAddress=ctr-e138-1518143905142-317995-01-07.hwx.site:8042,
nodeRackName=/default-rack, nodeNumContainers=0
18/05/18 11:33:10 INFO distributedshell.Client: Queue info, queueName=default,
queueCurrentCapacity=0.02778, queueMaxCapacity=1.0,
queueApplicationCount=0, queueChildQueueCount=0
18/05/18 11:33:10 INFO distributedshell.Client: Max mem capability of resources
in this cluster 12288
18/05/18 11:33:10 INFO distributedshell.Client: Max virtual cores capability of
resources in this cluster 1
18/05/18 11:33:10 WARN distributedshell.Client: AM Memory not specified, use
100 mb as AM memory
18/05/18 11:33:10 WARN distributedshell.Client: AM vcore not specified, use 1
mb as AM vcores
18/05/18 11:33:10 WARN distributedshell.Client: AM Resource capability=
18/05/18 11:33:10 INFO distributedshell.Client: Copy App Master jar from local
filesystem and add to local environment
18/05/18 11:33:11 INFO distributedshell.Client: Set the environment for the
application master
18/05/18 11:33:11 INFO distributedshell.Client: Setting up app master command
18/05/18 11:33:11 INFO distributedshell.Client: Completed setting up app master
command {{JAVA_HOME}}/bin/java -Xmx100m
org.apache.hadoop.yarn.applications.distributedshell.ApplicationMaster
--container_type GUARANTEED --container_memory 10 --container_vcores 1
--num_containers 1 --priority 0 1>/AppMaster.stdout 2>/AppMaster.stderr
18/05/18 11:33:11 INFO hdfs.DFSClient: Created token for ambari-qa:
HDFS_DELEGATION_TOKEN owner=ambari...@example.com, renewer=cstm-yarn,
realUser=, issueDate=1526643191972, maxDate=1527247991972, sequenceNumber=27,
masterKeyId=4 on ha-hdfs:myclus
[jira] [Created] (AMBARI-23834) Rebalance HDFS fails
Srikanth Janardhan created AMBARI-23834:
---
Summary: Rebalance HDFS fails
Key: AMBARI-23834
URL: https://issues.apache.org/jira/browse/AMBARI-23834
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Dmytro Sen
Fix For: 2.7.0
The rebalance HDFS from Ambari is not working.
DFS Usage before rebalance (threshold of 1%)
{code:bash}
[cstm-hdfs@ctr-e138-1518143905142-299595-01-08 root]$ hadoop dfsadmin
-report | grep 'DFS Used%'
WARNING: Use of this script to execute dfsadmin is deprecated.
WARNING: Attempting to execute replacement "hdfs dfsadmin" instead.
DFS Used%: 4.21%
DFS Used%: 1.89%
DFS Used%: 3.40%
DFS Used%: 7.91%
DFS Used%: 3.47%
DFS Used%: 4.67%
DFS Used%: 3.54%
DFS Used%: 2.80%
{code}
After invoking the rebalance HDFS from Ambari UI, the /system/balancer.id file
is not present (meaning balancer is not running)
{code:bash}
[cstm-hdfs@ctr-e138-1518143905142-299595-01-08 root]$ while true; do echo
'checking /system'; hadoop fs -ls /system; sleep 1; done
checking /system
ls: `/system': No such file or directory
checking /system
ls: `/system': No such file or directory
checking /system
ls: `/system': No such file or directory
checking /system
ls: `/system': No such file or directory
checking /system
ls: `/system': No such file or directory
checking /system
^Cchecking /system
ls: `/system': No such file or directory
^C
[cstm-hdfs@ctr-e138-1518143905142-299595-01-08 root]$ hadoop dfsadmin
-report | grep 'DFS Used%'
WARNING: Use of this script to execute dfsadmin is deprecated.
WARNING: Attempting to execute replacement "hdfs dfsadmin" instead.
DFS Used%: 4.21%
DFS Used%: 1.89%
DFS Used%: 3.40%
DFS Used%: 7.91%
DFS Used%: 3.47%
DFS Used%: 4.67%
DFS Used%: 3.54%
DFS Used%: 2.80%
[cstm-hdfs@ctr-e138-1518143905142-299595-01-08 root]$
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23813) Service actions (Stop, Start) not enabled when individual components are stopped
Srikanth Janardhan created AMBARI-23813: --- Summary: Service actions (Stop, Start) not enabled when individual components are stopped Key: AMBARI-23813 URL: https://issues.apache.org/jira/browse/AMBARI-23813 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Srikanth Janardhan Assignee: Andrii Tkach Fix For: 2.7.0 Stop all components from the host detail page and navigate to the service actions. The start/stop button is not enabled. Only on refresh, the Start button is enabled. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23812) Ambari Metrics Collector going down in centos7
Srikanth Janardhan created AMBARI-23812: --- Summary: Ambari Metrics Collector going down in centos7 Key: AMBARI-23812 URL: https://issues.apache.org/jira/browse/AMBARI-23812 Project: Ambari Issue Type: Bug Components: ambari-metrics Affects Versions: 2.7.0 Reporter: Srikanth Janardhan Fix For: 2.7.0 Attachments: metric_collector.zip In ambari-2.7.0.0-477 and HDP-3.0.0.0-1315, ambari metrics goes down after starting. I triggered a config change and restarted all services, post which ambari metrics collector is down. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23802) Action not shown immediately in the BG Operations window
Srikanth Janardhan created AMBARI-23802: --- Summary: Action not shown immediately in the BG Operations window Key: AMBARI-23802 URL: https://issues.apache.org/jira/browse/AMBARI-23802 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Srikanth Janardhan Assignee: Andrii Tkach Fix For: 2.7.0 In ambari-2.7.0.0-472, When an action is selected via the Web UI (From service/host), the action is not shown in the BG Operations window that pops up. It is shown only after a refresh. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23801) Unable to add Hive Metastore from Host detail Page
[
https://issues.apache.org/jira/browse/AMBARI-23801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-23801:
Attachment: Screen Shot 2018-05-09 at 6.18.06 PM.png
> Unable to add Hive Metastore from Host detail Page
> --
>
> Key: AMBARI-23801
> URL: https://issues.apache.org/jira/browse/AMBARI-23801
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Fix For: 2.7.0
>
> Attachments: Screen Shot 2018-05-09 at 6.18.06 PM.png
>
>
> In ambari-2.7.0.0-472,
> Adding Hive Metastore from Host detail page leads to the modal window being
> stuck and javascript errors:
> Javascript errors:
> {code}
> Uncaught TypeError: Cannot read property 'tag' of undefined
> at Class.loadHiveConfigs (app.js:24588)
> at Class.opt.success (app.js:181624)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23801) Unable to add Hive Metastore from Host detail Page
Srikanth Janardhan created AMBARI-23801:
---
Summary: Unable to add Hive Metastore from Host detail Page
Key: AMBARI-23801
URL: https://issues.apache.org/jira/browse/AMBARI-23801
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Andrii Babiichuk
Fix For: 2.7.0
In ambari-2.7.0.0-472,
Adding Hive Metastore from Host detail page leads to the modal window being
stuck and javascript errors:
Javascript errors:
{code}
Uncaught TypeError: Cannot read property 'tag' of undefined
at Class.loadHiveConfigs (app.js:24588)
at Class.opt.success (app.js:181624)
at fire (vendor.js:1141)
at Object.fireWith [as resolveWith] (vendor.js:1252)
at done (vendor.js:8178)
at XMLHttpRequest.callback (vendor.js:8702)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23671) HDP package not installed completely in one host while UI deploy in ubuntu16
Srikanth Janardhan created AMBARI-23671:
---
Summary: HDP package not installed completely in one host while UI
deploy in ubuntu16
Key: AMBARI-23671
URL: https://issues.apache.org/jira/browse/AMBARI-23671
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Fix For: 2.7.0
In cluster [http://ctr-e138-1518143905142-256808-01-02.hwx.site:8080/],
with ambari-2.7.0.0-374 and HDP-3.0.0.0-1236, HDP version is not installed in
one of the hosts.
When a reinstall from the hosts page was attempted, the following error
occurred:
{code:java}
stderr:
2018-04-23 16:46:58,500 - Package Manager failed to install packages. Error:
'NoneType' object has no attribute 'replace'
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py", line
418, in install_packages
retry_count=agent_stack_retry_count
File "/usr/lib/ambari-agent/lib/ambari_commons/repo_manager/apt_manager.py",
line 34, in wrapper
name = args[1].replace("_", "-")
AttributeError: 'NoneType' object has no attribute 'replace'
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py", line
480, in
InstallPackages().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/custom_actions/scripts/install_packages.py", line
149, in actionexecute
raise Fail("Failed to distribute repositories/install packages")
resource_management.core.exceptions.Fail: Failed to distribute
repositories/install packages
stdout:
2018-04-23 16:43:05,693 - Will install packages for repository version
3.0.0.0-1236
2018-04-23 16:43:05,694 - Repository['HDP-3.0-repo-1'] {'append_to_file':
False, 'base_url':
'http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu16/3.x/BUILDS/3.0.0.0-1236',
'action': ['create'], 'components': [u'HDP', 'main'], 'repo_template':
'{{package_type}} {{base_url}} {{components}}', 'repo_file_name':
'ambari-hdp-1', 'mirror_list': None}
2018-04-23 16:43:05,704 - File['/tmp/tmpOEorH6'] {'content': 'deb
http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu16/3.x/BUILDS/3.0.0.0-1236
HDP main'}
2018-04-23 16:43:05,706 - Writing File['/tmp/tmpOEorH6'] because contents don't
match
2018-04-23 16:43:05,706 - File['/tmp/tmpcIEkzf'] {'content':
StaticFile('/etc/apt/sources.list.d/ambari-hdp-1.list')}
2018-04-23 16:43:05,707 - Writing File['/tmp/tmpcIEkzf'] because contents don't
match
2018-04-23 16:43:05,707 - File['/etc/apt/sources.list.d/ambari-hdp-1.list']
{'content': StaticFile('/tmp/tmpOEorH6')}
2018-04-23 16:43:05,708 - Writing
File['/etc/apt/sources.list.d/ambari-hdp-1.list'] because contents don't match
2018-04-23 16:43:05,708 - checked_call[['apt-get', 'update', '-qq', '-o',
u'Dir::Etc::sourcelist=sources.list.d/ambari-hdp-1.list', '-o',
'Dir::Etc::sourceparts=-', '-o', 'APT::Get::List-Cleanup=0']] {'sudo': True,
'quiet': False}
2018-04-23 16:43:06,136 - checked_call returned (0, '')
2018-04-23 16:43:06,138 - Repository['HDP-3.0-GPL-repo-1'] {'append_to_file':
True, 'base_url':
'http://s3.amazonaws.com/dev.hortonworks.com/HDP-GPL/ubuntu16/3.x/BUILDS/3.0.0.0-1236',
'action': ['create'], 'components': [u'HDP-GPL', 'main'], 'repo_template':
'{{package_type}} {{base_url}} {{components}}', 'repo_file_name':
'ambari-hdp-1', 'mirror_list': None}
2018-04-23 16:43:06,141 - File['/tmp/tmpOz0KD_'] {'content': 'deb
http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu16/3.x/BUILDS/3.0.0.0-1236
HDP main\ndeb
http://s3.amazonaws.com/dev.hortonworks.com/HDP-GPL/ubuntu16/3.x/BUILDS/3.0.0.0-1236
HDP-GPL main'}
2018-04-23 16:43:06,141 - Writing File['/tmp/tmpOz0KD_'] because contents don't
match
2018-04-23 16:43:06,142 - File['/tmp/tmpYf7ykB'] {'content':
StaticFile('/etc/apt/sources.list.d/ambari-hdp-1.list')}
2018-04-23 16:43:06,142 - Writing File['/tmp/tmpYf7ykB'] because contents don't
match
2018-04-23 16:43:06,143 - File['/etc/apt/sources.list.d/ambari-hdp-1.list']
{'content': StaticFile('/tmp/tmpOz0KD_')}
2018-04-23 16:43:06,143 - Writing
File['/etc/apt/sources.list.d/ambari-hdp-1.list'] because contents don't match
2018-04-23 16:43:06,144 - checked_call[['apt-get', 'update', '-qq', '-o',
u'Dir::Etc::sourcelist=sources.list.d/ambari-hdp-1.list', '-o',
'Dir::Etc::sourceparts=-', '-o', 'APT::Get::List-Cleanup=0']] {'sudo': True,
'quiet': False}
2018-04-23 16:43:06,834 - checked_call returned (0, '')
2018-04-23 16:43:06,835 - Repository['HDP-UTILS-1.1.0.22-repo-1']
{'append_to_file': True, 'base_url':
'http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.22/repos/ubuntu16',
'action': ['create'], 'components': [u'HDP-UTILS', 'main'], 'repo_template':
'{{package_type}} {{base_url}
[jira] [Created] (AMBARI-23654) Install wizard issues
Srikanth Janardhan created AMBARI-23654:
---
Summary: Install wizard issues
Key: AMBARI-23654
URL: https://issues.apache.org/jira/browse/AMBARI-23654
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Antonenko Alexander
Fix For: 2.7.0
Attachments: Screen Shot 2018-04-05 at 5.35.06 PM.png
When install wizard is running , reloading Ambari fails to load the page
completely.
Reason:
Selected stack from VDF was not saved (or was saved but it is not present on
response)
Stack creation:
POST api/v1/version_definitions?dry_run=true
Request body:
{code:java}
{"VersionDefinition":{"version_url":"http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos7/3.x/BUILDS/3.0.0.0-1223/HDP-3.0.0.0-1223.xml"}}
{code}
Response:
status: 201 created
body:
{code:java}
{
"resources" : [
{
"href" : "http://104.196.80.21:8080/api/v1/version_definitions/";,
"operating_systems" : [
{
"OperatingSystems" : {
"ambari_managed_repositories" : true,
"os_type" : "redhat7",
"stack_name" : "HDP",
"stack_version" : "3.0"
},
"repositories" : [
{
"Repositories" : {
"base_url" :
"http://s3.amazonaws.com/dev.hortonworks.com/HDP/centos7/3.x/BUILDS/3.0.0.0-1223";,
"os_type" : "redhat7",
"repo_id" : "HDP-3.0",
"repo_name" : "HDP",
"distribution" : null,
"components" : null,
"stack_name" : "HDP",
"stack_version" : "3.0",
"tags" : [ ]
}
},
{
"Repositories" : {
"base_url" :
"http://s3.amazonaws.com/dev.hortonworks.com/HDP-GPL/centos7/3.x/BUILDS/3.0.0.0-1223";,
"os_type" : "redhat7",
"repo_id" : "HDP-3.0-GPL",
"repo_name" : "HDP-GPL",
"distribution" : null,
"components" : null,
"stack_name" : "HDP",
"stack_version" : "3.0",
"tags" : [
"GPL"
]
}
},
{
"Repositories" : {
"base_url" :
"http://s3.amazonaws.com/dev.hortonworks.com/HDP-UTILS-1.1.0.22/repos/centos7";,
"os_type" : "redhat7",
"repo_id" : "HDP-UTILS-1.1.0.22",
"repo_name" : "HDP-UTILS",
"distribution" : null,
"components" : null,
"stack_name" : "HDP",
"stack_version" : "3.0",
"tags" : [ ]
}
}
]
}
],
"VersionDefinition" : {
"display_name" : "HDP-3.0.0.0-1223",
"id" : null,
"max_jdk" : "1.8",
"min_jdk" : "1.8",
"repository_version" : "3.0.0.0-1223",
"services" : [
{
"name" : "SQOOP",
"versions" : [
{
"version" : "1.4.7",
"components" : [ ]
}
],
"display_name" : "Sqoop"
},
{
"name" : "DRUID",
"versions" : [
{
"version" : "0.12.0",
"components" : [ ]
}
],
"display_name" : "Druid"
},
{
"name" : "OOZIE",
"versions" : [
{
"version" : "4.2.0",
"components" : [ ]
}
],
"display_name" : "Oozie"
},
{
"name" : "MAPREDUCE2",
"versions" : [
{
"version" : "3.0.0",
"components" : [ ]
}
],
"display_name" : "MapReduce2"
},
{
"name" : "TEZ",
"versions" : [
{
"version" : "0.9.0",
"components" : [ ]
}
],
"display_name" : "Tez"
},
{
"name" : "HDFS",
"versions" : [
{
"version" : "3.0.0",
"components" : [ ]
}
],
"display_name" : "HDFS"
},
{
"name" : "ACCUMULO",
"versions" : [
{
"version" : "1.7.0",
"components" : [ ]
}
],
"display_name" : "Accumulo"
},
{
"name" : "ZOOKEEPER",
"versions" : [
{
"version" : "3.4.6",
"components" : [
[jira] [Created] (AMBARI-23620) Oozie - JDBC Driver class does not change when the Database type is changed
Srikanth Janardhan created AMBARI-23620: --- Summary: Oozie - JDBC Driver class does not change when the Database type is changed Key: AMBARI-23620 URL: https://issues.apache.org/jira/browse/AMBARI-23620 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Srikanth Janardhan Fix For: 2.7.0 Attachments: db-config-issues.mov In ambari 2.7.0.0-330, when the database type is changed for Oozie service, the JDBC server class does not change. This happens in the install wizard as well as post-install. The behavior is different in Hive, where the JDBC server class changes when the database type changes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23613) View instances not created by default
[ https://issues.apache.org/jira/browse/AMBARI-23613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Janardhan reassigned AMBARI-23613: --- Assignee: Myroslav Papirkovskyi > View instances not created by default > - > > Key: AMBARI-23613 > URL: https://issues.apache.org/jira/browse/AMBARI-23613 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.7.0 >Reporter: Srikanth Janardhan >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Fix For: 2.7.0 > > > In ambari-2.7.0, the view instances are not created by default. > In previous versions, the instances of YARN, Files, Hive, Hive 2.0, > Smartsense and Tez were created automatically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23613) View instances not created by default
Srikanth Janardhan created AMBARI-23613: --- Summary: View instances not created by default Key: AMBARI-23613 URL: https://issues.apache.org/jira/browse/AMBARI-23613 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.7.0 Reporter: Srikanth Janardhan Fix For: 2.7.0 In ambari-2.7.0, the view instances are not created by default. In previous versions, the instances of YARN, Files, Hive, Hive 2.0, Smartsense and Tez were created automatically. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23429) Not able to install METRICS_MONITOR
[
https://issues.apache.org/jira/browse/AMBARI-23429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-23429.
-
Resolution: Fixed
> Not able to install METRICS_MONITOR
> ---
>
> Key: AMBARI-23429
> URL: https://issues.apache.org/jira/browse/AMBARI-23429
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> ambari version - 2.7.0.0-246
> metrics monitor installation failed due to below error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 28, in install
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
> line 376, in
> if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir
> is on local file system, create it.
> NameError: name 're' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 28, in install
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
> line 376, in
> if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir
> is on local file system, create it.
> NameError: name 're' is not defined
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23429) Not able to install METRICS_MONITOR
[
https://issues.apache.org/jira/browse/AMBARI-23429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-23429:
Component/s: (was: ambari-agent)
ambari-server
> Not able to install METRICS_MONITOR
> ---
>
> Key: AMBARI-23429
> URL: https://issues.apache.org/jira/browse/AMBARI-23429
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Blocker
> Fix For: 2.7.0
>
>
> ambari version - 2.7.0.0-246
> metrics monitor installation failed due to below error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 28, in install
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
> line 376, in
> if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir
> is on local file system, create it.
> NameError: name 're' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 28, in install
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
> line 376, in
> if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir
> is on local file system, create it.
> NameError: name 're' is not defined
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23429) Not able to install METRICS_MONITOR
[
https://issues.apache.org/jira/browse/AMBARI-23429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-23429:
Description:
ambari version - 2.7.0.0-246
metrics monitor installation failed due to below error
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
{code}
was:
ambari version - 2.7.0.0-246
metrics monitor installation failed due to below error [^blueprint.json]
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
{code}
> Not able to install METRICS_MONITOR
> ---
>
> Key: AMBARI-23429
> URL: https://issues.apache.org/jira/browse/AMBARI-23429
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Blocker
> Fix For: 2.7.0
>
>
> ambari version - 2.7.0.0-246
> metrics monitor installation failed due to below error
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 353, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 28, in install
> import params
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
> line 376, in
> if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir
> is on local file system, create it.
> NameError: name 're' is not defined
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
> line 72, in
> AmsMonitor().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
[jira] [Created] (AMBARI-23429) Not able to install METRICS_MONITOR
Srikanth Janardhan created AMBARI-23429:
---
Summary: Not able to install METRICS_MONITOR
Key: AMBARI-23429
URL: https://issues.apache.org/jira/browse/AMBARI-23429
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Srikanth Janardhan
Fix For: 2.7.0
ambari version - 2.7.0.0-246
metrics monitor installation failed due to below error [^blueprint.json]
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 72, in
AmsMonitor().execute()
File
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 353, in execute
method(env)
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/metrics_monitor.py",
line 28, in install
import params
File
"/var/lib/ambari-agent/cache/stacks/HDP/3.0/services/AMBARI_METRICS/package/scripts/params.py",
line 376, in
if hbase_wal_dir and re.search("^file://|/", hbase_wal_dir): #If wal dir is
on local file system, create it.
NameError: name 're' is not defined
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-22828) Ambari agent registration passes even though the hostnames do not match
[
https://issues.apache.org/jira/browse/AMBARI-22828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-22828.
-
Resolution: Not A Problem
> Ambari agent registration passes even though the hostnames do not match
> ---
>
> Key: AMBARI-22828
> URL: https://issues.apache.org/jira/browse/AMBARI-22828
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.6.2
>Reporter: Srikanth Janardhan
>Priority: Blocker
> Labels: regression
> Fix For: 2.6.2
>
>
> h6. Test Steps
> # # Setup Ambari and start it
> # Start Deployment of HDP till Install Options page
> # Enter different hostnames in Target Hosts field (for e.g. ambari-host.1 and
> ambari-host.2)
> # Change the hostnames for other hosts in the cluster in /etc/hosts in Ambari
> Server machine to match the above 2 host names (e.g. x.x.x.x abc.example.com
> to x.x.x.x ambari-host.1)
> # At this point, other machines in the cluster have different host names from
> what is provided in the server.
> # Add the SSH keys in Install Options page and click "Register and Confirm"
> h6. Expected
> # The ambari agent registration fails in Ambari UI
> # A Warning message appears in the agent logs: {quote}Ambari agent machine
> hostname (ctr-e137-1514896590304-32888-01-05.hwx.site.) does not match
> expected ambari server hostname (ambari.host-1). Aborting registration.
> Please check hostname, hostname -f and /etc/hosts file to confirm your
> hostname is setup correctly{quote}
> h6. Actual
> # Ambari agent registration passes successfully !Screen Shot 2018-01-23 at
> 12.34.06 PM.png|thumbnail!
> # The warning message does not appear in agent logs.
> Whereas attempting a restart of the agent with incorrect hostname does not
> succeed:
> {code:bash}
> [root@ctr-e137-1514896590304-32888-01-03 ~]# /usr/sbin/ambari-agent
> restart --expected-hostname=ambari.host-2
> Restarting ambari-agent
> Verifying Python version compatibility...
> Using python /usr/bin/python
> Found ambari-agent PID: 28192
> Stopping ambari-agent
> Removing PID file at /run/ambari-agent/ambari-agent.pid
> ambari-agent successfully stopped
> Verifying Python version compatibility...
> Using python /usr/bin/python
> Checking for previously running Ambari Agent...
> Checking ambari-common dir...
> Starting ambari-agent
> Killed
> ===
> INFO 2018-01-23 07:03:36,654 DataCleaner.py:120 - Data cleanup started
> INFO 2018-01-23 07:03:36,655 hostname.py:67 - agent:hostname_script
> configuration not defined thus read hostname
> 'ctr-e137-1514896590304-32888-01-03.hwx.site' using socket.getfqdn().
> ERROR 2018-01-23 07:03:36,656 main.py:244 - Ambari agent machine hostname
> (ctr-e137-1514896590304-32888-01-03.hwx.site) does not match expected
> ambari server hostname (ambari.host-2). Aborting registration. Please check
> hostname, hostname -f and /etc/hosts file to confirm your hostname is setup
> correctly
> INFO 2018-01-23 07:03:36,657 ExitHelper.py:56 - Performing cleanup before
> exiting...
> ===
> {code}
> Ambari build: 2.6.2.0-32.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23409) Overflowing list of frozen hosts in Assign Slaves and Clients page
Srikanth Janardhan created AMBARI-23409: --- Summary: Overflowing list of frozen hosts in Assign Slaves and Clients page Key: AMBARI-23409 URL: https://issues.apache.org/jira/browse/AMBARI-23409 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Srikanth Janardhan Fix For: 2.7.0 Attachments: Screen Shot 2018-03-30 at 9.06.19 AM.png, Screen Shot 2018-03-30 at 9.14.33 AM.png When more than 10 hosts are present in a deployed cluster, the frozen hosts column in assign slaves and clients page overflows the boundary and is not scrollable. Version: ambari-server-2.7.0.0-217 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23335) 400 server error when Cluster Administrator tries to add service and move components
Srikanth Janardhan created AMBARI-23335:
---
Summary: 400 server error when Cluster Administrator tries to add
service and move components
Key: AMBARI-23335
URL: https://issues.apache.org/jira/browse/AMBARI-23335
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Attila Magyar
Fix For: 2.7.0
Attachments: screenshot.png
STR:
# Deploy a HDP-3.0 cluster
# Create a user with role as "Cluster Administrator"
# Login as the user
# Click Add Service from the dashboard
# Click Next button in the wizard
The same error occurs while trying the Move Components wizard too.
Issue also present for Cluster Operator Role while moving components.
The page is stuck at this stage even after dismissing the popup.
{code:java|title=ambari-server.log}
17 Mar 2018 16:13:51,740 WARN [ambari-client-thread-524]
StackAdvisorCommand:204 - Error occurred during retrieving ldap configuration,
status=403, response={
"status" : 403,
"message" : "The authenticated user does not have the appropriate
authorizations to get the requested resource(s)"
}
17 Mar 2018 16:13:51,741 WARN [ambari-client-thread-524]
StackAdvisorCommand:182 - Error parsing services.json file content: Error
occurred during retrieving ldap configuration, status=403, response={
"status" : 403,
"message" : "The authenticated user does not have the appropriate
authorizations to get the requested resource(s)"
}
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException: Error
occurred during retrieving ldap configuration, status=403, response={
"status" : 403,
"message" : "The authenticated user does not have the appropriate
authorizations to get the requested resource(s)"
}
at
org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.populateLdapConfiguration(StackAdvisorCommand.java:205)
at
org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.adjust(StackAdvisorCommand.java:177)
at
org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:352)
at
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:132)
at
org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:145)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:296)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
at
org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:50)
at
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
at
org.apache.ambari.server.api.services.RecommendationService.getRecommendation(RecommendationService.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
com.sun.jersey.server.im
[jira] [Resolved] (AMBARI-23274) Database script issue when running MYSQL DDL scripts
[
https://issues.apache.org/jira/browse/AMBARI-23274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-23274.
-
Resolution: Fixed
> Database script issue when running MYSQL DDL scripts
>
>
> Key: AMBARI-23274
> URL: https://issues.apache.org/jira/browse/AMBARI-23274
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Srikanth Janardhan
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> running the
> [script|https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql]
> on MySQL, leads to error where user_authentication table is not present.
> With this user cannot login to Ambari
> {code:bash}
> mysql> CREATE TABLE user_authentication (
> -> user_authentication_id INTEGER,
> -> user_id INTEGER NOT NULL,
> -> authentication_type VARCHAR(50) NOT NULL,
> -> authentication_key TEXT,
> -> create_time TIMESTAMP NOT NULL DEFAULT 0,
> -> update_time TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE
> CURRENT_TIMESTAMP,
> -> CONSTRAINT PK_user_authentication PRIMARY KEY
> (user_authentication_id),
> -> CONSTRAINT FK_user_authentication_users FOREIGN KEY (user_id)
> REFERENCES users (user_id)
> -> );
> ERROR 1067 (42000): Invalid default value for 'create_time'
> {code}
> This is because the DEFAULT value is set to 0 for 'create_time' field.
> Fix: Setting the DEFAULT to {{CURRENT_TIMESTAMP}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23274) Database script issue when running MYSQL DDL scripts
Srikanth Janardhan created AMBARI-23274:
---
Summary: Database script issue when running MYSQL DDL scripts
Key: AMBARI-23274
URL: https://issues.apache.org/jira/browse/AMBARI-23274
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Srikanth Janardhan
Fix For: 2.7.0
running the
[script|https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql]
on MySQL, leads to error where user_authentication table is not present.
With this user cannot login to Ambari
{code:bash}
mysql> CREATE TABLE user_authentication (
-> user_authentication_id INTEGER,
-> user_id INTEGER NOT NULL,
-> authentication_type VARCHAR(50) NOT NULL,
-> authentication_key TEXT,
-> create_time TIMESTAMP NOT NULL DEFAULT 0,
-> update_time TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE
CURRENT_TIMESTAMP,
-> CONSTRAINT PK_user_authentication PRIMARY KEY (user_authentication_id),
-> CONSTRAINT FK_user_authentication_users FOREIGN KEY (user_id)
REFERENCES users (user_id)
-> );
ERROR 1067 (42000): Invalid default value for 'create_time'
{code}
This is because the DEFAULT value is set to 0 for 'create_time' field.
Fix: Setting the DEFAULT to {{CURRENT_TIMESTAMP}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22828) Ambari agent registration passes even though the hostnames do not match
Srikanth Janardhan created AMBARI-22828:
---
Summary: Ambari agent registration passes even though the
hostnames do not match
Key: AMBARI-22828
URL: https://issues.apache.org/jira/browse/AMBARI-22828
Project: Ambari
Issue Type: Bug
Components: ambari-agent
Affects Versions: 2.6.2
Reporter: Srikanth Janardhan
Fix For: 2.6.2
h6. Test Steps
# # Setup Ambari and start it
# Start Deployment of HDP till Install Options page
# Enter different hostnames in Target Hosts field (for e.g. ambari-host.1 and
ambari-host.2)
# Change the hostnames for other hosts in the cluster in /etc/hosts in Ambari
Server machine to match the above 2 host names (e.g. x.x.x.x abc.example.com to
x.x.x.x ambari-host.1)
# At this point, other machines in the cluster have different host names from
what is provided in the server.
# Add the SSH keys in Install Options page and click "Register and Confirm"
h6. Expected
# The ambari agent registration fails in Ambari UI
# A Warning message appears in the agent logs: {quote}Ambari agent machine
hostname (ctr-e137-1514896590304-32888-01-05.hwx.site.) does not match
expected ambari server hostname (ambari.host-1). Aborting registration. Please
check hostname, hostname -f and /etc/hosts file to confirm your hostname is
setup correctly{quote}
h6. Actual
# Ambari agent registration passes successfully !Screen Shot 2018-01-23 at
12.34.06 PM.png|thumbnail!
# The warning message does not appear in agent logs.
Whereas attempting a restart of the agent with incorrect hostname does not
succeed:
{code:bash}
[root@ctr-e137-1514896590304-32888-01-03 ~]# /usr/sbin/ambari-agent restart
--expected-hostname=ambari.host-2
Restarting ambari-agent
Verifying Python version compatibility...
Using python /usr/bin/python
Found ambari-agent PID: 28192
Stopping ambari-agent
Removing PID file at /run/ambari-agent/ambari-agent.pid
ambari-agent successfully stopped
Verifying Python version compatibility...
Using python /usr/bin/python
Checking for previously running Ambari Agent...
Checking ambari-common dir...
Starting ambari-agent
Killed
===
INFO 2018-01-23 07:03:36,654 DataCleaner.py:120 - Data cleanup started
INFO 2018-01-23 07:03:36,655 hostname.py:67 - agent:hostname_script
configuration not defined thus read hostname
'ctr-e137-1514896590304-32888-01-03.hwx.site' using socket.getfqdn().
ERROR 2018-01-23 07:03:36,656 main.py:244 - Ambari agent machine hostname
(ctr-e137-1514896590304-32888-01-03.hwx.site) does not match expected
ambari server hostname (ambari.host-2). Aborting registration. Please check
hostname, hostname -f and /etc/hosts file to confirm your hostname is setup
correctly
INFO 2018-01-23 07:03:36,657 ExitHelper.py:56 - Performing cleanup before
exiting...
===
{code}
Ambari build: 2.6.2.0-32.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Issue Comment Deleted] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-22606:
Comment: was deleted
(was: Reopening as issue occurs in ambari-113)
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-22606.
-
Resolution: Fixed
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan reopened AMBARI-22606:
-
Reopening as issue occurs in ambari-113
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21551) Restart due to Stale configurations leads to an internal system exception
Srikanth Janardhan created AMBARI-21551:
---
Summary: Restart due to Stale configurations leads to an internal
system exception
Key: AMBARI-21551
URL: https://issues.apache.org/jira/browse/AMBARI-21551
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.2
Reporter: Srikanth Janardhan
Assignee: Dmytro Sen
Priority: Critical
Fix For: 2.5.2
In build #116, while performing RBAC API tests, found the following:
POST call:
{code}
http://172.27.58.213:8080/api/v1/clusters/cl1/requests
{"RequestInfo":{"command":"RESTART","context":"Restart all required
services","operation_level":"host_component"},"Requests/resource_filters":[{"hosts_predicate":"HostRoles/stale_configs=true"}]}
{code}
Returns:
{code}
{
"status" : 500,
message" : "An internal system exception occurred: Command execution cannot
proceed without a resource filter."
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
