[jira] [Assigned] (AMBARI-22302) TEZ UI Tab in Hive View 2.0 is showing 'TEZ UI not available' after executing Query
[ https://issues.apache.org/jira/browse/AMBARI-22302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik reassigned AMBARI-22302: - Assignee: Akhil S Naik > TEZ UI Tab in Hive View 2.0 is showing 'TEZ UI not available' after > executing Query > > > Key: AMBARI-22302 > URL: https://issues.apache.org/jira/browse/AMBARI-22302 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Minor > Attachments: empty_dagId.png, hiveView.patch, screenshot > HiveView.png, screenshot tez_view.png, screenshot tezui_on_hive.png > > > *When I launch a job on Hive View 2.0 (via the Ambari Views) including a Tez > operation, I do have my results without any problem * > !https://issues.apache.org/jira/secure/attachment/12893881/screenshot%20HiveView.png! > *But when I click on the Tez UI tab on Hive View, I've got the "Tez UI not > available" *: > !https://issues.apache.org/jira/secure/attachment/12893882/screenshot%20tezui_on_hive.png! > *As you can see on Tez View (screenshot tez_view.png), the Hive query is > present. * > !https://issues.apache.org/jira/secure/attachment/12893883/screenshot%20tez_view.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22918) Decommission RegionServer fails when kerberos is enabled
[
https://issues.apache.org/jira/browse/AMBARI-22918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370852#comment-16370852
]
Toshihiro Suzuki commented on AMBARI-22918:
---
It looks like the patches were merged and this issue was resolved. Can anyone
please mark this Jira as Resolved and assign to me? Thanks.
> Decommission RegionServer fails when kerberos is enabled
>
>
> Key: AMBARI-22918
> URL: https://issues.apache.org/jira/browse/AMBARI-22918
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Toshihiro Suzuki
>Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> When kerberos is enabled, Decommission RegionServer fails with the following
> errors:
> stderr:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 114, in
> HbaseMaster().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 55, in decommission
> hbase_decommission(env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_decommission.py",
> line 84, in hbase_decommission
> logoutput=True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab
> hbase/mast...@example.com; /usr/hdp/current/hbase-master/bin/hbase --config
> /usr/hdp/current/hbase-master/conf
> -Djava.security.auth.login.config=/usr/hdp/current/hbase-master/conf/hbase_master_jaas.conf
> org.jruby.Main /usr/hdp/current/hbase-master/bin/draining_servers.rb add
> worker1' returned 1. Error: Could not find or load main class
> org.jruby.Main{code}
> stdout:
> {code:java}
> 2018-02-06 07:25:03,453 - Stack Feature Version Info: Cluster Stack=2.6,
> Cluster Current Version=2.6.2.0-205, Command Stack=None, Command
> Version=2.6.2.0-205 -> 2.6.2.0-205
> 2018-02-06 07:25:03,476 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2018-02-06 07:25:03,484 - checked_call['hostid'] {}
> 2018-02-06 07:25:03,490 - checked_call returned (0, '1aacc56c')
> 2018-02-06 07:25:03,502 -
> File['/usr/hdp/current/hbase-master/bin/draining_servers.rb'] {'content':
> StaticFile('draining_servers.rb'), 'mode': 0755}
> 2018-02-06 07:25:03,504 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab hbase/mast...@example.com;
> /usr/hdp/current/hbase-master/bin/hbase --config
> /usr/hdp/current/hbase-master/conf
> -Djava.security.auth.login.config=/usr/hdp/current/hbase-master/conf/hbase_master_jaas.conf
> org.jruby.Main /usr/hdp/current/hbase-master/bin/draining_servers.rb add
> worker1'] {'logoutput': True, 'user': 'hbase'}
> Error: Could not find or load main class org.jruby.Main
> Command failed after 1 tries{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23038) Alert filter with services having space is not working
Kishor Ramakrishnan created AMBARI-23038: Summary: Alert filter with services having space is not working Key: AMBARI-23038 URL: https://issues.apache.org/jira/browse/AMBARI-23038 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Kishor Ramakrishnan Fix For: 2.7.0 Alert filter with services having space is not working. STR: 1. Navigate to Alerts page 2. Try to filter using Service as filter key with services like "Ambari Infra"/"Log Search" 3. Alerts are not filtered. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23037) Admin user can delete own user from Users page
Kishor Ramakrishnan created AMBARI-23037: Summary: Admin user can delete own user from Users page Key: AMBARI-23037 URL: https://issues.apache.org/jira/browse/AMBARI-23037 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Kishor Ramakrishnan Fix For: 2.7.0 Attachments: Screen Shot 2018-02-08 at 9.40.50 PM.png Admin user can delete own user from Users page. STR: # Login to ambari UI as admin user # Navigate to Users page # Try to delete the same user (admin) from the users list The delete option is disabled in the individual user page, but not from the all Users page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22996) ViewInstanceResourceProviderTest, ViewPermissionResourceProviderTest, and ViewURLResourceProviderTest fail unexpectedly
[ https://issues.apache.org/jira/browse/AMBARI-22996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370734#comment-16370734 ] Hudson commented on AMBARI-22996: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8759 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8759/]) [AMBARI-22996] ViewInstanceResourceProviderTest, (6454655+adoroszlai: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=78df59c1380d770dbc053063b0368ce89b8907ea]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewInstanceResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewURLResourceProviderTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewPermissionResourceProviderTest.java > ViewInstanceResourceProviderTest, ViewPermissionResourceProviderTest, and > ViewURLResourceProviderTest fail unexpectedly > > > Key: AMBARI-22996 > URL: https://issues.apache.org/jira/browse/AMBARI-22996 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk > Environment: Ubuntu, 16.04 LTS >Reporter: Wing Lam >Priority: Minor > Labels: pull-request-available > Fix For: trunk > > Time Spent: 1h > Remaining Estimate: 0h > > The tests in ViewInstanceResourceProviderTest, > ViewPermissionResourceProviderTest, and ViewURLResourceProviderTest rely on a > ViewRegistry that is set up in a static initializer block. However, if the > another test sets the ViewRegistry after the class is initialized, then the > test class will use the wrong ViewRegistry and fail, despite there being no > changes in code. This can be fixed by setting the ViewRegistry in the @Before > method in each of the three test classes as shown in the pull request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23029) Not able to delete livy component from a host
[ https://issues.apache.org/jira/browse/AMBARI-23029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370653#comment-16370653 ] Hudson commented on AMBARI-23029: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8758 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8758/]) AMBARI-23029 Not able to delete livy component from a host. (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=dec0cb49ea5468c983bca5d78d64769ae619e5f3]) * (edit) ambari-web/app/views/common/configs/config_versions_control_view.js * (edit) ambari-web/app/templates/main/host/details/addDeleteComponentPopup.hbs * (edit) ambari-web/app/styles/common.less * (edit) ambari-web/test/views/common/configs/config_versions_control_view_test.js * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/styles/bootstrap_overrides.less > Not able to delete livy component from a host > - > > Key: AMBARI-23029 > URL: https://issues.apache.org/jira/browse/AMBARI-23029 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: datanode-delete.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > I am not able to delete livy(only one instance of livy is present on the > cluster) from a host. > After stopping livy, when I try to delete, its showing below message : > "WARNING! Delete the last Livy for Spark2 Server component in the cluster? > Deleting the last component in the cluster could result in permanent loss of > service data." (Attaching the screenshot) > But there's not way to enable 'Confirm Delete' button. > Note : In earlier versions of ambari there used to be a check box and user > has to check it to enable delete button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23008) AMS: SUM downsampling function works incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-23008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370651#comment-16370651 ] Hudson commented on AMBARI-23008: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8758 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8758/]) [AMBARI-23008] AMS: SUM downsampling function works incorrectly. (avijayan: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=f0e05da42df55151ec745ecf445dc7ee941c0379]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricReadHelper.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/DownSamplerTest.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/DownSamplerUtils.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/PhoenixTransactSQL.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TopNDownSampler.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/AbstractTimelineAggregator.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/EventMetricDownSampler.java > AMS: SUM downsampling function works incorrectly > > > Key: AMBARI-23008 > URL: https://issues.apache.org/jira/browse/AMBARI-23008 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > AMS, by default does not sum up across time dimension. However, there are > certain metric cases where this is useful. > *Aggregation Scenario - How it should work* > Let's say in Host H1 - the metric values for > 'topology.streamline-2-test-clone.3-KAFKA.TASK1.--emit-count.STREAM1' are > 1,1,0,1,2 in time 10:01 to 10:05 (1 minute values) respectively > And, in Host H2 - the metric values for the same metric are 1,0,2,2,1 > respectively > AMS will first aggregate across hosts. 'Sum' aggregation -> 2,1,2,3,3 (10:01 > - 10:05) and then across time (downsampling) for larger windows. In time > based downsampling, the 'sum' value will be 11 (2 + 1 + 2 + 3 + 3) at 10:05. > Also, such metrics should not be interpolated, because the injected values > will cause wrong summed up values. > * Work* > A new custom downsampler was added which implements the above logic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23028) Fix AMBARI_INFRA_SOLR dependency for the stack code
[ https://issues.apache.org/jira/browse/AMBARI-23028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370654#comment-16370654 ] Hudson commented on AMBARI-23028: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8758 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8758/]) AMBARI-23028. Fix AMBARI_INFRA_SOLR dependency for the stack code. (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=a4b3d658ffbef0bbb80212d6080e12c601d98596]) * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/RANGER/0.6.0/metainfo.xml * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/metainfo.xml * (edit) ambari-server/src/test/python/stacks/2.4/AMBARI_INFRA/test_infra_solr.py > Fix AMBARI_INFRA_SOLR dependency for the stack code > --- > > Key: AMBARI-23028 > URL: https://issues.apache.org/jira/browse/AMBARI-23028 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >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-23034) Create HDP 2.6 to HDP 3.0 express upgrade pack
[ https://issues.apache.org/jira/browse/AMBARI-23034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370652#comment-16370652 ] Hudson commented on AMBARI-23034: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8758 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8758/]) AMBARI-23034 Create HDP 2.6 to HDP 3.0 express upgrade pack (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=18e4da86ee35f8a57d819a39ab06b07beedd1649]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml * (add) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-3.0.xml AMBARI-23034. Create HDP 2.6 to HDP 3.0 express upgrade pack - add (dlysnichenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=003102bf65e9bf835bda88c862580832e1704748]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-3.0.xml > Create HDP 2.6 to HDP 3.0 express upgrade pack > -- > > Key: AMBARI-23034 > URL: https://issues.apache.org/jira/browse/AMBARI-23034 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Labels: pull-request-available > Time Spent: 1h 10m > Remaining Estimate: 0h > > Create HDP 2.6. to HDP 3.0 express upgrade pack -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23027) Add backup/copy znode command for infra-solr-client
[ https://issues.apache.org/jira/browse/AMBARI-23027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23027: Labels: pull-request-available (was: ) > Add backup/copy znode command for infra-solr-client > --- > > Key: AMBARI-23027 > URL: https://issues.apache.org/jira/browse/AMBARI-23027 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23035) HDFS Balancer via Ambari fails when FIPS mode is activated on the OS
[ https://issues.apache.org/jira/browse/AMBARI-23035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-23035: -- Status: Patch Available (was: Open) > HDFS Balancer via Ambari fails when FIPS mode is activated on the OS > > > Key: AMBARI-23035 > URL: https://issues.apache.org/jira/browse/AMBARI-23035 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > This is similar issue as reported on AMBARI-22417, but for service checks. > The original issue of ambari check is resolved. But the same issue is seen > when running the HDFS balancer via Ambari. > *Solution* > MD5 is disabled on the OS, Code needs to be updated to use SHA > This is required when FIPS mode is enabled on the RHEL OS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23036) Create Lifecycle changes for Upgrade Packs
Nate Cole created AMBARI-23036:
--
Summary: Create Lifecycle changes for Upgrade Packs
Key: AMBARI-23036
URL: https://issues.apache.org/jira/browse/AMBARI-23036
Project: Ambari
Issue Type: Task
Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
Fix For: 3.0.0
In Upgrade Packs, abstract the {{}} element further and wrap them with a
{{}} element.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23007) Create Upgrade Plan menu item and popup
[ https://issues.apache.org/jira/browse/AMBARI-23007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23007: Labels: pull-request-available (was: ) > Create Upgrade Plan menu item and popup > --- > > Key: AMBARI-23007 > URL: https://issues.apache.org/jira/browse/AMBARI-23007 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Jason Golieb >Assignee: Jason Golieb >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Implements the action for the Create Upgrade Plan menu item on the Service > Groups admin screen and the popup that appears when the menu item is clicked. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23030) Remove light icon in user edit if user role is admin
[ https://issues.apache.org/jira/browse/AMBARI-23030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370593#comment-16370593 ] Hudson commented on AMBARI-23030: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #8757 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8757/]) AMBARI-23030. Remove light icon in user edit if user role is admin (aantonenko: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=7eb382862ae8c0f3f32dd8d1139029889ed43bbc]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/userManagement/userEdit.html > Remove light icon in user edit if user role is admin > > > Key: AMBARI-23030 > URL: https://issues.apache.org/jira/browse/AMBARI-23030 > Project: Ambari > Issue Type: Task > Components: ambari-admin >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] [Updated] (AMBARI-23035) HDFS Balancer via Ambari fails when FIPS mode is activated on the OS
[ https://issues.apache.org/jira/browse/AMBARI-23035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23035: Labels: pull-request-available (was: ) > HDFS Balancer via Ambari fails when FIPS mode is activated on the OS > > > Key: AMBARI-23035 > URL: https://issues.apache.org/jira/browse/AMBARI-23035 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: Robert Levas >Assignee: Robert Levas >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > > This is similar issue as reported on AMBARI-22417, but for service checks. > The original issue of ambari check is resolved. But the same issue is seen > when running the HDFS balancer via Ambari. > *Solution* > MD5 is disabled on the OS, Code needs to be updated to use SHA > This is required when FIPS mode is enabled on the RHEL OS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23028) Fix AMBARI_INFRA_SOLR dependency for the stack code
[ https://issues.apache.org/jira/browse/AMBARI-23028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23028. --- Resolution: Fixed > Fix AMBARI_INFRA_SOLR dependency for the stack code > --- > > Key: AMBARI-23028 > URL: https://issues.apache.org/jira/browse/AMBARI-23028 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >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] [Comment Edited] (AMBARI-18528) Need a way to escape config values that contain $
[
https://issues.apache.org/jira/browse/AMBARI-18528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603928#comment-15603928
]
Ted Yu edited comment on AMBARI-18528 at 2/20/18 6:35 PM:
--
Escaping the dollar sign automatically is a desirable solution.
was (Author: yuzhih...@gmail.com):
Escaping the dollar sign automatically is a desirable solution .
> Need a way to escape config values that contain $
> -
>
> Key: AMBARI-18528
> URL: https://issues.apache.org/jira/browse/AMBARI-18528
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
> Labels: zookeeper
>
> We tried specifying auth_to_local in zookeeper env input box:
> {code}
> export SERVER_JVMFLAGS="$SERVER_JVMFLAGS
> -Dzookeeper.security.auth_to_local=RULE:[2:$1@$0](hb...@c.net)s/.*/hbase/
> -Djava.security.auth.login.config={{zk_server_jaas_file}}"
> {code}
> However, when zookeeper quorum starts, the rule got interrupted with
> zkServer.sh
> We should add the capability of specifying auth_to_local in Ambari UI
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-20945) Configuration parameter 'hdfs-site' was not found error when AMS rootdir is on s3a
[
https://issues.apache.org/jira/browse/AMBARI-20945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-20945:
Description:
When I specify AMS rootdir to be on s3a and restart AMS, I would get the
following error:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 86, in
AmsCollector().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 315, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 817, in restart
self.start(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 48, in start
self.configure(env, action = 'start') # for security
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 118, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 43, in configure
hbase('master', action)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py",
line 222, in hbase
dfs_type=params.dfs_type
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 119, in run_action
provider = provider_class(resource)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 503, in __init__
self.assert_parameter_is_set('hdfs_site')
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 575, in assert_parameter_is_set
if not getattr(self.resource, parameter_name):
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not found in
configurations dictionary!")
resource_management.core.exceptions.Fail: Configuration parameter 'hdfs-site'
was not found in configurations dictionary!
{code}
was:
When I specify AMS rootdir to be on s3a and restart AMS, I would get the
following error:
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 86, in
AmsCollector().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 315, in execute
method(env)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 817, in restart
self.start(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 48, in start
self.configure(env, action = 'start') # for security
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 118, in locking_configure
original_configure(obj, *args, **kw)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_collector.py",
line 43, in configure
hbase('master', action)
File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
line 89, in thunk
return fn(*args, **kwargs)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/hbase.py",
line 222, in hbase
dfs_type=params.dfs_type
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 155, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 160, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 119, in run_action
provider = provider_class(resource)
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 503, in __init__
self.assert_parameter_is_set('hdfs_site')
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
line 575, in assert_parameter_is_set
if not getattr(self.resource, parameter_name):
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/config_dictionary.py",
line 73, in __getattr__
raise Fail("Configuration parameter '" + self.name + "' was not
[jira] [Updated] (AMBARI-22621) Ensure value for hbase.coprocessor.abortonerror is true
[ https://issues.apache.org/jira/browse/AMBARI-22621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-22621: Description: In the coprocessor refactor for hbase-2, Server#abort has been taken out of reach. We should ensure that value for hbase.coprocessor.abortonerror is true so that coprocessor can abort the server by throwing exception. See HBASE-19341 for related details. was: In the coprocessor refactor for hbase-2, Server#abort has been taken out of reach. We should ensure that value for hbase.coprocessor.abortonerror is true so that coprocessor can abort the server by throwing exception. See HBASE-19341 for related details. > Ensure value for hbase.coprocessor.abortonerror is true > --- > > Key: AMBARI-22621 > URL: https://issues.apache.org/jira/browse/AMBARI-22621 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu >Priority: Major > > In the coprocessor refactor for hbase-2, Server#abort has been taken out of > reach. > We should ensure that value for hbase.coprocessor.abortonerror is true so > that coprocessor can abort the server by throwing exception. > See HBASE-19341 for related details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22943) Wrong condition in FixCapacitySchedulerOrderingPolicy#execute()
[
https://issues.apache.org/jira/browse/AMBARI-22943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-22943:
Description:
{code}
} else if (!orderingPolicyValue.equals(UTILIZATION) ||
!orderingPolicyValue.equals(PRIORITY_UTILIZATION)) {
{code}
Regardless of the value for orderingPolicyValue, the condition would be true.
was:
{code}
} else if (!orderingPolicyValue.equals(UTILIZATION) ||
!orderingPolicyValue.equals(PRIORITY_UTILIZATION)) {
{code}
Regardless of the value for orderingPolicyValue, the condition would be true.
> Wrong condition in FixCapacitySchedulerOrderingPolicy#execute()
> ---
>
> Key: AMBARI-22943
> URL: https://issues.apache.org/jira/browse/AMBARI-22943
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
>
> {code}
> } else if (!orderingPolicyValue.equals(UTILIZATION) ||
> !orderingPolicyValue.equals(PRIORITY_UTILIZATION)) {
> {code}
> Regardless of the value for orderingPolicyValue, the condition would be true.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23029) Not able to delete livy component from a host
[ https://issues.apache.org/jira/browse/AMBARI-23029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach resolved AMBARI-23029. --- Resolution: Fixed > Not able to delete livy component from a host > - > > Key: AMBARI-23029 > URL: https://issues.apache.org/jira/browse/AMBARI-23029 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: datanode-delete.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > I am not able to delete livy(only one instance of livy is present on the > cluster) from a host. > After stopping livy, when I try to delete, its showing below message : > "WARNING! Delete the last Livy for Spark2 Server component in the cluster? > Deleting the last component in the cluster could result in permanent loss of > service data." (Attaching the screenshot) > But there's not way to enable 'Confirm Delete' button. > Note : In earlier versions of ambari there used to be a check box and user > has to check it to enable delete button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23029) Not able to delete livy component from a host
[ https://issues.apache.org/jira/browse/AMBARI-23029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370372#comment-16370372 ] Andrii Tkach commented on AMBARI-23029: --- committed to trunk > Not able to delete livy component from a host > - > > Key: AMBARI-23029 > URL: https://issues.apache.org/jira/browse/AMBARI-23029 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: datanode-delete.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > I am not able to delete livy(only one instance of livy is present on the > cluster) from a host. > After stopping livy, when I try to delete, its showing below message : > "WARNING! Delete the last Livy for Spark2 Server component in the cluster? > Deleting the last component in the cluster could result in permanent loss of > service data." (Attaching the screenshot) > But there's not way to enable 'Confirm Delete' button. > Note : In earlier versions of ambari there used to be a check box and user > has to check it to enable delete button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-20038) LogFeeder Simulator Enhancements for 3000-node cluster testing
[ https://issues.apache.org/jira/browse/AMBARI-20038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370361#comment-16370361 ] Hudson commented on AMBARI-20038: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #617 (See [https://builds.apache.org/job/Ambari-branch-2.6/617/]) [AMBARI-20038] Removing debug statements (avijayan: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=983c5c405816bc4be858dc9a764e51bdab729105]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java > LogFeeder Simulator Enhancements for 3000-node cluster testing > --- > > Key: AMBARI-20038 > URL: https://issues.apache.org/jira/browse/AMBARI-20038 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 2.5.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Major > Fix For: 2.5.0 > > Attachments: AMBARI-20038.patch > > > The number of simulators set via logfeeder.simulate.input_number should work > as imitating separate hosts, having separate queues pushing data from to the > solr. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23008) AMS: SUM downsampling function works incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-23008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370360#comment-16370360 ] Hudson commented on AMBARI-23008: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #617 (See [https://builds.apache.org/job/Ambari-branch-2.6/617/]) [AMBARI-23008] AMS: SUM downsampling function works incorrectly. (avijayan: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=32aded2d102eb7ce7c64718a7029e67fda52f165]) * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/DownSamplerUtils.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricClusterAggregatorSecond.java * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/AbstractTimelineAggregator.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/DownSamplerTest.java * (add) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/EventMetricDownSampler.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/PhoenixTransactSQL.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TimelineMetricConfiguration.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TopNDownSampler.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/PhoenixHBaseAccessor.java * (edit) ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/aggregators/TimelineMetricReadHelper.java > AMS: SUM downsampling function works incorrectly > > > Key: AMBARI-23008 > URL: https://issues.apache.org/jira/browse/AMBARI-23008 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > AMS, by default does not sum up across time dimension. However, there are > certain metric cases where this is useful. > *Aggregation Scenario - How it should work* > Let's say in Host H1 - the metric values for > 'topology.streamline-2-test-clone.3-KAFKA.TASK1.--emit-count.STREAM1' are > 1,1,0,1,2 in time 10:01 to 10:05 (1 minute values) respectively > And, in Host H2 - the metric values for the same metric are 1,0,2,2,1 > respectively > AMS will first aggregate across hosts. 'Sum' aggregation -> 2,1,2,3,3 (10:01 > - 10:05) and then across time (downsampling) for larger windows. In time > based downsampling, the 'sum' value will be 11 (2 + 1 + 2 + 3 + 3) at 10:05. > Also, such metrics should not be interpolated, because the injected values > will cause wrong summed up values. > * Work* > A new custom downsampler was added which implements the above logic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23008) AMS: SUM downsampling function works incorrectly
[ https://issues.apache.org/jira/browse/AMBARI-23008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-23008. Resolution: Fixed PR merged to trunk and branch-2.6 > AMS: SUM downsampling function works incorrectly > > > Key: AMBARI-23008 > URL: https://issues.apache.org/jira/browse/AMBARI-23008 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Critical > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > AMS, by default does not sum up across time dimension. However, there are > certain metric cases where this is useful. > *Aggregation Scenario - How it should work* > Let's say in Host H1 - the metric values for > 'topology.streamline-2-test-clone.3-KAFKA.TASK1.--emit-count.STREAM1' are > 1,1,0,1,2 in time 10:01 to 10:05 (1 minute values) respectively > And, in Host H2 - the metric values for the same metric are 1,0,2,2,1 > respectively > AMS will first aggregate across hosts. 'Sum' aggregation -> 2,1,2,3,3 (10:01 > - 10:05) and then across time (downsampling) for larger windows. In time > based downsampling, the 'sum' value will be 11 (2 + 1 + 2 + 3 + 3) at 10:05. > Also, such metrics should not be interpolated, because the injected values > will cause wrong summed up values. > * Work* > A new custom downsampler was added which implements the above logic. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23035) HDFS Balancer via Ambari fails when FIPS mode is activated on the OS
Robert Levas created AMBARI-23035: - Summary: HDFS Balancer via Ambari fails when FIPS mode is activated on the OS Key: AMBARI-23035 URL: https://issues.apache.org/jira/browse/AMBARI-23035 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.1 Reporter: Robert Levas Assignee: Robert Levas Fix For: 2.6.2 This is similar issue as reported on AMBARI-22417, but for service checks. The original issue of ambari check is resolved. But the same issue is seen when running the HDFS balancer via Ambari. *Solution* MD5 is disabled on the OS, Code needs to be updated to use SHA This is required when FIPS mode is enabled on the RHEL OS -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23030) Remove light icon in user edit if user role is admin
[ https://issues.apache.org/jira/browse/AMBARI-23030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23030: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Remove light icon in user edit if user role is admin > > > Key: AMBARI-23030 > URL: https://issues.apache.org/jira/browse/AMBARI-23030 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23034) Create HDP 2.6 to HDP 3.0 express upgrade pack
[ https://issues.apache.org/jira/browse/AMBARI-23034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23034: Labels: pull-request-available (was: ) > Create HDP 2.6 to HDP 3.0 express upgrade pack > -- > > Key: AMBARI-23034 > URL: https://issues.apache.org/jira/browse/AMBARI-23034 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Labels: pull-request-available > > Create HDP 2.6. to HDP 3.0 express upgrade pack -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23034) Create HDP 2.6 to HDP 3.0 express upgrade pack
Dmitry Lysnichenko created AMBARI-23034: --- Summary: Create HDP 2.6 to HDP 3.0 express upgrade pack Key: AMBARI-23034 URL: https://issues.apache.org/jira/browse/AMBARI-23034 Project: Ambari Issue Type: Task Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Create HDP 2.6. to HDP 3.0 express upgrade pack -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23034) Create HDP 2.6 to HDP 3.0 express upgrade pack
[ https://issues.apache.org/jira/browse/AMBARI-23034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-23034: Component/s: ambari-server > Create HDP 2.6 to HDP 3.0 express upgrade pack > -- > > Key: AMBARI-23034 > URL: https://issues.apache.org/jira/browse/AMBARI-23034 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > > Create HDP 2.6. to HDP 3.0 express upgrade pack -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22987) Fix Ambari doc site to fix errors from https://whimsy.apache.org/site/project/ambari
[ https://issues.apache.org/jira/browse/AMBARI-22987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated AMBARI-22987: -- Resolution: Fixed Status: Resolved (was: Patch Available) Resolved. Need to publish the doc site - opened a new Jira - https://issues.apache.org/jira/browse/AMBARI-23033 > Fix Ambari doc site to fix errors from > https://whimsy.apache.org/site/project/ambari > > > Key: AMBARI-22987 > URL: https://issues.apache.org/jira/browse/AMBARI-22987 > Project: Ambari > Issue Type: Bug > Components: site >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Labels: pull-request-available > Attachments: > 0001-AMBARI-22987-fixes-to-errors-shown-from-whimsy.apach.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Fix errors shown in https://whimsy.apache.org/site/project/ambari -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23033) Publish ambari website based on the doc updates in the ambari repo.
Selvamohan Neethiraj created AMBARI-23033: - Summary: Publish ambari website based on the doc updates in the ambari repo. Key: AMBARI-23033 URL: https://issues.apache.org/jira/browse/AMBARI-23033 Project: Ambari Issue Type: Task Components: site Reporter: Selvamohan Neethiraj As the issue - https://issues.apache.org/jira/browse/AMBARI-22987 is patched/resolved, we need to generate the ambari site content and needs to be uploaded. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23031) View name is not displayed in ambari-views page
[ https://issues.apache.org/jira/browse/AMBARI-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23031: Labels: pull-request-available (was: ) > View name is not displayed in ambari-views page > --- > > Key: AMBARI-23031 > URL: https://issues.apache.org/jira/browse/AMBARI-23031 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-02-09 at 11.44.53 AM.png > > > *Steps to reporduce:-* > 1. go to ambari-views tab > 2. create as many view you can create > 3. see the views dashboard > Screenshot: [^Screen Shot 2018-02-09 at 11.44.53 AM.png] > The Name field is blank > the Name Only get populated add a "Short URL". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22947) All Container-executor.cfg properties should be managed by ambari ui
[ https://issues.apache.org/jira/browse/AMBARI-22947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22947: Labels: pull-request-available (was: ) > All Container-executor.cfg properties should be managed by ambari ui > > > Key: AMBARI-22947 > URL: https://issues.apache.org/jira/browse/AMBARI-22947 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Yesha Vora >Assignee: Sandor Molnar >Priority: Major > Labels: pull-request-available > > Currently, only few properties from Container-executor.cfg can be managed via > ambari UI. > Container-executor.cfg should be handled similar to yarn-env.sh in ambari. > This way ambari ui can manage all config properties for Container-executor.cfg -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23032) Support for Blueprint exports for MPack-based clusters
Balázs Bence Sári created AMBARI-23032: -- Summary: Support for Blueprint exports for MPack-based clusters Key: AMBARI-23032 URL: https://issues.apache.org/jira/browse/AMBARI-23032 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 3.0.0 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: 3.0.0 The Blueprints export feature needs to be updated to support a deployment based on multiple MPacks. The Blueprint export processor will need to integrate with the MPack set of APIs in order to properly export a cluster created with the new mechanism. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23031) View name is not displayed in ambari-views page
[ https://issues.apache.org/jira/browse/AMBARI-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23031: -- Description: *Steps to reporduce:-* 1. go to ambari-views tab 2. create as many view you can create 3. see the views dashboard *Screensshot:- !Screen Shot 2018-02-09 at 11.44.53 AM.png!* [^Screen Shot 2018-02-09 at 11.44.53 AM.png] The Name field is blank the Name Only get populated add a "Short URL". was: *Steps to reporduce:-* 1. go to ambari-views tab 2. create as many view you can create 3. see the views dashboard *Screensshot:-* !Screen Shot 2018-02-09 at 11.44.53 AM.png|thumbnail! The Name field is blank the Name Only get populated add a "Short URL". > View name is not displayed in ambari-views page > --- > > Key: AMBARI-23031 > URL: https://issues.apache.org/jira/browse/AMBARI-23031 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-02-09 at 11.44.53 AM.png > > > *Steps to reporduce:-* > 1. go to ambari-views tab > 2. create as many view you can create > 3. see the views dashboard > *Screensshot:- !Screen Shot 2018-02-09 at 11.44.53 AM.png!* [^Screen Shot > 2018-02-09 at 11.44.53 AM.png] > The Name field is blank > the Name Only get populated add a "Short URL". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23031) View name is not displayed in ambari-views page
[ https://issues.apache.org/jira/browse/AMBARI-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23031: -- Description: *Steps to reporduce:-* 1. go to ambari-views tab 2. create as many view you can create 3. see the views dashboard Screenshot: [^Screen Shot 2018-02-09 at 11.44.53 AM.png] The Name field is blank the Name Only get populated add a "Short URL". was: *Steps to reporduce:-* 1. go to ambari-views tab 2. create as many view you can create 3. see the views dashboard *Screensshot:- !Screen Shot 2018-02-09 at 11.44.53 AM.png!* [^Screen Shot 2018-02-09 at 11.44.53 AM.png] The Name field is blank the Name Only get populated add a "Short URL". > View name is not displayed in ambari-views page > --- > > Key: AMBARI-23031 > URL: https://issues.apache.org/jira/browse/AMBARI-23031 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-02-09 at 11.44.53 AM.png > > > *Steps to reporduce:-* > 1. go to ambari-views tab > 2. create as many view you can create > 3. see the views dashboard > Screenshot: [^Screen Shot 2018-02-09 at 11.44.53 AM.png] > The Name field is blank > the Name Only get populated add a "Short URL". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23031) View name is not displayed in ambari-views page
Andrii Tkach created AMBARI-23031: - Summary: View name is not displayed in ambari-views page Key: AMBARI-23031 URL: https://issues.apache.org/jira/browse/AMBARI-23031 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 Attachments: Screen Shot 2018-02-09 at 11.44.53 AM.png *Steps to reporduce:-* 1. go to ambari-views tab 2. create as many view you can create 3. see the views dashboard *Screensshot:-* !Screen Shot 2018-02-09 at 11.44.53 AM.png|thumbnail! The Name field is blank the Name Only get populated add a "Short URL". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23031) View name is not displayed in ambari-views page
[ https://issues.apache.org/jira/browse/AMBARI-23031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23031: -- Attachment: Screen Shot 2018-02-09 at 11.44.53 AM.png > View name is not displayed in ambari-views page > --- > > Key: AMBARI-23031 > URL: https://issues.apache.org/jira/browse/AMBARI-23031 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-02-09 at 11.44.53 AM.png > > > *Steps to reporduce:-* > 1. go to ambari-views tab > 2. create as many view you can create > 3. see the views dashboard > *Screensshot:-* !Screen Shot 2018-02-09 at 11.44.53 AM.png|thumbnail! > The Name field is blank > the Name Only get populated add a "Short URL". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23030) Remove light icon in user edit if user role is admin
[ https://issues.apache.org/jira/browse/AMBARI-23030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-23030: - Status: Patch Available (was: Open) > Remove light icon in user edit if user role is admin > > > Key: AMBARI-23030 > URL: https://issues.apache.org/jira/browse/AMBARI-23030 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23029) Not able to delete livy component from a host
[ https://issues.apache.org/jira/browse/AMBARI-23029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23029: Labels: pull-request-available (was: ) > Not able to delete livy component from a host > - > > Key: AMBARI-23029 > URL: https://issues.apache.org/jira/browse/AMBARI-23029 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: datanode-delete.png > > > I am not able to delete livy(only one instance of livy is present on the > cluster) from a host. > After stopping livy, when I try to delete, its showing below message : > "WARNING! Delete the last Livy for Spark2 Server component in the cluster? > Deleting the last component in the cluster could result in permanent loss of > service data." (Attaching the screenshot) > But there's not way to enable 'Confirm Delete' button. > Note : In earlier versions of ambari there used to be a check box and user > has to check it to enable delete button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23030) Remove light icon in user edit if user role is admin
[ https://issues.apache.org/jira/browse/AMBARI-23030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23030: Labels: pull-request-available (was: ) > Remove light icon in user edit if user role is admin > > > Key: AMBARI-23030 > URL: https://issues.apache.org/jira/browse/AMBARI-23030 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23030) Remove light icon in user edit if user role is admin
[ https://issues.apache.org/jira/browse/AMBARI-23030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-23030: Assignee: Antonenko Alexander > Remove light icon in user edit if user role is admin > > > Key: AMBARI-23030 > URL: https://issues.apache.org/jira/browse/AMBARI-23030 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23030) Remove light icon in user edit if user role is admin
Antonenko Alexander created AMBARI-23030: Summary: Remove light icon in user edit if user role is admin Key: AMBARI-23030 URL: https://issues.apache.org/jira/browse/AMBARI-23030 Project: Ambari Issue Type: Task Components: ambari-admin Affects Versions: 2.7.0 Reporter: Antonenko Alexander Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23029) Not able to delete livy component from a host
[ https://issues.apache.org/jira/browse/AMBARI-23029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23029: -- Attachment: datanode-delete.png > Not able to delete livy component from a host > - > > Key: AMBARI-23029 > URL: https://issues.apache.org/jira/browse/AMBARI-23029 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.7.0 > > Attachments: datanode-delete.png > > > I am not able to delete livy(only one instance of livy is present on the > cluster) from a host. > After stopping livy, when I try to delete, its showing below message : > "WARNING! Delete the last Livy for Spark2 Server component in the cluster? > Deleting the last component in the cluster could result in permanent loss of > service data." (Attaching the screenshot) > But there's not way to enable 'Confirm Delete' button. > Note : In earlier versions of ambari there used to be a check box and user > has to check it to enable delete button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23029) Not able to delete livy component from a host
Andrii Tkach created AMBARI-23029: - Summary: Not able to delete livy component from a host Key: AMBARI-23029 URL: https://issues.apache.org/jira/browse/AMBARI-23029 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 I am not able to delete livy(only one instance of livy is present on the cluster) from a host. After stopping livy, when I try to delete, its showing below message : "WARNING! Delete the last Livy for Spark2 Server component in the cluster? Deleting the last component in the cluster could result in permanent loss of service data." (Attaching the screenshot) But there's not way to enable 'Confirm Delete' button. Note : In earlier versions of ambari there used to be a check box and user has to check it to enable delete button. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22962) Ambari Upgrade: LogSearch + Ambari Infra (2.6 -> 2.7)
[ https://issues.apache.org/jira/browse/AMBARI-22962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369995#comment-16369995 ] Hudson commented on AMBARI-22962: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8756 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8756/]) AMBARI-22962. ADDENDUM - UI and stack advistor changes for Ambari Infra (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=07287c5da0d246ace9243b1804afbdd5a33a5d7d]) * (edit) ambari-web/test/controllers/main/host/details_test.js * (edit) ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/service_advisor.py * (edit) ambari-web/test/controllers/wizard/step4_test.js * (delete) ambari-web/app/data/configs/services/ambari_infra_properties.js * (edit) ambari-web/app/data/configs/site_properties.js * (edit) ambari-web/test/controllers/main/admin/highAvailability/nameNode/step7_controller_test.js * (edit) ambari-web/app/controllers/wizard/step4_controller.js * (edit) ambari-server/src/test/python/stacks/2.5/common/test_stack_advisor.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/stack_advisor.py * (edit) ambari-web/app/controllers/main/admin/highAvailability/nameNode/step7_controller.js * (add) ambari-web/app/data/configs/services/ambari_infra_solr_properties.js * (edit) ambari-server/src/test/python/common-services/LOGSEARCH/test_service_advisor.py * (edit) ambari-web/app/models/stack_service.js > Ambari Upgrade: LogSearch + Ambari Infra (2.6 -> 2.7) > - > > Key: AMBARI-22962 > URL: https://issues.apache.org/jira/browse/AMBARI-22962 > Project: Ambari > Issue Type: Improvement > Components: ambari-infra, ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 1.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22897) Tez view button doesnt works in ambari hive views 1.5
[ https://issues.apache.org/jira/browse/AMBARI-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22897: -- Labels: patch-available (was: ) Fix Version/s: 3.0.0 Status: Patch Available (was: In Progress) > Tez view button doesnt works in ambari hive views 1.5 > - > > Key: AMBARI-22897 > URL: https://issues.apache.org/jira/browse/AMBARI-22897 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 > Environment: Ambari 2.6.1 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Labels: patch-available > Fix For: 3.0.0 > > Attachments: Screen Shot 2018-02-01 at 8.00.17 PM.png > > > *Issue :* > Login to ambari version 2.6.1 navigate to hive view 1.5 > When click on tez button or visualization or visual explain or settings > button > the page throws a script error and it become a blank page > *Root Cause :* > when click on the tez button, visualization or any other side button , > the following error is thrown from ember : > Assertion Failed: You attempted to render into 'index' but it was not found > attached the image error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22897) Tez view button doesnt works in ambari hive views 1.5
[ https://issues.apache.org/jira/browse/AMBARI-22897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil S Naik updated AMBARI-22897: -- Summary: Tez view button doesnt works in ambari hive views 1.5 (was: Tez view button doesnt works in ambari views 1.5) > Tez view button doesnt works in ambari hive views 1.5 > - > > Key: AMBARI-22897 > URL: https://issues.apache.org/jira/browse/AMBARI-22897 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.6.1 > Environment: Ambari 2.6.1 >Reporter: Akhil S Naik >Assignee: Akhil S Naik >Priority: Major > Attachments: Screen Shot 2018-02-01 at 8.00.17 PM.png > > > *Issue :* > Login to ambari version 2.6.1 navigate to hive view 1.5 > When click on tez button or visualization or visual explain or settings > button > the page throws a script error and it become a blank page > *Root Cause :* > when click on the tez button, visualization or any other side button , > the following error is thrown from ember : > Assertion Failed: You attempted to render into 'index' but it was not found > attached the image error -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23017) [PERF] Deployment of PERF stack leads to Out of Sync
[ https://issues.apache.org/jira/browse/AMBARI-23017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369965#comment-16369965 ] Hudson commented on AMBARI-23017: - ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #8755 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8755/]) AMBARI-23017. [PERF] Deployment of PERF stack leads to Out of Sync (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=83c0e67dff5e2a2f91c04ddb09a689df94c1f592]) * (edit) ambari-agent/src/test/python/ambari_agent/dummy_files/alert_definitions.json * (add) ambari-agent/src/test/python/ambari_agent/dummy_files/host_level_params.json * (add) ambari-agent/src/test/python/ambari_agent/dummy_files/configurations.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHDFS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEYARN/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEZOOKEEPER/metainfo.xml * (add) ambari-agent/src/test/python/ambari_agent/dummy_files/topology.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/AMBARI_METRICS/metainfo.xml * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/services/FAKEHBASE/metainfo.xml * (add) ambari-agent/src/test/python/ambari_agent/dummy_files/metadata.json * (edit) ambari-server/src/main/resources/stacks/PERF/1.0/properties/stack_packages.json > [PERF] Deployment of PERF stack leads to Out of Sync > > > Key: AMBARI-23017 > URL: https://issues.apache.org/jira/browse/AMBARI-23017 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-23017.patch > > Time Spent: 1h 40m > Remaining Estimate: 0h > > While deploying PERF stack, PERF 1.0 stack is not installed and shows up as > Out of sync -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23021) ServiceInfo: credential_store_supported attempts to overwrite maintenance_state
[
https://issues.apache.org/jira/browse/AMBARI-23021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila reassigned AMBARI-23021:
--
Assignee: Doroszlai, Attila
> ServiceInfo: credential_store_supported attempts to overwrite
> maintenance_state
> ---
>
> Key: AMBARI-23021
> URL: https://issues.apache.org/jira/browse/AMBARI-23021
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Minor
>
> Try to update {{credential_store_supported}} property of a service:
> {noformat}
> $ curl -X PUT -d @-
> "http://$AMBARI_SERVER:8080/api/v1/clusters/TEST/services/HDFS; < { "ServiceInfo": { "credential_store_supported": "true" } }
> EOF
> HTTP/1.1 400 Bad Request
> ...
> "message" : "java.lang.IllegalArgumentException: No enum constant
> org.apache.ambari.server.state.MaintenanceState.true"
> {noformat}
> Expected response:
> {{IllegalArgumentException: Invalid arguments, cannot update
> credential_store_supported as it is set only via service definition.}}
> The response code is the same as expected due to a coincidence.
> The problem is setting the wrong property:
> {noformat}
> 414 o = properties.get(SERVICE_CREDENTIAL_STORE_SUPPORTED_PROPERTY_ID);
> 415 if (null != o) {
> 416 svcRequest.setMaintenanceState(o.toString());
> 417 }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23021) ServiceInfo: credential_store_supported attempts to overwrite maintenance_state
[
https://issues.apache.org/jira/browse/AMBARI-23021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-23021:
---
Summary: ServiceInfo: credential_store_supported attempts to overwrite
maintenance_state (was: ServiceInfo/credential_store_supported applied to
maintenance_state)
> ServiceInfo: credential_store_supported attempts to overwrite
> maintenance_state
> ---
>
> Key: AMBARI-23021
> URL: https://issues.apache.org/jira/browse/AMBARI-23021
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Doroszlai, Attila
>Priority: Minor
>
> Try to update {{credential_store_supported}} property of a service:
> {noformat}
> $ curl -X PUT -d @-
> "http://$AMBARI_SERVER:8080/api/v1/clusters/TEST/services/HDFS; < { "ServiceInfo": { "credential_store_supported": "true" } }
> EOF
> HTTP/1.1 400 Bad Request
> ...
> "message" : "java.lang.IllegalArgumentException: No enum constant
> org.apache.ambari.server.state.MaintenanceState.true"
> {noformat}
> Expected response:
> {{IllegalArgumentException: Invalid arguments, cannot update
> credential_store_supported as it is set only via service definition.}}
> The response code is the same as expected due to a coincidence.
> The problem is setting the wrong property:
> {noformat}
> 414 o = properties.get(SERVICE_CREDENTIAL_STORE_SUPPORTED_PROPERTY_ID);
> 415 if (null != o) {
> 416 svcRequest.setMaintenanceState(o.toString());
> 417 }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23028) Fix AMBARI_INFRA_SOLR dependency for the stack code
[ https://issues.apache.org/jira/browse/AMBARI-23028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23028: Labels: pull-request-available (was: ) > Fix AMBARI_INFRA_SOLR dependency for the stack code > --- > > Key: AMBARI-23028 > URL: https://issues.apache.org/jira/browse/AMBARI-23028 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23028) Fix AMBARI_INFRA_SOLR dependency for the stack code
[ https://issues.apache.org/jira/browse/AMBARI-23028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-23028: -- Summary: Fix AMBARI_INFRA_SOLR dependency for the stack code (was: Fix AMBARI_INFRA_SOLR dependency for the stack) > Fix AMBARI_INFRA_SOLR dependency for the stack code > --- > > Key: AMBARI-23028 > URL: https://issues.apache.org/jira/browse/AMBARI-23028 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23028) Fix AMBARI_INFRA_SOLR dependency for the stack
Olivér Szabó created AMBARI-23028: - Summary: Fix AMBARI_INFRA_SOLR dependency for the stack Key: AMBARI-23028 URL: https://issues.apache.org/jira/browse/AMBARI-23028 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
