[jira] [Resolved] (AMBARI-24910) Grafana: Fix for Storm Components and Storm Kafka Offset dashboards
[ https://issues.apache.org/jira/browse/AMBARI-24910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24910. -- Resolution: Fixed > Grafana: Fix for Storm Components and Storm Kafka Offset dashboards > --- > > Key: AMBARI-24910 > URL: https://issues.apache.org/jira/browse/AMBARI-24910 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > These two dashboards error out if no data point is provided. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24910) Grafana: Fix for Storm Components and Storm Kafka Offset dashboards
Ishan Bhatt created AMBARI-24910: Summary: Grafana: Fix for Storm Components and Storm Kafka Offset dashboards Key: AMBARI-24910 URL: https://issues.apache.org/jira/browse/AMBARI-24910 Project: Ambari Issue Type: Bug Components: ambari-metrics Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 These two dashboards error out if no data point is provided. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24898) Add cluster drop down to Grafana aggregate dashboards.
[ https://issues.apache.org/jira/browse/AMBARI-24898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24898. -- Resolution: Fixed > Add cluster drop down to Grafana aggregate dashboards. > -- > > Key: AMBARI-24898 > URL: https://issues.apache.org/jira/browse/AMBARI-24898 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Currently, the HOST based dashboards (System-Servers, HDFS Namenodes, > HBase-Regionservers etc) have a dropdown for the cluster level selection. > This selection determines the set of hosts in the HOST dropdown, and the > cluster is tagged in the API call made by every graph in the dashboard > through the "instanceId" query parameter. > We need to add the cluster dropdown to aggregate dashboards as well. This > cluster selection will also be tagged in the API call (instanceId) like in > other dashboards. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24884) AMS Grafana query editor panel does not work in upgraded version.
[ https://issues.apache.org/jira/browse/AMBARI-24884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24884. -- Resolution: Fixed > AMS Grafana query editor panel does not work in upgraded version. > - > > Key: AMBARI-24884 > URL: https://issues.apache.org/jira/browse/AMBARI-24884 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Following issues are encountered > - Dropdown list not appearing. > - Metrics not automatically refreshed > - Error on collapsing a metric. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24898) Add cluster drop down to Grafana aggregate dashboards.
Ishan Bhatt created AMBARI-24898: Summary: Add cluster drop down to Grafana aggregate dashboards. Key: AMBARI-24898 URL: https://issues.apache.org/jira/browse/AMBARI-24898 Project: Ambari Issue Type: Bug Components: ambari-metrics Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 Currently, the HOST based dashboards (System-Servers, HDFS Namenodes, HBase-Regionservers etc) have a dropdown for the cluster level selection. This selection determines the set of hosts in the HOST dropdown, and the cluster is tagged in the API call made by every graph in the dashboard through the "instanceId" query parameter. We need to add the cluster dropdown to aggregate dashboards as well. This cluster selection will also be tagged in the API call (instanceId) like in other dashboards. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24884) AMS Grafana query editor panel does not work in upgraded version.
[ https://issues.apache.org/jira/browse/AMBARI-24884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24884: - Summary: AMS Grafana query editor panel does not work in upgraded version. (was: Grafana New dashboard edit errors) > AMS Grafana query editor panel does not work in upgraded version. > - > > Key: AMBARI-24884 > URL: https://issues.apache.org/jira/browse/AMBARI-24884 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > > Following issues are encountered > - Dropdown list not appearing. > - Metrics not automatically refreshed > - Error on collapsing a metric. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24884) Grafana New dashboard edit errors
Ishan Bhatt created AMBARI-24884: Summary: Grafana New dashboard edit errors Key: AMBARI-24884 URL: https://issues.apache.org/jira/browse/AMBARI-24884 Project: Ambari Issue Type: Bug Components: ambari-metrics Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 Following issues are encountered - Dropdown list not appearing. - Metrics not automatically refreshed - Error on collapsing a metric. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24836) Service Auto start is enabled after page refresh
[ https://issues.apache.org/jira/browse/AMBARI-24836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24836. -- Resolution: Fixed > Service Auto start is enabled after page refresh > > > Key: AMBARI-24836 > URL: https://issues.apache.org/jira/browse/AMBARI-24836 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Steps to Reproduce: > # Goto Service Auto start page > # Toggle Enable button to disable > # Refresh the page OR Move to another page and come back to 'Service Auto > start' page > Observed that button toggle back to Enabled state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24738) Update grafana datasource to get values from new object
[ https://issues.apache.org/jira/browse/AMBARI-24738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24738. -- Resolution: Fixed > Update grafana datasource to get values from new object > --- > > Key: AMBARI-24738 > URL: https://issues.apache.org/jira/browse/AMBARI-24738 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > > In the new grafana version templateSrv doesn't have some fields. We need to > get these values from a different fields -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24857) UI Changes for supporting Ozone deployment
[ https://issues.apache.org/jira/browse/AMBARI-24857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24857. -- Resolution: Fixed > UI Changes for supporting Ozone deployment > -- > > Key: AMBARI-24857 > URL: https://issues.apache.org/jira/browse/AMBARI-24857 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 2h > Remaining Estimate: 0h > > UI changes: > 1. Allow multi file system for cases where only HDFS and Ozone are being > deployed together. (Currently only single file system is allowed) > 2. If user selects HDFS and Ozone, allow only HDFS Datanodes to be deployed > (Install wizard as well as Add Service Wizard) > 3. If user select Ozone as only service, allow Ozone-Datanodes to be deployed > (cardinality: 1+) > 4. Do not allow HDFS installation via Add Service Wizard if Ozone is deployed. > 5. If Hdfs is already installed don't allow ozone-datanodes during Add Host > Wizard. > 6. Do not allow host component Ozone-Datanodes to be added if HDFS Datanodes > are already added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24417) HDFS Service page Datanode does not show count
[ https://issues.apache.org/jira/browse/AMBARI-24417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24417. -- Resolution: Fixed > HDFS Service page Datanode does not show count > -- > > Key: AMBARI-24417 > URL: https://issues.apache.org/jira/browse/AMBARI-24417 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > In the components section data just shows 'Started' without the actual count. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24834) UI: Configure Rolling Restart Batch Options for service rolling restart
[ https://issues.apache.org/jira/browse/AMBARI-24834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24834. -- Resolution: Fixed > UI: Configure Rolling Restart Batch Options for service rolling restart > --- > > Key: AMBARI-24834 > URL: https://issues.apache.org/jira/browse/AMBARI-24834 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
[ https://issues.apache.org/jira/browse/AMBARI-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24696. -- Resolution: Fixed > UI: Options Page to choose Rolling or Express Restart > - > > Key: AMBARI-24696 > URL: https://issues.apache.org/jira/browse/AMBARI-24696 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-09-26 at 3.21.27 PM.png > > Time Spent: 50m > Remaining Estimate: 0h > > !Screen Shot 2018-09-26 at 3.21.27 PM.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24396) Service theme call failing
[ https://issues.apache.org/jira/browse/AMBARI-24396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24396. -- Resolution: Fixed > Service theme call failing > -- > > Key: AMBARI-24396 > URL: https://issues.apache.org/jira/browse/AMBARI-24396 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > pon clicking service summary page themes call is failing. > ../api/v1/stacks/ODS/versions/1.0.0-b483/services/ZOOKEEPER/themes?ThemeInfo/default=true > for ODS mpack zookeeper is being checked for theme info which is incorrect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24857) UI Changes for supporting Ozone deployment
Ishan Bhatt created AMBARI-24857: Summary: UI Changes for supporting Ozone deployment Key: AMBARI-24857 URL: https://issues.apache.org/jira/browse/AMBARI-24857 Project: Ambari Issue Type: Task Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk UI changes: 1. Allow multi file system for cases where only HDFS and Ozone are being deployed together. (Currently only single file system is allowed) 2. If user selects HDFS and Ozone, allow only HDFS Datanodes to be deployed (Install wizard as well as Add Service Wizard) 3. If user select Ozone as only service, allow Ozone-Datanodes to be deployed (cardinality: 1+) 4. Do not allow HDFS installation via Add Service Wizard if Ozone is deployed. 5. If Hdfs is already installed don't allow ozone-datanodes during Add Host Wizard. 6. Do not allow host component Ozone-Datanodes to be added if HDFS Datanodes are already added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24836) Service Auto start is enabled after page refresh
[ https://issues.apache.org/jira/browse/AMBARI-24836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24836: - Fix Version/s: (was: trunk) 2.8.0 > Service Auto start is enabled after page refresh > > > Key: AMBARI-24836 > URL: https://issues.apache.org/jira/browse/AMBARI-24836 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Fix For: 2.8.0 > > > Steps to Reproduce: > # Goto Service Auto start page > # Toggle Enable button to disable > # Refresh the page OR Move to another page and come back to 'Service Auto > start' page > Observed that button toggle back to Enabled state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24836) Service Auto start is enabled after page refresh
Ishan Bhatt created AMBARI-24836: Summary: Service Auto start is enabled after page refresh Key: AMBARI-24836 URL: https://issues.apache.org/jira/browse/AMBARI-24836 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk Steps to Reproduce: # Goto Service Auto start page # Toggle Enable button to disable # Refresh the page OR Move to another page and come back to 'Service Auto start' page Observed that button toggle back to Enabled state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24834) UI: Configure Rolling Restart Batch Options for service rolling restart
Ishan Bhatt created AMBARI-24834: Summary: UI: Configure Rolling Restart Batch Options for service rolling restart Key: AMBARI-24834 URL: https://issues.apache.org/jira/browse/AMBARI-24834 Project: Ambari Issue Type: Task Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24803) Separating Restart All, Masters and Slaves
[ https://issues.apache.org/jira/browse/AMBARI-24803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24803. -- Resolution: Fixed > Separating Restart All, Masters and Slaves > -- > > Key: AMBARI-24803 > URL: https://issues.apache.org/jira/browse/AMBARI-24803 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Three separate options for service restarts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24803) Separating Restart All, Masters and Slaves
Ishan Bhatt created AMBARI-24803: Summary: Separating Restart All, Masters and Slaves Key: AMBARI-24803 URL: https://issues.apache.org/jira/browse/AMBARI-24803 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 Three separate options for service restarts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24790) Restart Masters for Service Restart
[ https://issues.apache.org/jira/browse/AMBARI-24790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24790. -- Resolution: Fixed > Restart Masters for Service Restart > --- > > Key: AMBARI-24790 > URL: https://issues.apache.org/jira/browse/AMBARI-24790 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24791) Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated
[ https://issues.apache.org/jira/browse/AMBARI-24791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24791. -- Resolution: Fixed > Node Managers fail to start after RM is moved to a different host as > 'resource-tracker.address' config is not updated > - > > Key: AMBARI-24791 > URL: https://issues.apache.org/jira/browse/AMBARI-24791 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.3 > > Time Spent: 1h > Remaining Estimate: 0h > > # Under Yarn --> Service Actions - choose to Move Resource Manager. Pick a > new host for the active RM node and let the move operation complete > # Observe the state of Node Managers in Ambari UI > *Result* > All Node Managers show as down. > Observed that one of the configs - > 'yarn.resourcemanager.resource-tracker.address.rm2' still points to older RM > node[!Screen Shot 2018-10-11 at 6.20.51 > PM.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/165347/165347_Screen+Shot+2018-10-11+at+6.20.51+PM.png] > , which may be causing this issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24791) Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated
Ishan Bhatt created AMBARI-24791: Summary: Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated Key: AMBARI-24791 URL: https://issues.apache.org/jira/browse/AMBARI-24791 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.7.3 # Under Yarn --> Service Actions - choose to Move Resource Manager. Pick a new host for the active RM node and let the move operation complete # Observe the state of Node Managers in Ambari UI *Result* All Node Managers show as down. Observed that one of the configs - 'yarn.resourcemanager.resource-tracker.address.rm2' still points to older RM node[!Screen Shot 2018-10-11 at 6.20.51 PM.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/165347/165347_Screen+Shot+2018-10-11+at+6.20.51+PM.png] , which may be causing this issue -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24790) Restart Masters for Service Restart
Ishan Bhatt created AMBARI-24790: Summary: Restart Masters for Service Restart Key: AMBARI-24790 URL: https://issues.apache.org/jira/browse/AMBARI-24790 Project: Ambari Issue Type: Task Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24779) Move Namenode operation fails as it tries to install and start ZKFailoverController on non-HA cluster
[
https://issues.apache.org/jira/browse/AMBARI-24779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-24779.
--
Resolution: Fixed
> Move Namenode operation fails as it tries to install and start
> ZKFailoverController on non-HA cluster
> --
>
> Key: AMBARI-24779
> URL: https://issues.apache.org/jira/browse/AMBARI-24779
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Error at final screen during Service start for ZKFailoverController. This is
> unexpected as the cluster is non-HA and ZKFailoverController component should
> not be attempted for a start at all on the new NN host
> {code:java}
> 2018-10-11 14:22:52,136 - Execute['ambari-sudo.sh su cstm-hdfs -l -s
> /bin/bash -c 'ulimit -c unlimited ; /usr/hdp/3.0.3.0-74/hadoop/bin/hdfs
> --config /usr/hdp/3.0.3.0-74/hadoop/conf --daemon start zkfc'']
> {'environment': {'HADOOP_LIBEXEC_DIR': '/usr/hdp/3.0.3.0-74/hadoop/libexec'},
> 'not_if': 'ambari-sudo.sh -H -E test -f
> /var/run/hadoop/cstm-hdfs/hadoop-cstm-hdfs-zkfc.pid && ambari-sudo.sh -H -E
> pgrep -F /var/run/hadoop/cstm-hdfs/hadoop-cstm-hdfs-zkfc.pid'}
> 2018-10-11 14:22:54,336 - Execute['find /grid/0/log/hdfs/cstm-hdfs -maxdepth
> 1 -type f -name '*' -exec echo '==> {} <==' \; -exec tail -n 40 {} \;']
> {'logoutput': True, 'ignore_failures': True, 'user': 'cstm-hdfs'}
> Hortonworks #
> This is MOTD message, added for testing in qe infra
> ==>
> /grid/0/log/hdfs/cstm-hdfs/hadoop-cstm-hdfs-zkfc-ctr-e138-1518143905142-517699-01-03.hwx.site.out
> <==
> Exception in thread "main" org.apache.hadoop.HadoopIllegalArgumentException:
> HA is not enabled for this namenode.
> at
> org.apache.hadoop.hdfs.tools.DFSZKFailoverController.create(DFSZKFailoverController.java:134)
> at
> org.apache.hadoop.hdfs.tools.DFSZKFailoverController.main(DFSZKFailoverController.java:192)
> core file size (blocks, -c) unlimited
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24779) Move Namenode operation fails as it tries to install and start ZKFailoverController on non-HA cluster
Ishan Bhatt created AMBARI-24779:
Summary: Move Namenode operation fails as it tries to install and
start ZKFailoverController on non-HA cluster
Key: AMBARI-24779
URL: https://issues.apache.org/jira/browse/AMBARI-24779
Project: Ambari
Issue Type: Bug
Components: ambari-web
Reporter: Ishan Bhatt
Assignee: Ishan Bhatt
Fix For: 2.7.3
Error at final screen during Service start for ZKFailoverController. This is
unexpected as the cluster is non-HA and ZKFailoverController component should
not be attempted for a start at all on the new NN host
{code:java}
2018-10-11 14:22:52,136 - Execute['ambari-sudo.sh su cstm-hdfs -l -s /bin/bash
-c 'ulimit -c unlimited ; /usr/hdp/3.0.3.0-74/hadoop/bin/hdfs --config
/usr/hdp/3.0.3.0-74/hadoop/conf --daemon start zkfc''] {'environment':
{'HADOOP_LIBEXEC_DIR': '/usr/hdp/3.0.3.0-74/hadoop/libexec'}, 'not_if':
'ambari-sudo.sh -H -E test -f
/var/run/hadoop/cstm-hdfs/hadoop-cstm-hdfs-zkfc.pid && ambari-sudo.sh -H -E
pgrep -F /var/run/hadoop/cstm-hdfs/hadoop-cstm-hdfs-zkfc.pid'}
2018-10-11 14:22:54,336 - Execute['find /grid/0/log/hdfs/cstm-hdfs -maxdepth 1
-type f -name '*' -exec echo '==> {} <==' \; -exec tail -n 40 {} \;']
{'logoutput': True, 'ignore_failures': True, 'user': 'cstm-hdfs'}
Hortonworks #
This is MOTD message, added for testing in qe infra
==>
/grid/0/log/hdfs/cstm-hdfs/hadoop-cstm-hdfs-zkfc-ctr-e138-1518143905142-517699-01-03.hwx.site.out
<==
Exception in thread "main" org.apache.hadoop.HadoopIllegalArgumentException: HA
is not enabled for this namenode.
at
org.apache.hadoop.hdfs.tools.DFSZKFailoverController.create(DFSZKFailoverController.java:134)
at
org.apache.hadoop.hdfs.tools.DFSZKFailoverController.main(DFSZKFailoverController.java:192)
core file size (blocks, -c) unlimited
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24738) Update grafana datasource to get values from new object
Ishan Bhatt created AMBARI-24738: Summary: Update grafana datasource to get values from new object Key: AMBARI-24738 URL: https://issues.apache.org/jira/browse/AMBARI-24738 Project: Ambari Issue Type: Task Components: ambari-metrics Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk In the new grafana version templateSrv doesn't have some fields. We need to get these values from a different fields -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24720) UI: Configure Rolling Restart Advanced Options
[ https://issues.apache.org/jira/browse/AMBARI-24720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24720. -- Resolution: Fixed > UI: Configure Rolling Restart Advanced Options > -- > > Key: AMBARI-24720 > URL: https://issues.apache.org/jira/browse/AMBARI-24720 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24720) UI: Configure Rolling Restart Advanced Options
Ishan Bhatt created AMBARI-24720: Summary: UI: Configure Rolling Restart Advanced Options Key: AMBARI-24720 URL: https://issues.apache.org/jira/browse/AMBARI-24720 Project: Ambari Issue Type: Task Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
[ https://issues.apache.org/jira/browse/AMBARI-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24696: - Description: !Screen Shot 2018-09-26 at 3.21.27 PM.png! > UI: Options Page to choose Rolling or Express Restart > - > > Key: AMBARI-24696 > URL: https://issues.apache.org/jira/browse/AMBARI-24696 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-09-26 at 3.21.27 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > !Screen Shot 2018-09-26 at 3.21.27 PM.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
[ https://issues.apache.org/jira/browse/AMBARI-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24696: - Attachment: Screen Shot 2018-09-26 at 3.21.27 PM.png > UI: Options Page to choose Rolling or Express Restart > - > > Key: AMBARI-24696 > URL: https://issues.apache.org/jira/browse/AMBARI-24696 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Attachments: Screen Shot 2018-09-26 at 3.21.27 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
[ https://issues.apache.org/jira/browse/AMBARI-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24696: - Attachment: (was: Screen Shot 2018-09-26 at 3.03.48 PM.png) > UI: Options Page to choose Rolling or Express Restart > - > > Key: AMBARI-24696 > URL: https://issues.apache.org/jira/browse/AMBARI-24696 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
[ https://issues.apache.org/jira/browse/AMBARI-24696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24696: - Description: (was: !Screen Shot 2018-09-26 at 3.03.48 PM.png!) > UI: Options Page to choose Rolling or Express Restart > - > > Key: AMBARI-24696 > URL: https://issues.apache.org/jira/browse/AMBARI-24696 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24696) UI: Options Page to choose Rolling or Express Restart
Ishan Bhatt created AMBARI-24696: Summary: UI: Options Page to choose Rolling or Express Restart Key: AMBARI-24696 URL: https://issues.apache.org/jira/browse/AMBARI-24696 Project: Ambari Issue Type: Task Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.8.0 Attachments: Screen Shot 2018-09-26 at 3.03.48 PM.png !Screen Shot 2018-09-26 at 3.03.48 PM.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24665) Migrating grafana plugin for 5.x use
[ https://issues.apache.org/jira/browse/AMBARI-24665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24665. -- Resolution: Fixed > Migrating grafana plugin for 5.x use > > > Key: AMBARI-24665 > URL: https://issues.apache.org/jira/browse/AMBARI-24665 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24665) Migrating grafana plugin for 5.x use
Ishan Bhatt created AMBARI-24665: Summary: Migrating grafana plugin for 5.x use Key: AMBARI-24665 URL: https://issues.apache.org/jira/browse/AMBARI-24665 Project: Ambari Issue Type: Bug Components: ambari-metrics Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24636) Add Service wizard fails if a service without configs is installed
[ https://issues.apache.org/jira/browse/AMBARI-24636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24636. -- Resolution: Fixed > Add Service wizard fails if a service without configs is installed > -- > > Key: AMBARI-24636 > URL: https://issues.apache.org/jira/browse/AMBARI-24636 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 50m > Remaining Estimate: 0h > > Fails during the Customize services page -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24636) Add Service wizard fails if a service without configs is installed
Ishan Bhatt created AMBARI-24636: Summary: Add Service wizard fails if a service without configs is installed Key: AMBARI-24636 URL: https://issues.apache.org/jira/browse/AMBARI-24636 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.7.2 Fails during the Customize services page -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24577) Services should display the "Stop" button if any of their components are started
[ https://issues.apache.org/jira/browse/AMBARI-24577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt resolved AMBARI-24577. -- Resolution: Fixed > Services should display the "Stop" button if any of their components are > started > > > Key: AMBARI-24577 > URL: https://issues.apache.org/jira/browse/AMBARI-24577 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In Ambari 2.7, the "Stop" button for each service is only available if all > its components are started. This means that if any component is not started > (or down), the rest of the components must be stopped individually from every > host. > [!5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/162070/162070_5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png] > > For services where one component cannot be started (for example, due to > memory limitations), stopping the service can be a very painful exercise. > Please enable the "stop" button to be triggered, if any component of a > service can be stopped. > Similarly for the Start button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24577) Services should display the "Stop" button if any of their components are started
[ https://issues.apache.org/jira/browse/AMBARI-24577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24577: - Fix Version/s: 2.7.2 > Services should display the "Stop" button if any of their components are > started > > > Key: AMBARI-24577 > URL: https://issues.apache.org/jira/browse/AMBARI-24577 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: trunk, 2.7.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > In Ambari 2.7, the "Stop" button for each service is only available if all > its components are started. This means that if any component is not started > (or down), the rest of the components must be stopped individually from every > host. > [!5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/162070/162070_5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png] > > For services where one component cannot be started (for example, due to > memory limitations), stopping the service can be a very painful exercise. > Please enable the "stop" button to be triggered, if any component of a > service can be stopped. > Similarly for the Start button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24577) Services should display the "Stop" button if any of their components are started
Ishan Bhatt created AMBARI-24577: Summary: Services should display the "Stop" button if any of their components are started Key: AMBARI-24577 URL: https://issues.apache.org/jira/browse/AMBARI-24577 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk In Ambari 2.7, the "Stop" button for each service is only available if all its components are started. This means that if any component is not started (or down), the rest of the components must be stopped individually from every host. [!5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/162070/162070_5516EB4E-F2A5-44DA-8A4A-453C40FDA0E4.png] For services where one component cannot be started (for example, due to memory limitations), stopping the service can be a very painful exercise. Please enable the "stop" button to be triggered, if any component of a service can be stopped. Similarly for the Start button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24523) Hive and Oozie JDBC url reset after set manually
[ https://issues.apache.org/jira/browse/AMBARI-24523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24523: - Fix Version/s: (was: 2.7.1) 2.7.2 > Hive and Oozie JDBC url reset after set manually > > > Key: AMBARI-24523 > URL: https://issues.apache.org/jira/browse/AMBARI-24523 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt >Priority: Major > Labels: pull-request-available > Fix For: 2.7.2 > > Time Spent: 20m > Remaining Estimate: 0h > > JDBC urls of Hive and Oozie are reset even after being set manually when > toggling RANGER plugins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24523) Hive and Oozie JDBC url reset after set manually
Ishan Bhatt created AMBARI-24523: Summary: Hive and Oozie JDBC url reset after set manually Key: AMBARI-24523 URL: https://issues.apache.org/jira/browse/AMBARI-24523 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.1 Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 2.7.1 JDBC urls of Hive and Oozie are reset even after being set manually when toggling RANGER plugins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24452) [UI Deploy] LLAP queue is not created/set in YARN configs while enabling HSI
Ishan Bhatt created AMBARI-24452:
Summary: [UI Deploy] LLAP queue is not created/set in YARN configs
while enabling HSI
Key: AMBARI-24452
URL: https://issues.apache.org/jira/browse/AMBARI-24452
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.1
Reporter: Ishan Bhatt
Assignee: Ishan Bhatt
Fix For: 2.7.1
In a cluster installed via UI deploy:
HSI was enabled as part of UI install wizard, but in the YARN configs, the
'llap' queue is not added leading to deploy failures. (Hive Server Interactive
did not start)
{code:java}
Failed: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
application_1532935384747_0002 to YARN : Application
application_1532935384747_0002 submitted by user hive to unknown queue: llap
java.lang.RuntimeException: org.apache.hadoop.yarn.exceptions.YarnException:
Failed to submit application_1532935384747_0002 to YARN : Application
application_1532935384747_0002 submitted by user hive to unknown queue: llap
at
org.apache.hadoop.hive.llap.cli.LlapSliderUtils.startCluster(LlapSliderUtils.java:154)
at
org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:602)
at
org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:120)
Caused by: org.apache.hadoop.yarn.exceptions.YarnException: Failed to submit
application_1532935384747_0002 to YARN : Application
application_1532935384747_0002 submitted by user hive to unknown queue: llap
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.submitApplication(YarnClientImpl.java:304)
at
org.apache.hadoop.yarn.service.client.ServiceClient.submitApp(ServiceClient.java:837)
at
org.apache.hadoop.yarn.service.client.ServiceClient.actionCreate(ServiceClient.java:365)
at
org.apache.hadoop.yarn.service.client.ServiceClient.actionLaunch(ServiceClient.java:351)
at
org.apache.hadoop.hive.llap.cli.LlapSliderUtils.startCluster(LlapSliderUtils.java:149)
... 2 more
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24417) HDFS Service page Datanode does not show count
Ishan Bhatt created AMBARI-24417: Summary: HDFS Service page Datanode does not show count Key: AMBARI-24417 URL: https://issues.apache.org/jira/browse/AMBARI-24417 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 3.0.0 In the components section data just shows 'Started' without the actual count. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24396) Service theme call failing
Ishan Bhatt created AMBARI-24396: Summary: Service theme call failing Key: AMBARI-24396 URL: https://issues.apache.org/jira/browse/AMBARI-24396 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: 3.0.0 pon clicking service summary page themes call is failing. ../api/v1/stacks/ODS/versions/1.0.0-b483/services/ZOOKEEPER/themes?ThemeInfo/default=true for ODS mpack zookeeper is being checked for theme info which is incorrect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24341) UI service configs page hangs.
[
https://issues.apache.org/jira/browse/AMBARI-24341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-24341.
--
Resolution: Duplicate
> UI service configs page hangs.
> ---
>
> Key: AMBARI-24341
> URL: https://issues.apache.org/jira/browse/AMBARI-24341
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Ishan Bhatt
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-07-23 at 3.29.26 PM.png, Screen Shot
> 2018-07-23 at 3.29.42 PM.png
>
>
> *ISSUE:*
> UI Service Config page hangs when clicked post deploy.
> Below is the calls made:
> -
> http://172.27.56.18:8080/api/v1/clusters/cl1?fields=Clusters/desired_configs&_=1532384868506
>
> which succeeds.
> !Screen Shot 2018-07-23 at 3.29.26 PM.png! !Screen Shot 2018-07-23 at
> 3.29.42 PM.png!
> And then the UI code fails :
> {code}
> app.js:1898 Uncaught TypeError: Cannot read property 'always' of undefined
> at Class. (app.js:1898)
> 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}
> at *line 6* while processing the response:
> {code}
> 1 loadConfigProperties: function loadConfigProperties() {
> 2var self = this;
> 3
> App.config.loadConfigsFromStack(App.Service.find().mapProperty('serviceName')).always(function
> () {
> 4 App.config.loadClusterConfigsFromStack().always(function () {
> 5
> App.router.get('configurationController').updateConfigTags().always(function
> () {
> 6
> App.router.get('updateController').updateClusterEnv().always(function () {
> 7self.set('isConfigsPropertiesLoaded', true);
> 8 });
> });
> });
> });
> },
> {code}
> .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24342) PostTrunkMerge : UI issue at Step 7 of deploy, while getting configs for service.
[
https://issues.apache.org/jira/browse/AMBARI-24342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-24342.
--
Resolution: Fixed
> PostTrunkMerge : UI issue at Step 7 of deploy, while getting configs for
> service.
> -
>
> Key: AMBARI-24342
> URL: https://issues.apache.org/jira/browse/AMBARI-24342
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> *ISSUE:*
> Post Trunk merge, deploy fails at Step 7.
> *Console O/P:*
> {code:java}
> app.js:67915 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.updateAttributesFromTheme
> (http://172.22.107.63:8080/javascripts/app.js:67915:90)
> at http://172.22.107.63:8080/javascripts/app.js:44914:21
> at Array.forEach (native)
> at Class.updateConfigAttributesFromThemes
> (http://172.22.107.63:8080/javascripts/app.js:44913:41)
> at Class.applyServicesConfigs
> (http://172.22.107.63:8080/javascripts/app.js:43405:10)
> at Class.loadStep (http://172.22.107.63:8080/javascripts/app.js:43345:12)
> at Class.willInsertElement
> (http://172.22.107.63:8080/javascripts/app.js:249561:30)
> at Class.newFunc [as willInsertElement]
> (http://172.22.107.63:8080/javascripts/vendor.js:12954:16)
> at Class.trigger
> (http://172.22.107.63:8080/javascripts/vendor.js:25526:21)
> at Class.newFunc [as trigger]
> (http://172.22.107.63:8080/javascripts/vendor.js:12954:16)
> {code}
> Code line:
> {code:java}
> updateAttributesFromTheme: function updateAttributesFromTheme(serviceName) {
> this.prepareSectionsConfigProperties(serviceName);
> var serviceConfigs = this.get('stepConfigs').findProperty('serviceName',
> serviceName).get('configs'), <-- Issue LINE
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24350) UI service configs page hangs.
[
https://issues.apache.org/jira/browse/AMBARI-24350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-24350.
--
Resolution: Fixed
> UI service configs page hangs.
> --
>
> Key: AMBARI-24350
> URL: https://issues.apache.org/jira/browse/AMBARI-24350
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Ishan Bhatt
>Assignee: Ishan Bhatt
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> UI code fails :
> {code:java}
> app.js:1898 Uncaught TypeError: Cannot read property 'always' of undefined
> at Class. (app.js:1898)
> 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}
> at *line 6* while processing the response:
> {code:java}
> 1 loadConfigProperties: function loadConfigProperties() {
> 2var self = this;
> 3
> App.config.loadConfigsFromStack(App.Service.find().mapProperty('serviceName')).always(function
> () {
> 4 App.config.loadClusterConfigsFromStack().always(function () {
> 5
> App.router.get('configurationController').updateConfigTags().always(function
> () {
> 6
> App.router.get('updateController').updateClusterEnv().always(function () {
> 7self.set('isConfigsPropertiesLoaded', true);
> 8 });
> });
> });
> });
> },
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24350) UI service configs page hangs.
Ishan Bhatt created AMBARI-24350:
Summary: UI service configs page hangs.
Key: AMBARI-24350
URL: https://issues.apache.org/jira/browse/AMBARI-24350
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 3.0.0
Reporter: Ishan Bhatt
Assignee: Ishan Bhatt
Fix For: 3.0.0
UI code fails :
{code:java}
app.js:1898 Uncaught TypeError: Cannot read property 'always' of undefined
at Class. (app.js:1898)
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}
at *line 6* while processing the response:
{code:java}
1 loadConfigProperties: function loadConfigProperties() {
2var self = this;
3
App.config.loadConfigsFromStack(App.Service.find().mapProperty('serviceName')).always(function
() {
4 App.config.loadClusterConfigsFromStack().always(function () {
5
App.router.get('configurationController').updateConfigTags().always(function ()
{
6
App.router.get('updateController').updateClusterEnv().always(function () {
7self.set('isConfigsPropertiesLoaded', true);
8 });
});
});
});
},
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24342) PostTrunkMerge : UI issue at Step 7 of deploy, while getting configs for service.
Ishan Bhatt created AMBARI-24342:
Summary: PostTrunkMerge : UI issue at Step 7 of deploy, while
getting configs for service.
Key: AMBARI-24342
URL: https://issues.apache.org/jira/browse/AMBARI-24342
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 3.0.0
Reporter: Ishan Bhatt
Assignee: Ishan Bhatt
Fix For: 3.0.0
*ISSUE:*
Post Trunk merge, deploy fails at Step 7.
*Console O/P:*
{code:java}
app.js:67915 Uncaught TypeError: Cannot read property 'get' of undefined
at Class.updateAttributesFromTheme
(http://172.22.107.63:8080/javascripts/app.js:67915:90)
at http://172.22.107.63:8080/javascripts/app.js:44914:21
at Array.forEach (native)
at Class.updateConfigAttributesFromThemes
(http://172.22.107.63:8080/javascripts/app.js:44913:41)
at Class.applyServicesConfigs
(http://172.22.107.63:8080/javascripts/app.js:43405:10)
at Class.loadStep (http://172.22.107.63:8080/javascripts/app.js:43345:12)
at Class.willInsertElement
(http://172.22.107.63:8080/javascripts/app.js:249561:30)
at Class.newFunc [as willInsertElement]
(http://172.22.107.63:8080/javascripts/vendor.js:12954:16)
at Class.trigger (http://172.22.107.63:8080/javascripts/vendor.js:25526:21)
at Class.newFunc [as trigger]
(http://172.22.107.63:8080/javascripts/vendor.js:12954:16)
{code}
Code line:
{code:java}
updateAttributesFromTheme: function updateAttributesFromTheme(serviceName) {
this.prepareSectionsConfigProperties(serviceName);
var serviceConfigs = this.get('stepConfigs').findProperty('serviceName',
serviceName).get('configs'), <-- Issue LINE
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24276) Upgrade failed at ConvertTable, container mode, with data deployed
Ishan Bhatt created AMBARI-24276:
Summary: Upgrade failed at ConvertTable, container mode, with data
deployed
Key: AMBARI-24276
URL: https://issues.apache.org/jira/browse/AMBARI-24276
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Ishan Bhatt
Assignee: Miklos Gergely
Fix For: 2.7.1
Upgrade failed for cluster where pre-upgrade data deploy was done, container
mode.
{noformat}
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize
class org.apache.derby.jdbc.AutoloadedDriver40
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at java.sql.DriverManager.isDriverAllowed(DriverManager.java:556)
at java.sql.DriverManager.getConnection(DriverManager.java:661)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at com.jolbox.bonecp.BoneCP.obtainRawInternalConnection(BoneCP.java:351)
at com.jolbox.bonecp.BoneCP.(BoneCP.java:416)
at
com.jolbox.bonecp.BoneCPDataSource.getConnection(BoneCPDataSource.java:120)
at
org.apache.hadoop.hive.metastore.txn.TxnHandler.getDbConn(TxnHandler.java:1935)
at
org.apache.hadoop.hive.metastore.txn.TxnHandler.getDbConn(TxnHandler.java:1928)
at
org.apache.hadoop.hive.metastore.txn.TxnHandler.setConf(TxnHandler.java:270)
at
org.apache.hadoop.hive.metastore.txn.TxnUtils.getTxnStore(TxnUtils.java:115)
at
org.apache.hadoop.hive.upgrade.acid.PreUpgradeTool.prepareAcidUpgradeInternal(PreUpgradeTool.java:229)
at
org.apache.hadoop.hive.upgrade.acid.PreUpgradeTool.main(PreUpgradeTool.java:148)
Command failed after 1 tries{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24276) Upgrade failed at ConvertTable, container mode, with data deployed
[
https://issues.apache.org/jira/browse/AMBARI-24276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539217#comment-16539217
]
Ishan Bhatt commented on AMBARI-24276:
--
This needs to get into trunk for now
> Upgrade failed at ConvertTable, container mode, with data deployed
> --
>
> Key: AMBARI-24276
> URL: https://issues.apache.org/jira/browse/AMBARI-24276
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Ishan Bhatt
>Assignee: Miklos Gergely
>Priority: Major
> Fix For: 2.7.1
>
>
> Upgrade failed for cluster where pre-upgrade data deploy was done, container
> mode.
> {noformat}
> Exception in thread "main" java.lang.NoClassDefFoundError: Could not
> initialize class org.apache.derby.jdbc.AutoloadedDriver40
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at java.sql.DriverManager.isDriverAllowed(DriverManager.java:556)
> at java.sql.DriverManager.getConnection(DriverManager.java:661)
> at java.sql.DriverManager.getConnection(DriverManager.java:247)
> at com.jolbox.bonecp.BoneCP.obtainRawInternalConnection(BoneCP.java:351)
> at com.jolbox.bonecp.BoneCP.(BoneCP.java:416)
> at
> com.jolbox.bonecp.BoneCPDataSource.getConnection(BoneCPDataSource.java:120)
> at
> org.apache.hadoop.hive.metastore.txn.TxnHandler.getDbConn(TxnHandler.java:1935)
> at
> org.apache.hadoop.hive.metastore.txn.TxnHandler.getDbConn(TxnHandler.java:1928)
> at
> org.apache.hadoop.hive.metastore.txn.TxnHandler.setConf(TxnHandler.java:270)
> at
> org.apache.hadoop.hive.metastore.txn.TxnUtils.getTxnStore(TxnUtils.java:115)
> at
> org.apache.hadoop.hive.upgrade.acid.PreUpgradeTool.prepareAcidUpgradeInternal(PreUpgradeTool.java:229)
> at
> org.apache.hadoop.hive.upgrade.acid.PreUpgradeTool.main(PreUpgradeTool.java:148)
> Command failed after 1 tries{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24187) Ambari Server Setup LDAP Label Updates
[
https://issues.apache.org/jira/browse/AMBARI-24187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538040#comment-16538040
]
Ishan Bhatt commented on AMBARI-24187:
--
Moving it out to 2.7.1
> Ambari Server Setup LDAP Label Updates
> --
>
> Key: AMBARI-24187
> URL: https://issues.apache.org/jira/browse/AMBARI-24187
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 2.7.1
>
>
> It was noticed in the bug bash that there were issues with label names and
> defaults. In an effort to make them easier to read and fix the issues
> identified, the following labels, default values, and spacing before ':'
> changes need to be made. Please make the wizard look just like the text below:
> {code}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host:
> Primary LDAP Port:
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (user):
> User ID attribute (sAMAccountName):
> Group object class (group):
> Group name attribute (cn):
> Group member attribute (member):
> Distinguished name attribute (distinguishedName):
> Search Base (dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (cn=ldapbind,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> Force lower-case user names [true/false] (true):
> Results from LDAP are paginated when requested [true/false] (false):
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24199) Fix Atlas HA support in Ambari via blueprint deployment
[
https://issues.apache.org/jira/browse/AMBARI-24199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538041#comment-16538041
]
Ishan Bhatt commented on AMBARI-24199:
--
Moving it out to 2.7.1
> Fix Atlas HA support in Ambari via blueprint deployment
> ---
>
> Key: AMBARI-24199
> URL: https://issues.apache.org/jira/browse/AMBARI-24199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Robert Nettleton
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently deploying Atlas in HA mode via blueprint is not possible due to
> property
> [{{atlas.server.bind.address}}|https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java#L3156]
> being set by Blueprint Processor, need to remove the property from being
> processed in Blueprint Processor and let the default value to be effective.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24187) Ambari Server Setup LDAP Label Updates
[
https://issues.apache.org/jira/browse/AMBARI-24187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24187:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Ambari Server Setup LDAP Label Updates
> --
>
> Key: AMBARI-24187
> URL: https://issues.apache.org/jira/browse/AMBARI-24187
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Krisztian Kasa
>Assignee: Krisztian Kasa
>Priority: Major
> Fix For: 2.7.1
>
>
> It was noticed in the bug bash that there were issues with label names and
> defaults. In an effort to make them easier to read and fix the issues
> identified, the following labels, default values, and spacing before ':'
> changes need to be made. Please make the wizard look just like the text below:
> {code}
> # ambari-server setup-ldap
> Using python /usr/bin/python
> Currently 'no auth method' is configured, do you wish to use LDAP instead
> [y/n] (y)?
> Primary LDAP Host:
> Primary LDAP Port:
> Secondary LDAP Host :
> Secondary LDAP Port :
> Use SSL [true/false] (false):
> User object class (user):
> User ID attribute (sAMAccountName):
> Group object class (group):
> Group name attribute (cn):
> Group member attribute (member):
> Distinguished name attribute (distinguishedName):
> Search Base (dc=ambari,dc=apache,dc=org):
> Referral method [follow/ignore] (follow):
> Bind anonymously [true/false] (false):
> Bind DN (cn=ldapbind,dc=ambari,dc=apache,dc=org):
> Enter Bind DN Password:
> Confirm Bind DN Password:
> Handling behavior for username collisions [convert/skip] for LDAP sync
> (skip):
> Force lower-case user names [true/false] (true):
> Results from LDAP are paginated when requested [true/false] (false):
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24199) Fix Atlas HA support in Ambari via blueprint deployment
[
https://issues.apache.org/jira/browse/AMBARI-24199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24199:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Fix Atlas HA support in Ambari via blueprint deployment
> ---
>
> Key: AMBARI-24199
> URL: https://issues.apache.org/jira/browse/AMBARI-24199
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vishal Suvagia
>Assignee: Robert Nettleton
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.1
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently deploying Atlas in HA mode via blueprint is not possible due to
> property
> [{{atlas.server.bind.address}}|https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java#L3156]
> being set by Blueprint Processor, need to remove the property from being
> processed in Blueprint Processor and let the default value to be effective.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24004) [Logsearch UI] Add hosts link in log index filter popup is not working
[ https://issues.apache.org/jira/browse/AMBARI-24004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24004: - Resolution: Fixed Status: Resolved (was: Patch Available) > [Logsearch UI] Add hosts link in log index filter popup is not working > -- > > Key: AMBARI-24004 > URL: https://issues.apache.org/jira/browse/AMBARI-24004 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Kishor Ramakrishnan >Assignee: Istvan Tobias >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Add hosts link in log index filter popup is not working. > STR > 1. Login to Logsearch portal > 2. Click to filter log index from menu, select a valid cluster from the drop > down > 3. Try to add custom filters for host, user should be able to add custom > filter index for additional hosts by clicking add hosts link. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538039#comment-16538039 ] Ishan Bhatt commented on AMBARI-24118: -- Moving it out to 2.7.1 > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24118: - Fix Version/s: (was: 2.7.0) 2.7.1 > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23976) Ambari changes required for YARN are missing
[ https://issues.apache.org/jira/browse/AMBARI-23976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23976: - Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari changes required for YARN are missing > > > Key: AMBARI-23976 > URL: https://issues.apache.org/jira/browse/AMBARI-23976 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23976.patch, AMBARI-23976.patch, > AMBARI-23976.patch > > Time Spent: 2h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24204) Ambari upgrade should set storm kerberos config to correct value
[ https://issues.apache.org/jira/browse/AMBARI-24204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24204: - Fix Version/s: (was: 2.7.0) 2.7.1 > Ambari upgrade should set storm kerberos config to correct value > > > Key: AMBARI-24204 > URL: https://issues.apache.org/jira/browse/AMBARI-24204 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23005) Failed to Add Big SQL to HDP 3.0 due to a stack advisor error on calculating slave component dependencies
[ https://issues.apache.org/jira/browse/AMBARI-23005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23005: - Resolution: Fixed Status: Resolved (was: Patch Available) > Failed to Add Big SQL to HDP 3.0 due to a stack advisor error on calculating > slave component dependencies > - > > Key: AMBARI-23005 > URL: https://issues.apache.org/jira/browse/AMBARI-23005 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Di Li >Assignee: Di Li >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Failed to Add Big SQL to HDP 3.0 due to a stack advisor error on calculating > slave component dependencies. > Error printed by Ambari server > Error occured in stack advisor. > Error details: 'StackServiceComponents' > 14 Feb 2018 12:32:54,260 INFO [ambari-client-thread-94] > StackAdvisorRunner:164 - Advisor script stderr: Traceback (most recent call > last): > File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 167, > in > main(sys.argv) > File "/var/lib/ambari-server/resources/scripts/stack_advisor.py", line 108, > in main > result = stackAdvisor.recommendComponentLayout(services, hosts) > File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", > line 608, in recommendComponentLayout > layoutRecommendations = self.createComponentLayoutRecommendations(services, > hosts) > File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", > line 794, in createComponentLayoutRecommendations > filteredHosts = self.getFilteredHostsBasedOnDependencies(services, > component, hostsList, hostsComponentsMap) > File "/var/lib/ambari-server/resources/scripts/../stacks/stack_advisor.py", > line 928, in getFilteredHostsBasedOnDependencies > componentName = component["StackServiceComponents"]["component_name"] > KeyError: 'StackServiceComponents' > 14 Feb 2018 12:32:54,260 WARN [ambari-client-thread-94] > AbstractResourceProvider:97 - Error occured during recommendation > org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException: > Stack Advisor reported an error. Exit Code: 2. Error: KeyError: > 'StackServiceComponents' > StdOut file: /var/run/ambari-server/stack-recommendations/32/stackadvisor.out > StdErr file: /var/run/ambari-server/stack-recommendations/32/stackadvisor.err > at > org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.processLogs(StackAdvisorRunner.java:146) > at > org.apache.ambari.server.api.services.stackadvisor.StackAdvisorRunner.runScript(StackAdvisorRunner.java:86) > at > org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:345) > at > org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:132) > at > org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:92) > 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:45) > at > org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:76) > at > org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:166) > at > org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:130) > 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
[jira] [Updated] (AMBARI-23522) Revert AMBARI-23385
[ https://issues.apache.org/jira/browse/AMBARI-23522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23522: - Resolution: Fixed Status: Resolved (was: Patch Available) > Revert AMBARI-23385 > --- > > Key: AMBARI-23522 > URL: https://issues.apache.org/jira/browse/AMBARI-23522 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24204) Ambari upgrade should set storm kerberos config to correct value
[ https://issues.apache.org/jira/browse/AMBARI-24204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538036#comment-16538036 ] Ishan Bhatt commented on AMBARI-24204: -- Moving it out to 2.7.1 > Ambari upgrade should set storm kerberos config to correct value > > > Key: AMBARI-24204 > URL: https://issues.apache.org/jira/browse/AMBARI-24204 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Jaimin Jetly >Assignee: Jaimin Jetly >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538035#comment-16538035 ] Ishan Bhatt commented on AMBARI-23817: -- Moving it out to 2.7.1 > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Fix For: 2.7.1 > > Attachments: AMBARI-23817-trunk.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23817) Visualizing the Encrypted zones and Erasure coded zones in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-23817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23817: - Fix Version/s: (was: 2.7.0) 2.7.1 > Visualizing the Encrypted zones and Erasure coded zones in HDFS > --- > > Key: AMBARI-23817 > URL: https://issues.apache.org/jira/browse/AMBARI-23817 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Critical > Fix For: 2.7.1 > > Attachments: AMBARI-23817-trunk.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > For hadoop 3.0 Files view should show whether a folder or file is Encrypted > or not and what Erasure coding policy is used for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24224) Error in persisting web client state at ambari-server in editing a widget of HDFS
[ https://issues.apache.org/jira/browse/AMBARI-24224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24224: - Resolution: Fixed Status: Resolved (was: Patch Available) > Error in persisting web client state at ambari-server in editing a widget of > HDFS > -- > > Key: AMBARI-24224 > URL: https://issues.apache.org/jira/browse/AMBARI-24224 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Sandor Molnar >Assignee: Sandor Molnar >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > STR > # Login as admin to Ambari > # Install a cluster with HDFS, ZK and AMS > # Go to Services / HDFS / Metrics and edit one of the widgets (for instance > change the name of the widget) > # Create a new user with 'Cluster Operator' role > # Logout and login with the newly created user > # Try to edit the previously edit widget > The action will fail due to an authorization issue (403 is thrown). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24192) WebSockets traffic does not work between Ambari Web UI and Ambari Server when it is accessed via Knox Proxy (UI side changes)
[ https://issues.apache.org/jira/browse/AMBARI-24192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538033#comment-16538033 ] Ishan Bhatt commented on AMBARI-24192: -- Moving it out to 2.7.1 > WebSockets traffic does not work between Ambari Web UI and Ambari Server when > it is accessed via Knox Proxy (UI side changes) > - > > Key: AMBARI-24192 > URL: https://issues.apache.org/jira/browse/AMBARI-24192 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 20m > Remaining Estimate: 0h > > When connected via Knox proxy ambari server web socket URL should be changed > from ://: port>/api/stomp/v1/websocket to ://: port>/gateway/default/ambari/websocket -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24229) Prevent Configuration Changes During Keytab Regeneration in an Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-24229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt resolved AMBARI-24229.
--
Resolution: Fixed
> Prevent Configuration Changes During Keytab Regeneration in an Upgrade
> --
>
> Key: AMBARI-24229
> URL: https://issues.apache.org/jira/browse/AMBARI-24229
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Kavan Suresh
>Assignee: Robert Levas
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> Certain configuration changes should be avoided when regenerating keytab
> files during different scenarios.
> For example, existing non-Kerberos configurations should not be changed
> during the regenerate keytabs operation performed during an upgrade. However
> it is necessary for Kerberos identity-related configurations (such as keytab
> file paths and principal names) to be added and updated; as well as allow for
> new Kerberos-related configurations to be added.
> To allow for this, a new _update configuration policy_ value has been added
> to the set of directives (*_config_update_policy_*) allowed when issuing a
> call to regenerate keytab files. This directive replaces the less flexible
> *_ignore_config_updates_* directive which only allows a user to enable or
> disable the ability for the operation to change configurations. The values
> allowed for *_config_update_policy_* are as follows:
> * {{none}} - No configurations will be updated
> * {{identities_only}} - New and updated configurations related to Kerberos
> identity information - principal, keytab file, and auth-to-local rule
> properties
> * {{new_and_identities}} - Only new configurations declared by the Kerberos
> descriptor and stack advisor as well as the identity-related changes
> * {{all}} - All configuration changes
> During an upgrade, the _update configuration policy_ is set to
> {{new_and_identities}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24250) Create Checkpoint page stuck while Enabling HA on Namenode
[
https://issues.apache.org/jira/browse/AMBARI-24250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24250:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> 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
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 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/64786d Inode: 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] [Updated] (AMBARI-24192) WebSockets traffic does not work between Ambari Web UI and Ambari Server when it is accessed via Knox Proxy (UI side changes)
[ https://issues.apache.org/jira/browse/AMBARI-24192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24192: - Fix Version/s: (was: 2.7.0) 2.7.1 > WebSockets traffic does not work between Ambari Web UI and Ambari Server when > it is accessed via Knox Proxy (UI side changes) > - > > Key: AMBARI-24192 > URL: https://issues.apache.org/jira/browse/AMBARI-24192 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 20m > Remaining Estimate: 0h > > When connected via Knox proxy ambari server web socket URL should be changed > from ://: port>/api/stomp/v1/websocket to ://: port>/gateway/default/ambari/websocket -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23925) Zeppelin is not respecting the absolute hdfs path for notebooks
[ https://issues.apache.org/jira/browse/AMBARI-23925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538032#comment-16538032 ] Ishan Bhatt commented on AMBARI-23925: -- Moving it out to 2.7.1 > Zeppelin is not respecting the absolute hdfs path for notebooks > --- > > Key: AMBARI-23925 > URL: https://issues.apache.org/jira/browse/AMBARI-23925 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma >Priority: Blocker > Fix For: 2.7.1 > > > Zeppelin is not respecting the absolute hdfs path and picking up the > incorrect path for notebooks. > Even when user is setting 'zeppelin.notebook.dir' as > 'hdfs://ns2/zeppelin/tmp/tmp1/notebook', ambari is picking up the path as > /user/zeppelin/hdfs://ns2/zeppelin/tmp/tmp1/notebook > and due to this zeppelin service start is failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23921) If Kerberos is enabled, then stack upgrade prerequisite check should ensure the KDC admin credential is persisted
[ https://issues.apache.org/jira/browse/AMBARI-23921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23921: - Resolution: Fixed Status: Resolved (was: Patch Available) > If Kerberos is enabled, then stack upgrade prerequisite check should ensure > the KDC admin credential is persisted > - > > Key: AMBARI-23921 > URL: https://issues.apache.org/jira/browse/AMBARI-23921 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Blocker > Labels: kerberos, pull-request-available, upgrade > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > > If Kerberos is enabled and Ambari is managing Kerberos identities, then the > stack upgrade prerequisite check should ensure that the KDC admin credential > is stored in the Ambari persisted credential store. > # The Ambari credential store must be set up (ambari-server setup-security, > option #2) > # The KDC administrator credential is stored in the Ambari credential store > (persisted) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23925) Zeppelin is not respecting the absolute hdfs path for notebooks
[ https://issues.apache.org/jira/browse/AMBARI-23925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23925: - Fix Version/s: (was: 2.7.0) 2.7.1 > Zeppelin is not respecting the absolute hdfs path for notebooks > --- > > Key: AMBARI-23925 > URL: https://issues.apache.org/jira/browse/AMBARI-23925 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Affects Versions: 2.7.0 >Reporter: Supreeth Sharma >Assignee: Supreeth Sharma >Priority: Blocker > Fix For: 2.7.1 > > > Zeppelin is not respecting the absolute hdfs path and picking up the > incorrect path for notebooks. > Even when user is setting 'zeppelin.notebook.dir' as > 'hdfs://ns2/zeppelin/tmp/tmp1/notebook', ambari is picking up the path as > /user/zeppelin/hdfs://ns2/zeppelin/tmp/tmp1/notebook > and due to this zeppelin service start is failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23785) Download client configs fails at Oozie client with AttributeError
[
https://issues.apache.org/jira/browse/AMBARI-23785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-23785:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Download client configs fails at Oozie client with AttributeError
> -
>
> Key: AMBARI-23785
> URL: https://issues.apache.org/jira/browse/AMBARI-23785
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> - Deploy cluster for ambari-270 and HDP-3.0
> - Download client configs for the cluster
> - This fails with below error
> {code}
> {
> status: 500,
> message: "org.apache.ambari.server.controller.spi.SystemException: Execution
> of "ambari-python-wrap
> /var/lib/ambari-server/resources/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_client.py
> generate_configs
> /var/lib/ambari-server/data/tmp/OOZIE_CLIENT2729746438603000677-configuration.json
> /var/lib/ambari-server/resources/stacks/HDP/3.0/services/OOZIE/package
> /var/lib/ambari-server/data/tmp/structured-out.json INFO
> /var/lib/ambari-server/data/tmp" returned 1. java.lang.Throwable: 2018-04-30
> 21:20:41,087 - Stack Feature Version Info: Cluster Stack=3.0, Command
> Stack=None, Command Version=None -> 3.0 2018-04-30 21:20:41,109 - Using
> hadoop conf dir: /usr/hdp/3.0.0.0-1279/hadoop/conf 2018-04-30 21:20:41,209 -
> Directory['/var/lib/ambari-server/data/tmp'] \{'create_parents': True}
> 2018-04-30 21:20:41,293 - XmlConfig['oozie-site.xml'] {} Traceback (most
> recent call last): File
> "/var/lib/ambari-server/resources/stacks/HDP/3.0/services/OOZIE/package/scripts/oozie_client.py",
> line 74, in OozieClient().execute() File
> "/usr/lib/ambari-server/lib/resource_management/libraries/script/script.py",
> line 353, in execute method(env) File
> "/usr/lib/ambari-server/lib/resource_management/libraries/script/script.py",
> line 1093, in generate_configs Directory(conf_tmp_dir, action="delete") File
> "/usr/lib/ambari-server/lib/resource_management/core/base.py", line 166, in
> __init__ self.env.run() File
> "/usr/lib/ambari-server/lib/resource_management/core/environment.py", line
> 160, in run self.run_action(resource, action) File
> "/usr/lib/ambari-server/lib/resource_management/core/environment.py", line
> 124, in run_action provider_action() File
> "/usr/lib/ambari-server/lib/resource_management/libraries/providers/xml_config.py",
> line 60, in action_create xml_config_dest_file_path =
> os.path.join(xml_config_provider_config_dir, filename) File
> "/usr/lib64/python2.7/posixpath.py", line 77, in join elif path == '' or
> path.endswith('/'): AttributeError: 'NoneType' object has no attribute
> 'endswith' "
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23026) WEB type alerts authentication in Kerberos secured cluster
[ https://issues.apache.org/jira/browse/AMBARI-23026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23026: - Fix Version/s: (was: 2.7.0) 2.7.1 > WEB type alerts authentication in Kerberos secured cluster > -- > > Key: AMBARI-23026 > URL: https://issues.apache.org/jira/browse/AMBARI-23026 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.5.2, trunk, 2.6.2 > Environment: Ambari 2.5.2 > Hortonworks HDP-2.5.3.0-37 >Reporter: David F. Quiroga >Assignee: Robert Levas >Priority: Minor > Fix For: 2.7.1 > > > In a Kerberized cluster some web endpoints (App Timeline Web UI, > ResourceManger Web UI, etc.) require authentication. Any Ambari alerts > checking those endpoints must then be able to authenticate. > This was addressed in AMBARI-9586, however the default principal and keytab > used in the alerts.json is that of the "bare" SPNEGO principal > HTTP/_HOST@REALM. > My understanding is that the HTTP service principal is used to authenticate > users to a service, not used to authenticate to another service. > 1. Since most endpoints involved are Web UI, would it be more appropriate to > use the smokeuser in the alerts? > 2. This was first observed in Ranger Audit, the YARN Ranger Plug-in showed > many access denied from HTTP user. [This > post|https://community.hortonworks.com/content/supportkb/150206/ranger-audit-logs-refers-to-access-denied-for-http.html] > provided some direction as to where those requests were coming from. We have > updated the ResourceManger Web UI alert definition to use > cluster-env/smokeuser_keytab and cluster-env/smokeuser_principal_name and > this has resolved the initial HTTP access denied. > Would it also be advisable to make the change in the other secure Web UI > alert definitions? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23026) WEB type alerts authentication in Kerberos secured cluster
[ https://issues.apache.org/jira/browse/AMBARI-23026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538029#comment-16538029 ] Ishan Bhatt commented on AMBARI-23026: -- Moving it out to 2.7.1 > WEB type alerts authentication in Kerberos secured cluster > -- > > Key: AMBARI-23026 > URL: https://issues.apache.org/jira/browse/AMBARI-23026 > Project: Ambari > Issue Type: Bug > Components: alerts >Affects Versions: 2.5.2, trunk, 2.6.2 > Environment: Ambari 2.5.2 > Hortonworks HDP-2.5.3.0-37 >Reporter: David F. Quiroga >Assignee: Robert Levas >Priority: Minor > Fix For: 2.7.1 > > > In a Kerberized cluster some web endpoints (App Timeline Web UI, > ResourceManger Web UI, etc.) require authentication. Any Ambari alerts > checking those endpoints must then be able to authenticate. > This was addressed in AMBARI-9586, however the default principal and keytab > used in the alerts.json is that of the "bare" SPNEGO principal > HTTP/_HOST@REALM. > My understanding is that the HTTP service principal is used to authenticate > users to a service, not used to authenticate to another service. > 1. Since most endpoints involved are Web UI, would it be more appropriate to > use the smokeuser in the alerts? > 2. This was first observed in Ranger Audit, the YARN Ranger Plug-in showed > many access denied from HTTP user. [This > post|https://community.hortonworks.com/content/supportkb/150206/ranger-audit-logs-refers-to-access-denied-for-http.html] > provided some direction as to where those requests were coming from. We have > updated the ResourceManger Web UI alert definition to use > cluster-env/smokeuser_keytab and cluster-env/smokeuser_principal_name and > this has resolved the initial HTTP access denied. > Would it also be advisable to make the change in the other secure Web UI > alert definitions? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23890) [Logsearch UI] Column headers are missing in service logs tabular view
[ https://issues.apache.org/jira/browse/AMBARI-23890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-23890: - Fix Version/s: (was: 2.7.0) 2.7.1 > [Logsearch UI] Column headers are missing in service logs tabular view > -- > > Key: AMBARI-23890 > URL: https://issues.apache.org/jira/browse/AMBARI-23890 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Kishor Ramakrishnan >Priority: Minor > Fix For: 2.7.1 > > > Column headers are missing in service logs tabular view. > STR: > 1. Login to Logsearch portal > 2. Select valid time range with more than 10 log entries > 3. Click on Tabular view of logs > 4. Column headers should be displayed similar to the tabular view of Audit > logs page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23890) [Logsearch UI] Column headers are missing in service logs tabular view
[ https://issues.apache.org/jira/browse/AMBARI-23890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538031#comment-16538031 ] Ishan Bhatt commented on AMBARI-23890: -- Moving it out to 2.7.1 > [Logsearch UI] Column headers are missing in service logs tabular view > -- > > Key: AMBARI-23890 > URL: https://issues.apache.org/jira/browse/AMBARI-23890 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Kishor Ramakrishnan >Priority: Minor > Fix For: 2.7.1 > > > Column headers are missing in service logs tabular view. > STR: > 1. Login to Logsearch portal > 2. Select valid time range with more than 10 log entries > 3. Click on Tabular view of logs > 4. Column headers should be displayed similar to the tabular view of Audit > logs page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24227) Add Namespace: Hive Metastore fails to start because NN is in safemode
[
https://issues.apache.org/jira/browse/AMBARI-24227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538027#comment-16538027
]
Ishan Bhatt commented on AMBARI-24227:
--
Moving it out to 2.7.1
> Add Namespace: Hive Metastore fails to start because NN is in safemode
> --
>
> Key: AMBARI-24227
> URL: https://issues.apache.org/jira/browse/AMBARI-24227
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> Add Namespace: Hive Metastore fails to start because NN is in safemode
> {code}
> 18/06/29 10:43:41 INFO retry.RetryInvocationHandler:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.RetriableException):
> org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot modify ACL
> entries on /warehouse/tablespace/external/hive. Name node is in safe mode.
> The reported blocks 0 needs additional 1791 blocks to reach the threshold
> 1. of total blocks 1791.
> The number of live datanodes 0 has reached the minimum number 0. Safe mode
> will be turned off automatically once the thresholds have been reached.
> NamenodeHostName:
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkNameNodeSafeMode(FSNamesystem.java:1441)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.modifyAclEntries(FSNamesystem.java:7112)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.modifyAclEntries(NameNodeRpcServer.java:2045)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.modifyAclEntries(ClientNamenodeProtocolServerSideTranslatorPB.java:1442)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:872)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:818)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1688)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2678)
> Caused by: org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot
> modify ACL entries on /warehouse/tablespace/external/hive. Name node is in
> safe mode.
> The reported blocks 0 needs additional 1791 blocks to reach the threshold
> 1. of total blocks 1791.
> The number of live datanodes 0 has reached the minimum number 0. Safe mode
> will be turned off automatically once the thresholds have been reached.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24231) Adding additional jars in classpath of ambari views.
[ https://issues.apache.org/jira/browse/AMBARI-24231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24231: - Fix Version/s: (was: 2.7.0) 2.7.1 > Adding additional jars in classpath of ambari views. > > > Key: AMBARI-24231 > URL: https://issues.apache.org/jira/browse/AMBARI-24231 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-24212) Restart Indicators for Hdfs, Yarn, MR2 present after adding Knox
[ https://issues.apache.org/jira/browse/AMBARI-24212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538026#comment-16538026 ] Ishan Bhatt commented on AMBARI-24212: -- Moving it out to 2.7.1 > Restart Indicators for Hdfs, Yarn, MR2 present after adding Knox > > > Key: AMBARI-24212 > URL: https://issues.apache.org/jira/browse/AMBARI-24212 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > > STR: > 1) Create hdfs and yarn Config Groups > 2) Override some hdfs-site and yarn-site configs > 3) Now add Knox > After adding knox, Hdfs, Yarn and MR2 have restart indicators but they should > not have them > On deleting knox, this issue was not reproduced > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24227) Add Namespace: Hive Metastore fails to start because NN is in safemode
[
https://issues.apache.org/jira/browse/AMBARI-24227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24227:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Add Namespace: Hive Metastore fails to start because NN is in safemode
> --
>
> Key: AMBARI-24227
> URL: https://issues.apache.org/jira/browse/AMBARI-24227
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> Add Namespace: Hive Metastore fails to start because NN is in safemode
> {code}
> 18/06/29 10:43:41 INFO retry.RetryInvocationHandler:
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.RetriableException):
> org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot modify ACL
> entries on /warehouse/tablespace/external/hive. Name node is in safe mode.
> The reported blocks 0 needs additional 1791 blocks to reach the threshold
> 1. of total blocks 1791.
> The number of live datanodes 0 has reached the minimum number 0. Safe mode
> will be turned off automatically once the thresholds have been reached.
> NamenodeHostName:
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkNameNodeSafeMode(FSNamesystem.java:1441)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.modifyAclEntries(FSNamesystem.java:7112)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.modifyAclEntries(NameNodeRpcServer.java:2045)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.modifyAclEntries(ClientNamenodeProtocolServerSideTranslatorPB.java:1442)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:523)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:991)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:872)
> at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:818)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1688)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2678)
> Caused by: org.apache.hadoop.hdfs.server.namenode.SafeModeException: Cannot
> modify ACL entries on /warehouse/tablespace/external/hive. Name node is in
> safe mode.
> The reported blocks 0 needs additional 1791 blocks to reach the threshold
> 1. of total blocks 1791.
> The number of live datanodes 0 has reached the minimum number 0. Safe mode
> will be turned off automatically once the thresholds have been reached.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24231) Adding additional jars in classpath of ambari views.
[ https://issues.apache.org/jira/browse/AMBARI-24231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538028#comment-16538028 ] Ishan Bhatt commented on AMBARI-24231: -- Moving it out to 2.7.1 > Adding additional jars in classpath of ambari views. > > > Key: AMBARI-24231 > URL: https://issues.apache.org/jira/browse/AMBARI-24231 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.0 >Reporter: Nitiraj Singh Rathore >Assignee: Nitiraj Singh Rathore >Priority: Major > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24211) UI Install: Stackadvisor does not show GPL Error
[
https://issues.apache.org/jira/browse/AMBARI-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24211:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> UI Install: Stackadvisor does not show GPL Error
>
>
> Key: AMBARI-24211
> URL: https://issues.apache.org/jira/browse/AMBARI-24211
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> STR:
> 1) Setup ambari server and deny gpl license
> \{code}gpl.license.accepted=false\{code}
> 2) In customize services page, add the following properties
> {code:java}
> io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
>
> {code}
> io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
> (custom)
>
> 3) On clicking next button, it proceeds to the next step
> Expected Behavior : On clicking next button, show StackAdvisor error
> something like "Your Ambari Server has not been configured to download LZO
> and install it" and stop user from navigating to next page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24211) UI Install: Stackadvisor does not show GPL Error
[
https://issues.apache.org/jira/browse/AMBARI-24211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538025#comment-16538025
]
Ishan Bhatt commented on AMBARI-24211:
--
Moving it out to 2.7.1
> UI Install: Stackadvisor does not show GPL Error
>
>
> Key: AMBARI-24211
> URL: https://issues.apache.org/jira/browse/AMBARI-24211
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> STR:
> 1) Setup ambari server and deny gpl license
> \{code}gpl.license.accepted=false\{code}
> 2) In customize services page, add the following properties
> {code:java}
> io.compression.codecs=org.apache.hadoop.io.compress.GzipCodec,org.apache.hadoop.io.compress.DefaultCodec,org.apache.hadoop.io.compress.SnappyCodec,com.hadoop.compression.lzo.LzoCodec,com.hadoop.compression.lzo.LzopCodec\{code}
>
> {code}
> io.compression.codec.lzo.class = com.hadoop.compression.lzo.LzoCodec\{code}
> (custom)
>
> 3) On clicking next button, it proceeds to the next step
> Expected Behavior : On clicking next button, show StackAdvisor error
> something like "Your Ambari Server has not been configured to download LZO
> and install it" and stop user from navigating to next page
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24207) Python unit test failure on 2.7.6
[
https://issues.apache.org/jira/browse/AMBARI-24207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538024#comment-16538024
]
Ishan Bhatt commented on AMBARI-24207:
--
Moving it out to 2.7.1
> Python unit test failure on 2.7.6
> -
>
> Key: AMBARI-24207
> URL: https://issues.apache.org/jira/browse/AMBARI-24207
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.1
>
>
> Python unit tests fail on Python 2.7.6, because
> [SSLContext|https://docs.python.org/2/library/ssl.html#ssl-contexts] was only
> added in 2.7.9.
> {noformat:title=https://builds.apache.org/job/Ambari-trunk-Commit/9543/consoleText}
> ERROR: test_ldap_sync_ssl (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
> line 7804, in test_ldap_sync_ssl
> sync_ldap(options)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupSecurity.py",
> line 405, in sync_ldap
> raise FatalException(1, err)
> FatalException: "Fatal exception: Sync event creation failed. Error details:
> 'module' object has no attribute 'SSLContext', exit code 1"
> ERROR: test_get_ssl_context (TestServerUtils.TestServerUtils)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestServerUtils.py",
> line 124, in test_get_ssl_context
> context = get_ssl_context(properties)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverUtils.py",
> line 274, in get_ssl_context
> context = ssl.SSLContext(protocol)
> AttributeError: 'module' object has no attribute 'SSLContext'
> {noformat}
> CC [~rlevas]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24205) TestHeartbeatHandler.testComponents is flaky
[
https://issues.apache.org/jira/browse/AMBARI-24205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538023#comment-16538023
]
Ishan Bhatt commented on AMBARI-24205:
--
Moving it out to 2.7.1
> TestHeartbeatHandler.testComponents is flaky
>
>
> Key: AMBARI-24205
> URL: https://issues.apache.org/jira/browse/AMBARI-24205
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.1
>
>
> {{TestHeartbeatHandler.testComponents}} is failing ~15% of the time.
> {noformat}
> [ERROR] Tests run: 24, Failures: 1, Errors: 0, Skipped: 8, Time elapsed:
> 36.768 s <<< FAILURE! - in org.apache.ambari.server.agent.TestHeartbeatHandler
> [ERROR] testComponents(org.apache.ambari.server.agent.TestHeartbeatHandler)
> Time elapsed: 1.203 s <<< FAILURE!
> java.lang.AssertionError: expected:<{HDFS={NAMENODE=MASTER}}> but was:<{}>
> at
> org.apache.ambari.server.agent.TestHeartbeatHandler.testComponents(TestHeartbeatHandler.java:1352)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24205) TestHeartbeatHandler.testComponents is flaky
[
https://issues.apache.org/jira/browse/AMBARI-24205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24205:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> TestHeartbeatHandler.testComponents is flaky
>
>
> Key: AMBARI-24205
> URL: https://issues.apache.org/jira/browse/AMBARI-24205
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.1
>
>
> {{TestHeartbeatHandler.testComponents}} is failing ~15% of the time.
> {noformat}
> [ERROR] Tests run: 24, Failures: 1, Errors: 0, Skipped: 8, Time elapsed:
> 36.768 s <<< FAILURE! - in org.apache.ambari.server.agent.TestHeartbeatHandler
> [ERROR] testComponents(org.apache.ambari.server.agent.TestHeartbeatHandler)
> Time elapsed: 1.203 s <<< FAILURE!
> java.lang.AssertionError: expected:<{HDFS={NAMENODE=MASTER}}> but was:<{}>
> at
> org.apache.ambari.server.agent.TestHeartbeatHandler.testComponents(TestHeartbeatHandler.java:1352)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24212) Restart Indicators for Hdfs, Yarn, MR2 present after adding Knox
[ https://issues.apache.org/jira/browse/AMBARI-24212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24212: - Fix Version/s: (was: 2.7.0) 2.7.1 > Restart Indicators for Hdfs, Yarn, MR2 present after adding Knox > > > Key: AMBARI-24212 > URL: https://issues.apache.org/jira/browse/AMBARI-24212 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Priority: Major > Fix For: 2.7.1 > > > STR: > 1) Create hdfs and yarn Config Groups > 2) Override some hdfs-site and yarn-site configs > 3) Now add Knox > After adding knox, Hdfs, Yarn and MR2 have restart indicators but they should > not have them > On deleting knox, this issue was not reproduced > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24207) Python unit test failure on 2.7.6
[
https://issues.apache.org/jira/browse/AMBARI-24207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24207:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> Python unit test failure on 2.7.6
> -
>
> Key: AMBARI-24207
> URL: https://issues.apache.org/jira/browse/AMBARI-24207
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.7.1
>
>
> Python unit tests fail on Python 2.7.6, because
> [SSLContext|https://docs.python.org/2/library/ssl.html#ssl-contexts] was only
> added in 2.7.9.
> {noformat:title=https://builds.apache.org/job/Ambari-trunk-Commit/9543/consoleText}
> ERROR: test_ldap_sync_ssl (TestAmbariServer.TestAmbariServer)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestAmbariServer.py",
> line 7804, in test_ldap_sync_ssl
> sync_ldap(options)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/setupSecurity.py",
> line 405, in sync_ldap
> raise FatalException(1, err)
> FatalException: "Fatal exception: Sync event creation failed. Error details:
> 'module' object has no attribute 'SSLContext', exit code 1"
> ERROR: test_get_ssl_context (TestServerUtils.TestServerUtils)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/TestServerUtils.py",
> line 124, in test_get_ssl_context
> context = get_ssl_context(properties)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/main/python/ambari_server/serverUtils.py",
> line 274, in get_ssl_context
> context = ssl.SSLContext(protocol)
> AttributeError: 'module' object has no attribute 'SSLContext'
> {noformat}
> CC [~rlevas]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24120) cluster version is in invalid state
[
https://issues.apache.org/jira/browse/AMBARI-24120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538021#comment-16538021
]
Ishan Bhatt commented on AMBARI-24120:
--
Moving it out to 2.7.1
> cluster version is in invalid state
> ---
>
> Key: AMBARI-24120
> URL: https://issues.apache.org/jira/browse/AMBARI-24120
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: amarnath reddy pappu
>Priority: Major
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-06-15 at 9.40.16 AM.png
>
>
> Steps to reproduce:
> 1. Make sure you have stable cluster
> 2. add a new host - and make sure it fails with the installation at the end
> step.
> 3. Now go to "stack and versions" screen - you will see the cluster in kind
> of messed up state.
> Usually customers may not see the 3rd step right after adding the host and if
> they observe after few days then it gives very wrong impression that cluster
> is it messed up state though it is not.
> Output for host_version
> {noformat}
> select * from host_version where host_id in ( 301, 551) and repo_version_id =
> 102
> '901','102','301','CURRENT'
> '1052','102','551','OUT_OF_SYNC'
> 2nd row is problematic one.
> {noformat}
> Workaround:
> Remove the host and add it again and make sure installation is not failing
> or
> change the status of host_version to 'CURRENT'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24047) Infra Solr: Changed GC options are lost after Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-24047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24047: - Fix Version/s: (was: 2.7.0) 2.7.1 > Infra Solr: Changed GC options are lost after Ambari upgrade > > > Key: AMBARI-24047 > URL: https://issues.apache.org/jira/browse/AMBARI-24047 > Project: Ambari > Issue Type: Bug > Components: infra, solr >Affects Versions: 2.7.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.1 > > > at infra-solr env, people can define GC settings, as we are upgrading the > whole content during upgrade with on-ambari-update update=true, that can > override an already defined settings. > it would be good if we could include 2 new properties for infra-solr-env > config type (extend gc_log_opts and gc_tune), and put the already defined gc > settings there during upgrade. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24120) cluster version is in invalid state
[
https://issues.apache.org/jira/browse/AMBARI-24120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24120:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> cluster version is in invalid state
> ---
>
> Key: AMBARI-24120
> URL: https://issues.apache.org/jira/browse/AMBARI-24120
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: amarnath reddy pappu
>Priority: Major
> Fix For: 2.7.1
>
> Attachments: Screen Shot 2018-06-15 at 9.40.16 AM.png
>
>
> Steps to reproduce:
> 1. Make sure you have stable cluster
> 2. add a new host - and make sure it fails with the installation at the end
> step.
> 3. Now go to "stack and versions" screen - you will see the cluster in kind
> of messed up state.
> Usually customers may not see the 3rd step right after adding the host and if
> they observe after few days then it gives very wrong impression that cluster
> is it messed up state though it is not.
> Output for host_version
> {noformat}
> select * from host_version where host_id in ( 301, 551) and repo_version_id =
> 102
> '901','102','301','CURRENT'
> '1052','102','551','OUT_OF_SYNC'
> 2nd row is problematic one.
> {noformat}
> Workaround:
> Remove the host and add it again and make sure installation is not failing
> or
> change the status of host_version to 'CURRENT'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24173) UI Deploy: Cannot deploy cluster with Config Groups
[
https://issues.apache.org/jira/browse/AMBARI-24173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Bhatt updated AMBARI-24173:
-
Fix Version/s: (was: 2.7.0)
2.7.1
> UI Deploy: Cannot deploy cluster with Config Groups
> ---
>
> Key: AMBARI-24173
> URL: https://issues.apache.org/jira/browse/AMBARI-24173
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> UI Deploy: Cannot deploy cluster with Config Groups
> STR:
> 1) Install cluster via UI
> 2) On Customize services page, create a Config Group and add some hosts to it
> 3) Click Deploy
>
> {code}
> 2018-06-22 23:46:28,174 ERROR [ambari-client-thread-505]
> AbstractResourceProvider:353 - Caught AmbariException when modifying a
> resource
> org.apache.ambari.server.AmbariException: Config group not found, clusterName
> = cl1, groupId = 1529709098419
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateConfigGroups(ConfigGroupResourceProvider.java:683)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.access$300(ConfigGroupResourceProvider.java:76)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:351)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:348)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:346)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResources(ConfigGroupResourceProvider.java:348)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResourcesAuthorized(ConfigGroupResourceProvider.java:251)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.updateResources(AbstractAuthorizedResourceProvider.java:312)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.updateResources(ClusterControllerImpl.java:317)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.update(PersistenceManagerImpl.java:125)
> at
> org.apache.ambari.server.api.handlers.UpdateHandler.persist(UpdateHandler.java:46)
> 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.ConfigGroupService.updateConfigGroup(ConfigGroupService.java:186)
> 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.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> 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
[jira] [Commented] (AMBARI-24047) Infra Solr: Changed GC options are lost after Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-24047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538019#comment-16538019 ] Ishan Bhatt commented on AMBARI-24047: -- Moving it out to 2.7.1 > Infra Solr: Changed GC options are lost after Ambari upgrade > > > Key: AMBARI-24047 > URL: https://issues.apache.org/jira/browse/AMBARI-24047 > Project: Ambari > Issue Type: Bug > Components: infra, solr >Affects Versions: 2.7.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Fix For: 2.7.1 > > > at infra-solr env, people can define GC settings, as we are upgrading the > whole content during upgrade with on-ambari-update update=true, that can > override an already defined settings. > it would be good if we could include 2 new properties for infra-solr-env > config type (extend gc_log_opts and gc_tune), and put the already defined gc > settings there during upgrade. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23970) Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver fails to start because DN's are not up
[
https://issues.apache.org/jira/browse/AMBARI-23970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538018#comment-16538018
]
Ishan Bhatt commented on AMBARI-23970:
--
Moving it out to 2.7.1
> Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver
> fails to start because DN's are not up
>
>
> Key: AMBARI-23970
> URL: https://issues.apache.org/jira/browse/AMBARI-23970
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> Broken RCO in Add Namespace Wizards Restart Required Services, Hiveserver
> fails to start because DN's are not up
>
> {code}
> { "RemoteException": {"exception": "IOException", "javaClassName":
> "java.io.IOException", "message": "Failed to find datanode, suggest to
> check cluster health. excludeDatanodes=null" }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-24173) UI Deploy: Cannot deploy cluster with Config Groups
[
https://issues.apache.org/jira/browse/AMBARI-24173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538022#comment-16538022
]
Ishan Bhatt commented on AMBARI-24173:
--
Moving it out to 2.7.1
> UI Deploy: Cannot deploy cluster with Config Groups
> ---
>
> Key: AMBARI-24173
> URL: https://issues.apache.org/jira/browse/AMBARI-24173
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> UI Deploy: Cannot deploy cluster with Config Groups
> STR:
> 1) Install cluster via UI
> 2) On Customize services page, create a Config Group and add some hosts to it
> 3) Click Deploy
>
> {code}
> 2018-06-22 23:46:28,174 ERROR [ambari-client-thread-505]
> AbstractResourceProvider:353 - Caught AmbariException when modifying a
> resource
> org.apache.ambari.server.AmbariException: Config group not found, clusterName
> = cl1, groupId = 1529709098419
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateConfigGroups(ConfigGroupResourceProvider.java:683)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.access$300(ConfigGroupResourceProvider.java:76)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:351)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider$4.invoke(ConfigGroupResourceProvider.java:348)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.modifyResources(AbstractResourceProvider.java:346)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResources(ConfigGroupResourceProvider.java:348)
> at
> org.apache.ambari.server.controller.internal.ConfigGroupResourceProvider.updateResourcesAuthorized(ConfigGroupResourceProvider.java:251)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.updateResources(AbstractAuthorizedResourceProvider.java:312)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.updateResources(ClusterControllerImpl.java:317)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.update(PersistenceManagerImpl.java:125)
> at
> org.apache.ambari.server.api.handlers.UpdateHandler.persist(UpdateHandler.java:46)
> 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.ConfigGroupService.updateConfigGroup(ConfigGroupService.java:186)
> 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.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> 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
> c
[jira] [Commented] (AMBARI-23655) While adding HDFS Namespace from UI, Timeline service fails to start
[
https://issues.apache.org/jira/browse/AMBARI-23655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538015#comment-16538015
]
Ishan Bhatt commented on AMBARI-23655:
--
Moving it out to 2.7.1
> While adding HDFS Namespace from UI, Timeline service fails to start
>
>
> Key: AMBARI-23655
> URL: https://issues.apache.org/jira/browse/AMBARI-23655
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vivek Rathod
>Priority: Major
> Fix For: 2.7.1
>
>
> While adding HDFS Namespace from UI, Timeline service fails to start in the
> last step ("Restart All Services") because the active Namenode(from older
> namespace) is in Safe Mode
>
> It seems for restart all service operation we do not wait for namenode to
> leave safemode
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
