[jira] [Commented] (AMBARI-20638) Edit notifications options are disabled for administrator user
[ https://issues.apache.org/jira/browse/AMBARI-20638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020697#comment-16020697 ] Yao Lei commented on AMBARI-20638: -- Hi,[~apa...@hortonworks.com] Have you ever found in Ambari 2.5 the edit/duplicate buttons are always grey but you can click them and open a popup? > Edit notifications options are disabled for administrator user > -- > > Key: AMBARI-20638 > URL: https://issues.apache.org/jira/browse/AMBARI-20638 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: amarnath reddy pappu >Priority: Minor > > Steps to reproduce the issue: > 1. Login as admin user , create new user called cadmin and make him the > administrator. > 2. create couple of SNMP notifications under the Alert tab and Logout from UI > 3. Now login as cadmin and go to Alerts / SNMP Notifications, Try to edit the > Notifications , buttons are disabled. > Workaround: Navigate to Manage Ambari screen and then come back and check - > now buttons are enabled to edit. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20904) WFM: Include an option to clear filters in workflow dashboard
[ https://issues.apache.org/jira/browse/AMBARI-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020635#comment-16020635 ] Hudson commented on AMBARI-20904: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7519 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7519/]) AMBARI-20904.WFM: Include an option to clear filters in workflow (venkatasairam.lanka: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=201677be8deec6e3d898126fbc23b2114be2fa4c]) * (edit) contrib/views/wfmanager/src/main/resources/ui/app/templates/components/search-create-new-bar.hbs * (edit) contrib/views/wfmanager/src/main/resources/ui/app/components/search-create-new-bar.js > WFM: Include an option to clear filters in workflow dashboard > - > > Key: AMBARI-20904 > URL: https://issues.apache.org/jira/browse/AMBARI-20904 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Labels: WFD, WFM > Fix For: trunk > > Attachments: AMBARI-20904-may14.patch, AMBARI-20904.patch, > AMBARI-20904-updated.patch, ClearFilters-1.jpg, ClearFilters.jpg > > > Currently the filters can be cleared only manually by removing the contents, > having a button to clear the filters on one click would be helpful. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20904) WFM: Include an option to clear filters in workflow dashboard
[ https://issues.apache.org/jira/browse/AMBARI-20904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020625#comment-16020625 ] venkat commented on AMBARI-20904: - Committed to trunk. > WFM: Include an option to clear filters in workflow dashboard > - > > Key: AMBARI-20904 > URL: https://issues.apache.org/jira/browse/AMBARI-20904 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Labels: WFD, WFM > Fix For: trunk > > Attachments: AMBARI-20904-may14.patch, AMBARI-20904.patch, > AMBARI-20904-updated.patch, ClearFilters-1.jpg, ClearFilters.jpg > > > Currently the filters can be cleared only manually by removing the contents, > having a button to clear the filters on one click would be helpful. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21082) Ambari 3.0: Outstanding wizard issues
[ https://issues.apache.org/jira/browse/AMBARI-21082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020610#comment-16020610 ] Hudson commented on AMBARI-21082: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7518 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7518/]) AMBARI-21082 - Ambari 3.0: Outstanding wizard issues (rzang) (rzang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9415478dca03caf7f55ba21e8f00d954dc117757]) * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/templates/wizard/step4.hbs * (edit) ambari-web/app/views/wizard/step4_view.js > Ambari 3.0: Outstanding wizard issues > - > > Key: AMBARI-21082 > URL: https://issues.apache.org/jira/browse/AMBARI-21082 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 3.0.0 > > Attachments: AMBARI-21082.patch > > > On Ambari 3.0.0, the following are issues related to wizard: > The step number indicator is not center-aligned. Each step number is > positioned inside of a circle, and should always be centered in the circle. > This issue happened when you do command +/- to resize browser window view. > Install wizard step 4, should be able to select the service on clicking > anywhere within the row. Currently you can select the service ONLY clicking > on the checkbox. This is a regression from 2.5 > In install wizard, page footer was in wrong position. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21082) Ambari 3.0: Outstanding wizard issues
[ https://issues.apache.org/jira/browse/AMBARI-21082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21082: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk 9415478dca03caf7f55ba21e8f00d954dc117757 > Ambari 3.0: Outstanding wizard issues > - > > Key: AMBARI-21082 > URL: https://issues.apache.org/jira/browse/AMBARI-21082 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 3.0.0 > > Attachments: AMBARI-21082.patch > > > On Ambari 3.0.0, the following are issues related to wizard: > The step number indicator is not center-aligned. Each step number is > positioned inside of a circle, and should always be centered in the circle. > This issue happened when you do command +/- to resize browser window view. > Install wizard step 4, should be able to select the service on clicking > anywhere within the row. Currently you can select the service ONLY clicking > on the checkbox. This is a regression from 2.5 > In install wizard, page footer was in wrong position. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21096) Provide additional logging for config audit log
[
https://issues.apache.org/jira/browse/AMBARI-21096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21096:
-
Status: Patch Available (was: Open)
> Provide additional logging for config audit log
>
>
> Key: AMBARI-21096
> URL: https://issues.apache.org/jira/browse/AMBARI-21096
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: trunk, 2.5.2, 2.4.4
>
> Attachments: AMBARI-21096.branch-2.5.patch, AMBARI-21096.trunk.patch
>
>
> Improve logging of ambari-config-changes.log to include names, timestamps,
> and versions.
> Current log is of the form,
> {noformat}
> 2017-05-12 22:14:45,541 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-log4j' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-logsearch-conf' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-env' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1'
> # Changed default config
> 2017-05-12 22:18:06,277 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='2'
> 2017-05-12 22:18:06,278 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1494627510038'
> # Changed config in Custom_ZK_05
> 2017-05-12 22:22:48,957 INFO - User admin is creating new configuration
> group Custom_ZK_05 for tag ZOOKEEPER in cluster c1
> 2017-05-12 22:23:25,050 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='3'
> 2017-05-12 22:23:25,050 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1494627828482'
> {noformat}
> Will add the Note field, config group name (not just the id), config type,
> and perhaps number of hosts affected.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21096) Provide additional logging for config audit log
[
https://issues.apache.org/jira/browse/AMBARI-21096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21096:
-
Fix Version/s: 2.4.4
2.5.2
> Provide additional logging for config audit log
>
>
> Key: AMBARI-21096
> URL: https://issues.apache.org/jira/browse/AMBARI-21096
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: trunk, 2.5.2, 2.4.4
>
> Attachments: AMBARI-21096.branch-2.5.patch, AMBARI-21096.trunk.patch
>
>
> Improve logging of ambari-config-changes.log to include names, timestamps,
> and versions.
> Current log is of the form,
> {noformat}
> 2017-05-12 22:14:45,541 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-log4j' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-logsearch-conf' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-env' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1'
> # Changed default config
> 2017-05-12 22:18:06,277 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='2'
> 2017-05-12 22:18:06,278 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1494627510038'
> # Changed config in Custom_ZK_05
> 2017-05-12 22:22:48,957 INFO - User admin is creating new configuration
> group Custom_ZK_05 for tag ZOOKEEPER in cluster c1
> 2017-05-12 22:23:25,050 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='3'
> 2017-05-12 22:23:25,050 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1494627828482'
> {noformat}
> Will add the Note field, config group name (not just the id), config type,
> and perhaps number of hosts affected.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21096) Provide additional logging for config audit log
[
https://issues.apache.org/jira/browse/AMBARI-21096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21096:
-
Attachment: AMBARI-21096.trunk.patch
> Provide additional logging for config audit log
>
>
> Key: AMBARI-21096
> URL: https://issues.apache.org/jira/browse/AMBARI-21096
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: trunk
>
> Attachments: AMBARI-21096.branch-2.5.patch, AMBARI-21096.trunk.patch
>
>
> Improve logging of ambari-config-changes.log to include names, timestamps,
> and versions.
> Current log is of the form,
> {noformat}
> 2017-05-12 22:14:45,541 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-log4j' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-logsearch-conf' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-env' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1'
> # Changed default config
> 2017-05-12 22:18:06,277 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='2'
> 2017-05-12 22:18:06,278 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1494627510038'
> # Changed config in Custom_ZK_05
> 2017-05-12 22:22:48,957 INFO - User admin is creating new configuration
> group Custom_ZK_05 for tag ZOOKEEPER in cluster c1
> 2017-05-12 22:23:25,050 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='3'
> 2017-05-12 22:23:25,050 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1494627828482'
> {noformat}
> Will add the Note field, config group name (not just the id), config type,
> and perhaps number of hosts affected.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21096) Provide additional logging for config audit log
Alejandro Fernandez created AMBARI-21096:
Summary: Provide additional logging for config audit log
Key: AMBARI-21096
URL: https://issues.apache.org/jira/browse/AMBARI-21096
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Alejandro Fernandez
Assignee: Alejandro Fernandez
Fix For: trunk
Improve logging of ambari-config-changes.log to include names, timestamps, and
versions.
Current log is of the form,
{noformat}
2017-05-12 22:14:45,541 INFO - Cluster 'c1' changed by: 'admin';
service_name='ZOOKEEPER' config_group='Default' config_group_id='-1' version='1'
2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
type='zookeeper-log4j' tag='version1'
2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
type='zookeeper-logsearch-conf' tag='version1'
2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
type='zookeeper-env' tag='version1'
2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
type='zoo.cfg' tag='version1'
# Changed default config
2017-05-12 22:18:06,277 INFO - Cluster 'c1' changed by: 'admin';
service_name='ZOOKEEPER' config_group='Default' config_group_id='-1' version='2'
2017-05-12 22:18:06,278 INFO - cluster 'c1' changed by: 'admin';
type='zoo.cfg' tag='version1494627510038'
# Changed config in Custom_ZK_05
2017-05-12 22:22:48,957 INFO - User admin is creating new configuration group
Custom_ZK_05 for tag ZOOKEEPER in cluster c1
2017-05-12 22:23:25,050 INFO - Cluster 'c1' changed by: 'admin';
service_name='ZOOKEEPER' config_group='Default' config_group_id='-1' version='3'
2017-05-12 22:23:25,050 INFO - cluster 'c1' changed by: 'admin';
type='zoo.cfg' tag='version1494627828482'
{noformat}
Will add the Note field, config group name (not just the id), config type, and
perhaps number of hosts affected.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21096) Provide additional logging for config audit log
[
https://issues.apache.org/jira/browse/AMBARI-21096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-21096:
-
Attachment: AMBARI-21096.branch-2.5.patch
> Provide additional logging for config audit log
>
>
> Key: AMBARI-21096
> URL: https://issues.apache.org/jira/browse/AMBARI-21096
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
> Fix For: trunk
>
> Attachments: AMBARI-21096.branch-2.5.patch
>
>
> Improve logging of ambari-config-changes.log to include names, timestamps,
> and versions.
> Current log is of the form,
> {noformat}
> 2017-05-12 22:14:45,541 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-log4j' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-logsearch-conf' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zookeeper-env' tag='version1'
> 2017-05-12 22:14:45,562 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1'
> # Changed default config
> 2017-05-12 22:18:06,277 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='2'
> 2017-05-12 22:18:06,278 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1494627510038'
> # Changed config in Custom_ZK_05
> 2017-05-12 22:22:48,957 INFO - User admin is creating new configuration
> group Custom_ZK_05 for tag ZOOKEEPER in cluster c1
> 2017-05-12 22:23:25,050 INFO - Cluster 'c1' changed by: 'admin';
> service_name='ZOOKEEPER' config_group='Default' config_group_id='-1'
> version='3'
> 2017-05-12 22:23:25,050 INFO - cluster 'c1' changed by: 'admin';
> type='zoo.cfg' tag='version1494627828482'
> {noformat}
> Will add the Note field, config group name (not just the id), config type,
> and perhaps number of hosts affected.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21017) Misc tab at Customize Services Page has 2 'Livy User';No helper popup to identify if its Livy/Livy2
[ https://issues.apache.org/jira/browse/AMBARI-21017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020428#comment-16020428 ] Bikas Saha commented on AMBARI-21017: - Sure! > Misc tab at Customize Services Page has 2 'Livy User';No helper popup to > identify if its Livy/Livy2 > --- > > Key: AMBARI-21017 > URL: https://issues.apache.org/jira/browse/AMBARI-21017 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Dhanya Balasundaran >Assignee: Bikas Saha > Fix For: 2.5.2 > > > There are 2 Livy User in Misc tab of CustomizeServicesPage - one is for Livy2 > but there is no way to identify thats for Livy2. There is no helper > text/popup for the textboxes as well. > Either the labels should be different or there should be helper popup like > Livy group (which shows livy_group and livy2_group) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21095) Enable opening views in a new tab
[ https://issues.apache.org/jira/browse/AMBARI-21095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-21095: -- Priority: Minor (was: Major) > Enable opening views in a new tab > - > > Key: AMBARI-21095 > URL: https://issues.apache.org/jira/browse/AMBARI-21095 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-web >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj >Priority: Minor > Fix For: trunk > > Attachments: AMBARI-21095.patch > > > Enable views to be opened in a new tab instead of being opened in the same > tab, this would help in going between the different tabs to look for > information or for config updates in the services. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21095) Enable opening views in a new tab
[ https://issues.apache.org/jira/browse/AMBARI-21095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-21095: -- Attachment: AMBARI-21095.patch > Enable opening views in a new tab > - > > Key: AMBARI-21095 > URL: https://issues.apache.org/jira/browse/AMBARI-21095 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-web >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-21095.patch > > > Enable views to be opened in a new tab instead of being opened in the same > tab, this would help in going between the different tabs to look for > information or for config updates in the services. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21095) Enable opening views in a new tab
[ https://issues.apache.org/jira/browse/AMBARI-21095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-21095: -- Status: Patch Available (was: Open) > Enable opening views in a new tab > - > > Key: AMBARI-21095 > URL: https://issues.apache.org/jira/browse/AMBARI-21095 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-web >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-21095.patch > > > Enable views to be opened in a new tab instead of being opened in the same > tab, this would help in going between the different tabs to look for > information or for config updates in the services. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21095) Enable opening views in a new tab
Anita Gnanamalar Jebaraj created AMBARI-21095: - Summary: Enable opening views in a new tab Key: AMBARI-21095 URL: https://issues.apache.org/jira/browse/AMBARI-21095 Project: Ambari Issue Type: Bug Components: ambari-admin, ambari-web Affects Versions: trunk Reporter: Anita Gnanamalar Jebaraj Assignee: Anita Gnanamalar Jebaraj Fix For: trunk Enable views to be opened in a new tab instead of being opened in the same tab, this would help in going between the different tabs to look for information or for config updates in the services. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back
[ https://issues.apache.org/jira/browse/AMBARI-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21094: --- Fix Version/s: trunk > Customize services shows inconsistent config-groups after clicking on Back > -- > > Key: AMBARI-21094 > URL: https://issues.apache.org/jira/browse/AMBARI-21094 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21094.patch > > > Steps to reproduce: > 1. Go to Customize Services screen > 2. Create a Custom HostGroup > 3. Click Back button > 4. Click Next Button > 5. See that Custom Hostgroup still exists, but all the data including > assigned hosts is erased. > Ambari typically erases all the changes when clicked on Back button, because > the Custom HostGroup is not deleted but data related to it is deleted by > Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back
[ https://issues.apache.org/jira/browse/AMBARI-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21094: --- Attachment: AMBARI-21094.patch > Customize services shows inconsistent config-groups after clicking on Back > -- > > Key: AMBARI-21094 > URL: https://issues.apache.org/jira/browse/AMBARI-21094 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-21094.patch > > > Steps to reproduce: > 1. Go to Customize Services screen > 2. Create a Custom HostGroup > 3. Click Back button > 4. Click Next Button > 5. See that Custom Hostgroup still exists, but all the data including > assigned hosts is erased. > Ambari typically erases all the changes when clicked on Back button, because > the Custom HostGroup is not deleted but data related to it is deleted by > Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back
[ https://issues.apache.org/jira/browse/AMBARI-21094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-21094: --- Status: Patch Available (was: In Progress) > Customize services shows inconsistent config-groups after clicking on Back > -- > > Key: AMBARI-21094 > URL: https://issues.apache.org/jira/browse/AMBARI-21094 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Attachments: AMBARI-21094.patch > > > Steps to reproduce: > 1. Go to Customize Services screen > 2. Create a Custom HostGroup > 3. Click Back button > 4. Click Next Button > 5. See that Custom Hostgroup still exists, but all the data including > assigned hosts is erased. > Ambari typically erases all the changes when clicked on Back button, because > the Custom HostGroup is not deleted but data related to it is deleted by > Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back
Amruta Borkar created AMBARI-21094: -- Summary: Customize services shows inconsistent config-groups after clicking on Back Key: AMBARI-21094 URL: https://issues.apache.org/jira/browse/AMBARI-21094 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Amruta Borkar Assignee: Amruta Borkar Steps to reproduce: 1. Go to Customize Services screen 2. Create a Custom HostGroup 3. Click Back button 4. Click Next Button 5. See that Custom Hostgroup still exists, but all the data including assigned hosts is erased. Ambari typically erases all the changes when clicked on Back button, because the Custom HostGroup is not deleted but data related to it is deleted by Ambari cluster state goes in inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21033) Log Search use POJOs for input configuration
[ https://issues.apache.org/jira/browse/AMBARI-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020139#comment-16020139 ] Hudson commented on AMBARI-21033: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7517 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7517/]) AMBARI-21033 ADDENDUM - Log Search use POJOs for input configuration (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0626b789ba477c494dc5a260b2bca61e3d906690]) * (edit) ambari-logsearch/ambari-logsearch-config-api/src/test/java/org/apache/ambari/logsearch/config/api/LogSearchConfigFactoryTest.java > Log Search use POJOs for input configuration > > > Key: AMBARI-21033 > URL: https://issues.apache.org/jira/browse/AMBARI-21033 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21033.patch > > > Instead of parsing the input configuration jsons in logfeeder the > configuration api should return POJOs with the input and filter descriptions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21092) HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during EU (missing space)
[
https://issues.apache.org/jira/browse/AMBARI-21092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020034#comment-16020034
]
Alejandro Fernandez commented on AMBARI-21092:
--
+1 for [^AMBARI-21092.01.patch]
> HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during
> EU (missing space)
>
>
> Key: AMBARI-21092
> URL: https://issues.apache.org/jira/browse/AMBARI-21092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.1
>Reporter: Vivek Sharma
>Assignee: Siddharth Seth
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.1
>
> Attachments: AMBARI-21092.01.patch
>
>
> STR
> 1. Deploy HDP-2.5 cluster with HSI enabled and Ambari-2.4.2.0
> 2. Upgrade Ambari to 2.5.1.0-140
> 3. Start EU to HDP-2.6.1.0-105
> Result
> Error during HSI start
> From yarn log
> {code}
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> Unrecognized VM option 'UseParallelGC-Xss512k'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Looks to be caused by https://issues.apache.org/jira/browse/AMBARI-20537
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21081) Upgrade to 2.5.1 from 2.5.0 adds cgroups related configs back to YARN and indicates restart required
[
https://issues.apache.org/jira/browse/AMBARI-21081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020011#comment-16020011
]
Hudson commented on AMBARI-21081:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7516 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7516/])
AMBARI-21081 : Upgrade to 2.5.1 from 2.5.0 adds cgroups related configs
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6c68321448099167748efc8981103934a617dc11])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/services/YARN/configuration/yarn-site.xml
> Upgrade to 2.5.1 from 2.5.0 adds cgroups related configs back to YARN and
> indicates restart required
>
>
> Key: AMBARI-21081
> URL: https://issues.apache.org/jira/browse/AMBARI-21081
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21081.patch, Screen Shot 2017-05-19 at 10.42.46
> PM.png
>
>
> Upgrading to 2.5.1 after a fresh install of HDP-2.6 using 2.5.0.3, adds
> cgroup configs and results in YARN restart required indicator.
>
> !Screen Shot 2017-05-19 at 10.42.46 PM.png|thumbnail!
> This is because https://issues.apache.org/jira/browse/AMBARI-19311 added the
> logic to remove these configs when cgroup is not enabled but as the config
> properties have {{}} they get auto added when
> Ambari is upgraded.
> I believe simply setting {{}} to
> {{}} will fix this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21081) Upgrade to 2.5.1 from 2.5.0 adds cgroups related configs back to YARN and indicates restart required
[
https://issues.apache.org/jira/browse/AMBARI-21081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020008#comment-16020008
]
Hudson commented on AMBARI-21081:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1547 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1547/])
AMBARI-21081 : Upgrade to 2.5.1 from 2.5.0 adds cgroups related configs
(avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=943ac6d33ecf0e4762a202dcc2df832a006c1c78])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.2/services/YARN/configuration/yarn-site.xml
> Upgrade to 2.5.1 from 2.5.0 adds cgroups related configs back to YARN and
> indicates restart required
>
>
> Key: AMBARI-21081
> URL: https://issues.apache.org/jira/browse/AMBARI-21081
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21081.patch, Screen Shot 2017-05-19 at 10.42.46
> PM.png
>
>
> Upgrading to 2.5.1 after a fresh install of HDP-2.6 using 2.5.0.3, adds
> cgroup configs and results in YARN restart required indicator.
>
> !Screen Shot 2017-05-19 at 10.42.46 PM.png|thumbnail!
> This is because https://issues.apache.org/jira/browse/AMBARI-19311 added the
> logic to remove these configs when cgroup is not enabled but as the config
> properties have {{}} they get auto added when
> Ambari is upgraded.
> I believe simply setting {{}} to
> {{}} will fix this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21033) Log Search use POJOs for input configuration
[
https://issues.apache.org/jira/browse/AMBARI-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019986#comment-16019986
]
Olivér Szabó commented on AMBARI-21033:
---
ADDENDUM committed to trunk:
{code:java}
commit 0626b789ba477c494dc5a260b2bca61e3d906690
Author: oleewere
Date: Mon May 22 20:31:16 2017 +0200
AMBARI-21033 ADDENDUM - Log Search use POJOs for input configuration
(oleewere)
{code}
> Log Search use POJOs for input configuration
>
>
> Key: AMBARI-21033
> URL: https://issues.apache.org/jira/browse/AMBARI-21033
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Miklos Gergely
>Assignee: Miklos Gergely
> Fix For: 3.0.0
>
> Attachments: AMBARI-21033.patch
>
>
> Instead of parsing the input configuration jsons in logfeeder the
> configuration api should return POJOs with the input and filter descriptions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21092) HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during EU (missing space)
[
https://issues.apache.org/jira/browse/AMBARI-21092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated AMBARI-21092:
Attachment: AMBARI-21092.01.patch
> HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during
> EU (missing space)
>
>
> Key: AMBARI-21092
> URL: https://issues.apache.org/jira/browse/AMBARI-21092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.1
>Reporter: Vivek Sharma
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.1
>
> Attachments: AMBARI-21092.01.patch
>
>
> STR
> 1. Deploy HDP-2.5 cluster with HSI enabled and Ambari-2.4.2.0
> 2. Upgrade Ambari to 2.5.1.0-140
> 3. Start EU to HDP-2.6.1.0-105
> Result
> Error during HSI start
> From yarn log
> {code}
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> Unrecognized VM option 'UseParallelGC-Xss512k'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Looks to be caused by https://issues.apache.org/jira/browse/AMBARI-20537
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21092) HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during EU (missing space)
[
https://issues.apache.org/jira/browse/AMBARI-21092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated AMBARI-21092:
Status: Patch Available (was: Open)
> HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during
> EU (missing space)
>
>
> Key: AMBARI-21092
> URL: https://issues.apache.org/jira/browse/AMBARI-21092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.1
>Reporter: Vivek Sharma
>Assignee: Siddharth Seth
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.1
>
> Attachments: AMBARI-21092.01.patch
>
>
> STR
> 1. Deploy HDP-2.5 cluster with HSI enabled and Ambari-2.4.2.0
> 2. Upgrade Ambari to 2.5.1.0-140
> 3. Start EU to HDP-2.6.1.0-105
> Result
> Error during HSI start
> From yarn log
> {code}
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> Unrecognized VM option 'UseParallelGC-Xss512k'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Looks to be caused by https://issues.apache.org/jira/browse/AMBARI-20537
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (AMBARI-21092) HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during EU (missing space)
[
https://issues.apache.org/jira/browse/AMBARI-21092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth reassigned AMBARI-21092:
---
Assignee: Siddharth Seth
> HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during
> EU (missing space)
>
>
> Key: AMBARI-21092
> URL: https://issues.apache.org/jira/browse/AMBARI-21092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.1
>Reporter: Vivek Sharma
>Assignee: Siddharth Seth
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.1
>
> Attachments: AMBARI-21092.01.patch
>
>
> STR
> 1. Deploy HDP-2.5 cluster with HSI enabled and Ambari-2.4.2.0
> 2. Upgrade Ambari to 2.5.1.0-140
> 3. Start EU to HDP-2.6.1.0-105
> Result
> Error during HSI start
> From yarn log
> {code}
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> Unrecognized VM option 'UseParallelGC-Xss512k'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Looks to be caused by https://issues.apache.org/jira/browse/AMBARI-20537
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21092) HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during EU (missing space)
[
https://issues.apache.org/jira/browse/AMBARI-21092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019957#comment-16019957
]
Siddharth Seth commented on AMBARI-21092:
-
cc [~sumitmohanty], [~swapanshridhar]
> HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during
> EU (missing space)
>
>
> Key: AMBARI-21092
> URL: https://issues.apache.org/jira/browse/AMBARI-21092
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.5.1
>Reporter: Vivek Sharma
>Assignee: Siddharth Seth
>Priority: Critical
> Labels: express_upgrade
> Fix For: 2.5.1
>
> Attachments: AMBARI-21092.01.patch
>
>
> STR
> 1. Deploy HDP-2.5 cluster with HSI enabled and Ambari-2.4.2.0
> 2. Upgrade Ambari to 2.5.1.0-140
> 3. Start EU to HDP-2.6.1.0-105
> Result
> Error during HSI start
> From yarn log
> {code}
> org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> Unrecognized VM option 'UseParallelGC-Xss512k'
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {code}
> Looks to be caused by https://issues.apache.org/jira/browse/AMBARI-20537
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21081) Upgrade to 2.5.1 from 2.5.0 adds cgroups related configs back to YARN and indicates restart required
[
https://issues.apache.org/jira/browse/AMBARI-21081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aravindan Vijayan updated AMBARI-21081:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to branch-2.5 and trunk.
> Upgrade to 2.5.1 from 2.5.0 adds cgroups related configs back to YARN and
> indicates restart required
>
>
> Key: AMBARI-21081
> URL: https://issues.apache.org/jira/browse/AMBARI-21081
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21081.patch, Screen Shot 2017-05-19 at 10.42.46
> PM.png
>
>
> Upgrading to 2.5.1 after a fresh install of HDP-2.6 using 2.5.0.3, adds
> cgroup configs and results in YARN restart required indicator.
>
> !Screen Shot 2017-05-19 at 10.42.46 PM.png|thumbnail!
> This is because https://issues.apache.org/jira/browse/AMBARI-19311 added the
> logic to remove these configs when cgroup is not enabled but as the config
> properties have {{}} they get auto added when
> Ambari is upgraded.
> I believe simply setting {{}} to
> {{}} will fix this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21093) Nimbus fails to start due to AutoHDFS CNF on a cluster after Ambari is upgraded
[
https://issues.apache.org/jira/browse/AMBARI-21093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Sharma updated AMBARI-21093:
--
Labels: regression upgrade (was: upgrade)
> Nimbus fails to start due to AutoHDFS CNF on a cluster after Ambari is
> upgraded
> ---
>
> Key: AMBARI-21093
> URL: https://issues.apache.org/jira/browse/AMBARI-21093
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: Vivek Sharma
>Priority: Blocker
> Labels: regression, upgrade
> Fix For: 2.5.1
>
>
> *STR*
> # Deploy HDP2.6 cluster with Ambari-2.5.0 (secure cluster)
> # Upgrade Ambari to 2.5.1.0-140 and then 'Regenerate keytabs' from Ambari UI
> # Observe Nimbus state
> *Alternate STR*
> # Deploy HDP2.6 cluster with Ambari-2.5.0 (unsecure cluster)
> # Upgrade Ambari to 2.5.1.0-140 and then Express Upgrade to 2.6.1.0
> # Kerberize the cluster
> # Observe Nimbus state
> *Result*
> {code}
> 2017-05-22 12:12:57.768 o.a.s.d.nimbus main [ERROR] Error on initialization
> of server service-handler
> java.lang.RuntimeException: java.lang.ClassNotFoundException:
> org.apache.storm.hdfs.security.AutoHDFS
> at
> org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:188)
> ~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
> at org.apache.storm.daemon.nimbus$nimbus_data.invoke(nimbus.clj:223)
> ~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
> at
> org.apache.storm.daemon.nimbus$fn__9768$exec_fn__3648__auto9769.invoke(nimbus.clj:2416)
> ~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
> at clojure.lang.AFn.applyToHelper(AFn.java:156) ~[clojure-1.7.0.jar:?]
> at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
> at clojure.core$apply.invoke(core.clj:630) ~[clojure-1.7.0.jar:?]
> at
> org.apache.storm.daemon.nimbus$fn__9768$service_handler__9801.doInvoke(nimbus.clj:2413)
> ~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21093) Nimbus fails to start due to AutoHDFS CNF on a cluster after Ambari is upgraded
Vivek Sharma created AMBARI-21093:
-
Summary: Nimbus fails to start due to AutoHDFS CNF on a cluster
after Ambari is upgraded
Key: AMBARI-21093
URL: https://issues.apache.org/jira/browse/AMBARI-21093
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.1
Reporter: Vivek Sharma
Priority: Blocker
Fix For: 2.5.1
*STR*
# Deploy HDP2.6 cluster with Ambari-2.5.0 (secure cluster)
# Upgrade Ambari to 2.5.1.0-140 and then 'Regenerate keytabs' from Ambari UI
# Observe Nimbus state
*Alternate STR*
# Deploy HDP2.6 cluster with Ambari-2.5.0 (unsecure cluster)
# Upgrade Ambari to 2.5.1.0-140 and then Express Upgrade to 2.6.1.0
# Kerberize the cluster
# Observe Nimbus state
*Result*
{code}
2017-05-22 12:12:57.768 o.a.s.d.nimbus main [ERROR] Error on initialization of
server service-handler
java.lang.RuntimeException: java.lang.ClassNotFoundException:
org.apache.storm.hdfs.security.AutoHDFS
at
org.apache.storm.security.auth.AuthUtils.getNimbusAutoCredPlugins(AuthUtils.java:188)
~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
at org.apache.storm.daemon.nimbus$nimbus_data.invoke(nimbus.clj:223)
~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
at
org.apache.storm.daemon.nimbus$fn__9768$exec_fn__3648__auto9769.invoke(nimbus.clj:2416)
~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
at clojure.lang.AFn.applyToHelper(AFn.java:156) ~[clojure-1.7.0.jar:?]
at clojure.lang.AFn.applyTo(AFn.java:144) ~[clojure-1.7.0.jar:?]
at clojure.core$apply.invoke(core.clj:630) ~[clojure-1.7.0.jar:?]
at
org.apache.storm.daemon.nimbus$fn__9768$service_handler__9801.doInvoke(nimbus.clj:2413)
~[storm-core-1.1.0.2.6.0.3-8.jar:1.1.0.2.6.0.3-8]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21083) Create custom admin user during ambari server setup
[ https://issues.apache.org/jira/browse/AMBARI-21083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-21083: -- Attachment: (was: AMBARI-21083.patch) > Create custom admin user during ambari server setup > --- > > Key: AMBARI-21083 > URL: https://issues.apache.org/jira/browse/AMBARI-21083 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-21083.patch > > > Provide the ability to create custom admin user during ambari server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21083) Create custom admin user during ambari server setup
[ https://issues.apache.org/jira/browse/AMBARI-21083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-21083: -- Attachment: AMBARI-21083.patch > Create custom admin user during ambari server setup > --- > > Key: AMBARI-21083 > URL: https://issues.apache.org/jira/browse/AMBARI-21083 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-21083.patch > > > Provide the ability to create custom admin user during ambari server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21092) HSI start failed due to Unrecognized VM option 'UseParallelGC-Xss512k' during EU (missing space)
Vivek Sharma created AMBARI-21092:
-
Summary: HSI start failed due to Unrecognized VM option
'UseParallelGC-Xss512k' during EU (missing space)
Key: AMBARI-21092
URL: https://issues.apache.org/jira/browse/AMBARI-21092
Project: Ambari
Issue Type: Bug
Components: ambari-upgrade
Affects Versions: 2.5.1
Reporter: Vivek Sharma
Priority: Critical
Fix For: 2.5.1
STR
1. Deploy HDP-2.5 cluster with HSI enabled and Ambari-2.4.2.0
2. Upgrade Ambari to 2.5.1.0-140
3. Start EU to HDP-2.6.1.0-105
Result
Error during HSI start
>From yarn log
{code}
org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
Unrecognized VM option 'UseParallelGC-Xss512k'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
{code}
Looks to be caused by https://issues.apache.org/jira/browse/AMBARI-20537
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21091) HDP deploy from public repo failed
[ https://issues.apache.org/jira/browse/AMBARI-21091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019824#comment-16019824 ] Dmitry Lysnichenko commented on AMBARI-21091: - Committed fix "AMBARI-21091. HDP deploy from public repo failed. The left-off code breaks ambari-server setup (dlysnichenko)" To https://git-wip-us.apache.org/repos/asf/ambari.git 1e2ccbf086..11325b7c92 branch-feature-AMBARI-12556 -> branch-feature-AMBARI-12556 > HDP deploy from public repo failed > -- > > Key: AMBARI-21091 > URL: https://issues.apache.org/jira/browse/AMBARI-21091 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21091.patch > > > This left-off code breaks ambari-server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21090) Add Log Feeder input config to HDP 3.0 hooks too
[ https://issues.apache.org/jira/browse/AMBARI-21090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21090: Status: Patch Available (was: In Progress) > Add Log Feeder input config to HDP 3.0 hooks too > > > Key: AMBARI-21090 > URL: https://issues.apache.org/jira/browse/AMBARI-21090 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21090.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21083) Create custom admin user during ambari server setup
[ https://issues.apache.org/jira/browse/AMBARI-21083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-21083: -- Attachment: AMBARI-21083.patch > Create custom admin user during ambari server setup > --- > > Key: AMBARI-21083 > URL: https://issues.apache.org/jira/browse/AMBARI-21083 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-21083.patch > > > Provide the ability to create custom admin user during ambari server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21083) Create custom admin user during ambari server setup
[ https://issues.apache.org/jira/browse/AMBARI-21083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-21083: -- Attachment: (was: AMBARI-21083.patch) > Create custom admin user during ambari server setup > --- > > Key: AMBARI-21083 > URL: https://issues.apache.org/jira/browse/AMBARI-21083 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-21083.patch > > > Provide the ability to create custom admin user during ambari server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21069) Minimize config changes during ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019783#comment-16019783 ] Hudson commented on AMBARI-21069: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7515 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7515/]) AMBARI-21069. Minimize config changes during ambari upgrade. Add script (dlysnichenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=5ea441aa7b4080a7a1eb07a4a1e01a2aa8d0d92e]) * (add) dev-support/config-utils/diff_stack_properties.py > Minimize config changes during ambari upgrade > - > > Key: AMBARI-21069 > URL: https://issues.apache.org/jira/browse/AMBARI-21069 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21069.patch > > > I've implemented a python script that compares stack folders between > branches. It shows differences (between for example branch-2.5 and trunk) > that affect ambari upgrade (e.g. add-on-ambari-upgrade changes) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21091) HDP deploy from public repo failed
[ https://issues.apache.org/jira/browse/AMBARI-21091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21091: Fix Version/s: 3.0.0 > HDP deploy from public repo failed > -- > > Key: AMBARI-21091 > URL: https://issues.apache.org/jira/browse/AMBARI-21091 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21091.patch > > > This left-off code breaks ambari-server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21091) HDP deploy from public repo failed
[ https://issues.apache.org/jira/browse/AMBARI-21091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21091: Attachment: AMBARI-21091.patch > HDP deploy from public repo failed > -- > > Key: AMBARI-21091 > URL: https://issues.apache.org/jira/browse/AMBARI-21091 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21091.patch > > > This left-off code breaks ambari-server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21091) HDP deploy from public repo failed
[ https://issues.apache.org/jira/browse/AMBARI-21091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21091: Status: Patch Available (was: Open) > HDP deploy from public repo failed > -- > > Key: AMBARI-21091 > URL: https://issues.apache.org/jira/browse/AMBARI-21091 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > Attachments: AMBARI-21091.patch > > > This left-off code breaks ambari-server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21091) HDP deploy from public repo failed
[ https://issues.apache.org/jira/browse/AMBARI-21091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-21091: Component/s: ambari-server > HDP deploy from public repo failed > -- > > Key: AMBARI-21091 > URL: https://issues.apache.org/jira/browse/AMBARI-21091 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Critical > > This left-off code breaks ambari-server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21091) HDP deploy from public repo failed
Dmitry Lysnichenko created AMBARI-21091: --- Summary: HDP deploy from public repo failed Key: AMBARI-21091 URL: https://issues.apache.org/jira/browse/AMBARI-21091 Project: Ambari Issue Type: Bug Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Priority: Critical This left-off code breaks ambari-server setup -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21090) Add Log Feeder input config to HDP 3.0 hooks too
[ https://issues.apache.org/jira/browse/AMBARI-21090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21090: Attachment: AMBARI-21090.patch > Add Log Feeder input config to HDP 3.0 hooks too > > > Key: AMBARI-21090 > URL: https://issues.apache.org/jira/browse/AMBARI-21090 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21090.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21090) Add Log Feeder input config to HDP 3.0 hooks too
Miklos Gergely created AMBARI-21090: --- Summary: Add Log Feeder input config to HDP 3.0 hooks too Key: AMBARI-21090 URL: https://issues.apache.org/jira/browse/AMBARI-21090 Project: Ambari Issue Type: Bug Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21089) Host health tooltip is too far left off browser window/screen to be read
[ https://issues.apache.org/jira/browse/AMBARI-21089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Sekhon updated AMBARI-21089: - Attachment: Ambari pop up off left edge of screen.png > Host health tooltip is too far left off browser window/screen to be read > > > Key: AMBARI-21089 > URL: https://issues.apache.org/jira/browse/AMBARI-21089 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: HDP 2.5 >Reporter: Hari Sekhon >Priority: Minor > Attachments: Ambari pop up off left edge of screen.png > > > The Host health indicator tool tip on the Host page is displaying to far off > the left of the screen, I've seen this before at different clients. > See screenshot, you can't see if it's complaining about Ambari Agent or > SmartSense Agent being down as you can't read the first bit of the tool tip. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21089) Host health tooltip is too far left off browser window/screen to be read
Hari Sekhon created AMBARI-21089: Summary: Host health tooltip is too far left off browser window/screen to be read Key: AMBARI-21089 URL: https://issues.apache.org/jira/browse/AMBARI-21089 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Environment: HDP 2.5 Reporter: Hari Sekhon Priority: Minor The Host health indicator tool tip on the Host page is displaying to far off the left of the screen, I've seen this before at different clients. See screenshot, you can't see if it's complaining about Ambari Agent or SmartSense Agent being down as you can't read the first bit of the tool tip. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21088) HDP 3.0 TP - create service definition for Zeppelin with configs, kerberos, widgets, etc
[ https://issues.apache.org/jira/browse/AMBARI-21088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21088: --- Attachment: (was: AMBARI-21088.patch) > HDP 3.0 TP - create service definition for Zeppelin with configs, kerberos, > widgets, etc > > > Key: AMBARI-21088 > URL: https://issues.apache.org/jira/browse/AMBARI-21088 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21088.patch > > > create service definition for Zeppelin with configs, kerberos, widgets, etc -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21088) HDP 3.0 TP - create service definition for Zeppelin with configs, kerberos, widgets, etc
[ https://issues.apache.org/jira/browse/AMBARI-21088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21088: --- Attachment: AMBARI-21088.patch > HDP 3.0 TP - create service definition for Zeppelin with configs, kerberos, > widgets, etc > > > Key: AMBARI-21088 > URL: https://issues.apache.org/jira/browse/AMBARI-21088 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21088.patch > > > create service definition for Zeppelin with configs, kerberos, widgets, etc -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21088) HDP 3.0 TP - create service definition for Zeppelin with configs, kerberos, widgets, etc
[ https://issues.apache.org/jira/browse/AMBARI-21088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21088: --- Status: Patch Available (was: Open) > HDP 3.0 TP - create service definition for Zeppelin with configs, kerberos, > widgets, etc > > > Key: AMBARI-21088 > URL: https://issues.apache.org/jira/browse/AMBARI-21088 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21088.patch > > > create service definition for Zeppelin with configs, kerberos, widgets, etc -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21088) HDP 3.0 TP - create service definition for Zeppelin with configs, kerberos, widgets, etc
[ https://issues.apache.org/jira/browse/AMBARI-21088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21088: --- Attachment: AMBARI-21088.patch > HDP 3.0 TP - create service definition for Zeppelin with configs, kerberos, > widgets, etc > > > Key: AMBARI-21088 > URL: https://issues.apache.org/jira/browse/AMBARI-21088 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21088.patch > > > create service definition for Zeppelin with configs, kerberos, widgets, etc -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21088) HDP 3.0 TP - create service definition for Zeppelin with configs, kerberos, widgets, etc
Vitaly Brodetskyi created AMBARI-21088: -- Summary: HDP 3.0 TP - create service definition for Zeppelin with configs, kerberos, widgets, etc Key: AMBARI-21088 URL: https://issues.apache.org/jira/browse/AMBARI-21088 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 3.0.0 Attachments: AMBARI-21088.patch create service definition for Zeppelin with configs, kerberos, widgets, etc -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21081) Upgrade to 2.5.1 from 2.5.0 adds cgroups related configs back to YARN and indicates restart required
[
https://issues.apache.org/jira/browse/AMBARI-21081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019620#comment-16019620
]
Aravindan Vijayan commented on AMBARI-21081:
LGTM, +1
> Upgrade to 2.5.1 from 2.5.0 adds cgroups related configs back to YARN and
> indicates restart required
>
>
> Key: AMBARI-21081
> URL: https://issues.apache.org/jira/browse/AMBARI-21081
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.1
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-21081.patch, Screen Shot 2017-05-19 at 10.42.46
> PM.png
>
>
> Upgrading to 2.5.1 after a fresh install of HDP-2.6 using 2.5.0.3, adds
> cgroup configs and results in YARN restart required indicator.
>
> !Screen Shot 2017-05-19 at 10.42.46 PM.png|thumbnail!
> This is because https://issues.apache.org/jira/browse/AMBARI-19311 added the
> logic to remove these configs when cgroup is not enabled but as the config
> properties have {{}} they get auto added when
> Ambari is upgraded.
> I believe simply setting {{}} to
> {{}} will fix this issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21060) HDP 3.0 TP - create service definition for Oozie with configs, kerberos, widgets, etc
[ https://issues.apache.org/jira/browse/AMBARI-21060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21060: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > HDP 3.0 TP - create service definition for Oozie with configs, kerberos, > widgets, etc > - > > Key: AMBARI-21060 > URL: https://issues.apache.org/jira/browse/AMBARI-21060 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21060.patch > > > create service definition for Oozie with configs, kerberos, widgets, etc -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21067) Atlas config values not getting populated on BP cluster install with strategy : "NEVER_APPLY"
[
https://issues.apache.org/jira/browse/AMBARI-21067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019601#comment-16019601
]
Hudson commented on AMBARI-21067:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1546 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1546/])
AMBARI-21067. Atlas config values not getting populated on BP cluster
(smagyari:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fa9a0af4af6280814e36354b4b13d930239f5db7])
* (edit)
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml
> Atlas config values not getting populated on BP cluster install with strategy
> : "NEVER_APPLY"
> -
>
> Key: AMBARI-21067
> URL: https://issues.apache.org/jira/browse/AMBARI-21067
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 3.0.0, 2.5.2
>
> Attachments: AMBARI-21067.patch
>
>
> After cluster install, the following 5 ATLAS's 'application-properties'
> configs are empty:
> {code}
> atlas.graph.index.search.solr.zookeeper-url
> atlas.graph.storage.hostname
> atlas.kafka.bootstrap.servers
> atlas.kafka.zookeeper.connect
> atlas.audit.hbase.zookeeper.quorum
> {code}
> BlueprintConfigProcessor should configure these properties in case there's no
> stack advisor strategy set.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21060) HDP 3.0 TP - create service definition for Oozie with configs, kerberos, widgets, etc
[ https://issues.apache.org/jira/browse/AMBARI-21060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019600#comment-16019600 ] Hudson commented on AMBARI-21060: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7514 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7514/]) AMBARI-21060. HDP 3.0 TP - create service definition for Oozie with (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cdc18ecb9d06ef6810962fb3742d75781ff8e831]) * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/oozie_service.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/files/oozieSmoke2.sh * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/oozie.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/oozie_server.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/params_linux.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/configuration/oozie-site.xml * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/themes/theme.json * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/service_check.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/status_params.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/configuration/oozie-env.xml * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/templates/input.config-oozie.json.j2 * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/files/wrap_ooziedb.sh * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/params_windows.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/check_oozie_server_status.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/templates/zkmigrator_jaas.conf.j2 * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/metainfo.xml * (add) ambari-server/src/main/resources/stacks/HDP/3.0/services/OOZIE/metainfo.xml * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/role_command_order.json * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/alerts/alert_check_oozie_server.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/files/prepareOozieHdfsDirectories.sh * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/quicklinks/quicklinks.json * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/templates/adminusers.txt.j2 * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/templates/oozie.conf.j2 * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/params.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/kerberos.json * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/oozie_server_upgrade.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/scripts/oozie_client.py * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/package/templates/oozie-log4j.properties.j2 * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/alerts.json * (add) ambari-server/src/main/resources/common-services/OOZIE/4.2.0.3.0/configuration/oozie-log4j.xml > HDP 3.0 TP - create service definition for Oozie with configs, kerberos, > widgets, etc > - > > Key: AMBARI-21060 > URL: https://issues.apache.org/jira/browse/AMBARI-21060 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-21060.patch > > > create service definition for Oozie with configs, kerberos, widgets, etc -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21067) Atlas config values not getting populated on BP cluster install with strategy : "NEVER_APPLY"
[
https://issues.apache.org/jira/browse/AMBARI-21067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Magyari updated AMBARI-21067:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Atlas config values not getting populated on BP cluster install with strategy
> : "NEVER_APPLY"
> -
>
> Key: AMBARI-21067
> URL: https://issues.apache.org/jira/browse/AMBARI-21067
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 3.0.0, 2.5.2
>
> Attachments: AMBARI-21067.patch
>
>
> After cluster install, the following 5 ATLAS's 'application-properties'
> configs are empty:
> {code}
> atlas.graph.index.search.solr.zookeeper-url
> atlas.graph.storage.hostname
> atlas.kafka.bootstrap.servers
> atlas.kafka.zookeeper.connect
> atlas.audit.hbase.zookeeper.quorum
> {code}
> BlueprintConfigProcessor should configure these properties in case there's no
> stack advisor strategy set.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21067) Atlas config values not getting populated on BP cluster install with strategy : "NEVER_APPLY"
[
https://issues.apache.org/jira/browse/AMBARI-21067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019561#comment-16019561
]
Hudson commented on AMBARI-21067:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7513 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7513/])
AMBARI-21067. Atlas config values not getting populated on BP cluster
(smagyari:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=74972de559b21633288c03785dc672e792a172bb])
* (edit)
ambari-server/src/main/resources/common-services/ATLAS/0.7.0.2.5/configuration/application-properties.xml
> Atlas config values not getting populated on BP cluster install with strategy
> : "NEVER_APPLY"
> -
>
> Key: AMBARI-21067
> URL: https://issues.apache.org/jira/browse/AMBARI-21067
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
>Priority: Critical
> Fix For: 3.0.0, 2.5.2
>
> Attachments: AMBARI-21067.patch
>
>
> After cluster install, the following 5 ATLAS's 'application-properties'
> configs are empty:
> {code}
> atlas.graph.index.search.solr.zookeeper-url
> atlas.graph.storage.hostname
> atlas.kafka.bootstrap.servers
> atlas.kafka.zookeeper.connect
> atlas.audit.hbase.zookeeper.quorum
> {code}
> BlueprintConfigProcessor should configure these properties in case there's no
> stack advisor strategy set.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21087) Infra manger: Add static data folder servlet endpoint
Olivér Szabó created AMBARI-21087: - Summary: Infra manger: Add static data folder servlet endpoint Key: AMBARI-21087 URL: https://issues.apache.org/jira/browse/AMBARI-21087 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 3.0.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21033) Log Search use POJOs for input configuration
[ https://issues.apache.org/jira/browse/AMBARI-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019480#comment-16019480 ] Hudson commented on AMBARI-21033: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7512 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7512/]) AMBARI-21033 Log Search use POJOs for input configuration (mgergely) (mgergely: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fd4a7a46a2db9869dca28294660ca40e693504ea]) * (edit) ambari-logsearch/docker/test-config/logsearch/logsearch.properties * (edit) ambari-logsearch/ambari-logsearch-config-api/src/test/java/org/apache/ambari/logsearch/config/api/LogSearchConfigClass2.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/input/Input.java * (add) ambari-logsearch/ambari-logsearch-config-zookeeper/src/main/java/org/apache/ambari/logsearch/config/zookeeper/model/inputconfig/impl/FilterDescriptorImpl.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/output/Output.java * (add) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/InputConfig.java * (edit) ambari-logsearch/ambari-logsearch-config-zookeeper/src/main/java/org/apache/ambari/logsearch/config/zookeeper/LogSearchConfigZK.java * (edit) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/InputConfigMonitor.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/output/OutputLineFilterTest.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/FilterKeyValue.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerInput.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerPostMapValues.java * (add) ambari-logsearch/ambari-logsearch-config-zookeeper/src/main/java/org/apache/ambari/logsearch/config/zookeeper/model/inputconfig/impl/InputConfigImpl.java * (add) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/InputS3FileDescriptor.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/filter/FilterKeyValueTest.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/filter/FilterJSONTest.java * (add) ambari-logsearch/ambari-logsearch-config-zookeeper/src/main/java/org/apache/ambari/logsearch/config/zookeeper/model/inputconfig/impl/FilterAdapter.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerMapFieldCopy.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/FilterJSON.java * (add) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/InputFileBaseDescriptor.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerMapDate.java * (add) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/Conditions.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/test/java/org/apache/ambari/logfeeder/logconfig/LogConfigHandlerTest.java * (add) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/MapFieldDescriptor.java * (add) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/InputDescriptor.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/filter/Filter.java * (add) ambari-logsearch/ambari-logsearch-config-api/src/main/java/org/apache/ambari/logsearch/config/api/model/inputconfig/MapFieldValueDescriptor.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerInputFileBase.java * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/util/LogFeederUtil.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerInputConfig.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/model/common/LSServerMapField.java * (add) ambari-logsearch/ambari-logsearch-config-zookeeper/src/main/java/org/apache/ambari/logsearch/config/zookeeper/model/inputconfig/impl/InputConfigGson.java * (edit) ambari-logsearch/docker/test-config/logfeeder/logfeeder.properties * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/
[jira] [Updated] (AMBARI-21035) Integrate ClusterService resource with Swagger
[
https://issues.apache.org/jira/browse/AMBARI-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-21035:
---
Attachment: AMBARI-21035_addendum.patch
Minor tweaks:
* wrap request object in {{"Clusters"}}
* document {{"health_report"}} structure
[~bsari], can you please review?
> Integrate ClusterService resource with Swagger
> --
>
> Key: AMBARI-21035
> URL: https://issues.apache.org/jira/browse/AMBARI-21035
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-21035_addendum.patch, AMBARI-21035.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Reopened] (AMBARI-21035) Integrate ClusterService resource with Swagger
[ https://issues.apache.org/jira/browse/AMBARI-21035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila reopened AMBARI-21035: > Integrate ClusterService resource with Swagger > -- > > Key: AMBARI-21035 > URL: https://issues.apache.org/jira/browse/AMBARI-21035 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Doroszlai, Attila >Assignee: Doroszlai, Attila > Fix For: 3.0.0 > > Attachments: AMBARI-21035.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20812) Hive view 1.5 does not work in Safari8 and IE11
[
https://issues.apache.org/jira/browse/AMBARI-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha updated AMBARI-20812:
-
Status: Patch Available (was: Open)
> Hive view 1.5 does not work in Safari8 and IE11
> ---
>
> Key: AMBARI-20812
> URL: https://issues.apache.org/jira/browse/AMBARI-20812
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.2
>Reporter: amarnath reddy pappu
>Assignee: Pallav Kulshreshtha
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-20812-trunk.patch
>
>
> Steps to reproduce:
> 1. Launch Hive1.5 in IE11 browser - it loads Databases and Tables at left side
> 2. enter any query and submit.
> 3. Execute button would be disabled and there is no response back even if you
> wait 10-15mins.
> In console it fails with the below error.
> -
> [Error] TypeError: undefined is not a function (evaluating
> 'finalQuery.trim().endsWith(';')')
>
> run (vendor.js, line 10758)
>
> run (vendor.js, line 27192)
>
> handleRegisteredAction (vendor.js, line 29618)
>
> (anonymous function) (vendor.js, line 50042)
>
> dispatch (vendor.js, line 4872)
>
> handle (vendor.js, line 4540)
>
> This is happens in Safari8 browser as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21086) Hive view 2.0 does not work on IE 11 browser
[ https://issues.apache.org/jira/browse/AMBARI-21086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-21086: - Status: Patch Available (was: Open) > Hive view 2.0 does not work on IE 11 browser > > > Key: AMBARI-21086 > URL: https://issues.apache.org/jira/browse/AMBARI-21086 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.2 > > Attachments: AMBARI-21086-trunk.patch > > > It encounters JS errors and does not execute query execution. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20812) Hive view 1.5 does not work in Safari8 and IE11
[
https://issues.apache.org/jira/browse/AMBARI-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha updated AMBARI-20812:
-
Attachment: AMBARI-20812-trunk.patch
> Hive view 1.5 does not work in Safari8 and IE11
> ---
>
> Key: AMBARI-20812
> URL: https://issues.apache.org/jira/browse/AMBARI-20812
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.2
>Reporter: amarnath reddy pappu
>Assignee: Pallav Kulshreshtha
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-20812-trunk.patch
>
>
> Steps to reproduce:
> 1. Launch Hive1.5 in IE11 browser - it loads Databases and Tables at left side
> 2. enter any query and submit.
> 3. Execute button would be disabled and there is no response back even if you
> wait 10-15mins.
> In console it fails with the below error.
> -
> [Error] TypeError: undefined is not a function (evaluating
> 'finalQuery.trim().endsWith(';')')
>
> run (vendor.js, line 10758)
>
> run (vendor.js, line 27192)
>
> handleRegisteredAction (vendor.js, line 29618)
>
> (anonymous function) (vendor.js, line 50042)
>
> dispatch (vendor.js, line 4872)
>
> handle (vendor.js, line 4540)
>
> This is happens in Safari8 browser as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21086) Hive view 2.0 does not work on IE 11 browser
[ https://issues.apache.org/jira/browse/AMBARI-21086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pallav Kulshreshtha updated AMBARI-21086: - Attachment: AMBARI-21086-trunk.patch > Hive view 2.0 does not work on IE 11 browser > > > Key: AMBARI-21086 > URL: https://issues.apache.org/jira/browse/AMBARI-21086 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Pallav Kulshreshtha >Assignee: Pallav Kulshreshtha > Fix For: 2.5.2 > > Attachments: AMBARI-21086-trunk.patch > > > It encounters JS errors and does not execute query execution. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21085) Hive view 1.5 does not work in Safari8 and IE11
[
https://issues.apache.org/jira/browse/AMBARI-21085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha updated AMBARI-21085:
-
Attachment: AMBARI-20812-trunk.patch
> Hive view 1.5 does not work in Safari8 and IE11
> ---
>
> Key: AMBARI-21085
> URL: https://issues.apache.org/jira/browse/AMBARI-21085
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.2
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
>Priority: Critical
> Fix For: 2.5.2
>
> Attachments: AMBARI-20812-trunk.patch
>
>
> Steps to reproduce:
> 1. Launch Hive1.5 in IE11 browser - it loads Databases and Tables at left side
> 2. enter any query and submit.
> 3. Execute button would be disabled and there is no response back even if you
> wait 10-15mins.
> In console it fails with the below error.
> {noformat}
> -
> [Error] TypeError: undefined is not a function (evaluating
> 'finalQuery.trim().endsWith(';')')
>
> run (vendor.js, line 10758)
>
> run (vendor.js, line 27192)
>
> handleRegisteredAction (vendor.js, line 29618)
>
> (anonymous function) (vendor.js, line 50042)
>
> dispatch (vendor.js, line 4872)
>
> handle (vendor.js, line 4540)
>
> {noformat}
> This is happens in Safari8 browser as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21084) Files view on IE 11- On Concatenating files or downloading, the concatenated or downloaded file occupies the entire UI.
[ https://issues.apache.org/jira/browse/AMBARI-21084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-21084: Attachment: AMBARI-21084-trunk.patch > Files view on IE 11- On Concatenating files or downloading, the concatenated > or downloaded file occupies the entire UI. > --- > > Key: AMBARI-21084 > URL: https://issues.apache.org/jira/browse/AMBARI-21084 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.4.3 >Reporter: venkat >Assignee: venkat > Fix For: 2.5.2 > > Attachments: AMBARI-21084-trunk.patch > > > The same behaviour is observed while we are trying to download the file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21086) Hive view 2.0 does not work on IE 11 browser
Pallav Kulshreshtha created AMBARI-21086: Summary: Hive view 2.0 does not work on IE 11 browser Key: AMBARI-21086 URL: https://issues.apache.org/jira/browse/AMBARI-21086 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Pallav Kulshreshtha Assignee: Pallav Kulshreshtha Fix For: 2.5.2 It encounters JS errors and does not execute query execution. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20812) Hive view 1.5 does not work in Safari8 and IE11
[
https://issues.apache.org/jira/browse/AMBARI-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha reassigned AMBARI-20812:
Assignee: Pallav Kulshreshtha
> Hive view 1.5 does not work in Safari8 and IE11
> ---
>
> Key: AMBARI-20812
> URL: https://issues.apache.org/jira/browse/AMBARI-20812
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.2
>Reporter: amarnath reddy pappu
>Assignee: Pallav Kulshreshtha
>Priority: Critical
> Fix For: 2.5.2
>
>
> Steps to reproduce:
> 1. Launch Hive1.5 in IE11 browser - it loads Databases and Tables at left side
> 2. enter any query and submit.
> 3. Execute button would be disabled and there is no response back even if you
> wait 10-15mins.
> In console it fails with the below error.
> -
> [Error] TypeError: undefined is not a function (evaluating
> 'finalQuery.trim().endsWith(';')')
>
> run (vendor.js, line 10758)
>
> run (vendor.js, line 27192)
>
> handleRegisteredAction (vendor.js, line 29618)
>
> (anonymous function) (vendor.js, line 50042)
>
> dispatch (vendor.js, line 4872)
>
> handle (vendor.js, line 4540)
>
> This is happens in Safari8 browser as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20812) Hive view 1.5 does not work in Safari8 and IE11
[
https://issues.apache.org/jira/browse/AMBARI-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha updated AMBARI-20812:
-
Fix Version/s: 2.5.2
> Hive view 1.5 does not work in Safari8 and IE11
> ---
>
> Key: AMBARI-20812
> URL: https://issues.apache.org/jira/browse/AMBARI-20812
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.2
>Reporter: amarnath reddy pappu
>Priority: Critical
> Fix For: 2.5.2
>
>
> Steps to reproduce:
> 1. Launch Hive1.5 in IE11 browser - it loads Databases and Tables at left side
> 2. enter any query and submit.
> 3. Execute button would be disabled and there is no response back even if you
> wait 10-15mins.
> In console it fails with the below error.
> -
> [Error] TypeError: undefined is not a function (evaluating
> 'finalQuery.trim().endsWith(';')')
>
> run (vendor.js, line 10758)
>
> run (vendor.js, line 27192)
>
> handleRegisteredAction (vendor.js, line 29618)
>
> (anonymous function) (vendor.js, line 50042)
>
> dispatch (vendor.js, line 4872)
>
> handle (vendor.js, line 4540)
>
> This is happens in Safari8 browser as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-21085) Hive view 1.5 does not work in Safari8 and IE11
[
https://issues.apache.org/jira/browse/AMBARI-21085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha resolved AMBARI-21085.
--
Resolution: Fixed
> Hive view 1.5 does not work in Safari8 and IE11
> ---
>
> Key: AMBARI-21085
> URL: https://issues.apache.org/jira/browse/AMBARI-21085
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.2
>Reporter: Pallav Kulshreshtha
>Assignee: Pallav Kulshreshtha
>Priority: Critical
> Fix For: 2.5.2
>
>
> Steps to reproduce:
> 1. Launch Hive1.5 in IE11 browser - it loads Databases and Tables at left side
> 2. enter any query and submit.
> 3. Execute button would be disabled and there is no response back even if you
> wait 10-15mins.
> In console it fails with the below error.
> {noformat}
> -
> [Error] TypeError: undefined is not a function (evaluating
> 'finalQuery.trim().endsWith(';')')
>
> run (vendor.js, line 10758)
>
> run (vendor.js, line 27192)
>
> handleRegisteredAction (vendor.js, line 29618)
>
> (anonymous function) (vendor.js, line 50042)
>
> dispatch (vendor.js, line 4872)
>
> handle (vendor.js, line 4540)
>
> {noformat}
> This is happens in Safari8 browser as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20812) Hive view 1.5 does not work in Safari8 and IE11
[
https://issues.apache.org/jira/browse/AMBARI-20812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pallav Kulshreshtha updated AMBARI-20812:
-
Summary: Hive view 1.5 does not work in Safari8 and IE11 (was: Hive view
does not work in Safari8 and IE11)
> Hive view 1.5 does not work in Safari8 and IE11
> ---
>
> Key: AMBARI-20812
> URL: https://issues.apache.org/jira/browse/AMBARI-20812
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Affects Versions: 2.4.2
>Reporter: amarnath reddy pappu
>Priority: Critical
>
> Steps to reproduce:
> 1. Launch Hive1.5 in IE11 browser - it loads Databases and Tables at left side
> 2. enter any query and submit.
> 3. Execute button would be disabled and there is no response back even if you
> wait 10-15mins.
> In console it fails with the below error.
> -
> [Error] TypeError: undefined is not a function (evaluating
> 'finalQuery.trim().endsWith(';')')
>
> run (vendor.js, line 10758)
>
> run (vendor.js, line 27192)
>
> handleRegisteredAction (vendor.js, line 29618)
>
> (anonymous function) (vendor.js, line 50042)
>
> dispatch (vendor.js, line 4872)
>
> handle (vendor.js, line 4540)
>
> This is happens in Safari8 browser as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21085) Hive view 1.5 does not work in Safari8 and IE11
Pallav Kulshreshtha created AMBARI-21085:
Summary: Hive view 1.5 does not work in Safari8 and IE11
Key: AMBARI-21085
URL: https://issues.apache.org/jira/browse/AMBARI-21085
Project: Ambari
Issue Type: Bug
Components: ambari-views
Affects Versions: 2.4.2
Reporter: Pallav Kulshreshtha
Assignee: Pallav Kulshreshtha
Priority: Critical
Fix For: 2.5.2
Steps to reproduce:
1. Launch Hive1.5 in IE11 browser - it loads Databases and Tables at left side
2. enter any query and submit.
3. Execute button would be disabled and there is no response back even if you
wait 10-15mins.
In console it fails with the below error.
{noformat}
-
[Error] TypeError: undefined is not a function (evaluating
'finalQuery.trim().endsWith(';')')
run (vendor.js, line 10758)
run (vendor.js, line 27192)
handleRegisteredAction (vendor.js, line 29618)
(anonymous function) (vendor.js, line 50042)
dispatch (vendor.js, line 4872)
handle (vendor.js, line 4540)
{noformat}
This is happens in Safari8 browser as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-21084) Files view on IE 11- On Concatenating files or downloading, the concatenated or downloaded file occupies the entire UI.
venkat created AMBARI-21084: --- Summary: Files view on IE 11- On Concatenating files or downloading, the concatenated or downloaded file occupies the entire UI. Key: AMBARI-21084 URL: https://issues.apache.org/jira/browse/AMBARI-21084 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.4.3 Reporter: venkat Assignee: venkat Fix For: 2.5.2 The same behaviour is observed while we are trying to download the file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-21033) Log Search use POJOs for input configuration
[ https://issues.apache.org/jira/browse/AMBARI-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely resolved AMBARI-21033. - Resolution: Fixed > Log Search use POJOs for input configuration > > > Key: AMBARI-21033 > URL: https://issues.apache.org/jira/browse/AMBARI-21033 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21033.patch > > > Instead of parsing the input configuration jsons in logfeeder the > configuration api should return POJOs with the input and filter descriptions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21033) Log Search use POJOs for input configuration
[ https://issues.apache.org/jira/browse/AMBARI-21033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Gergely updated AMBARI-21033: Attachment: AMBARI-21033.patch > Log Search use POJOs for input configuration > > > Key: AMBARI-21033 > URL: https://issues.apache.org/jira/browse/AMBARI-21033 > Project: Ambari > Issue Type: Improvement > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Miklos Gergely >Assignee: Miklos Gergely > Fix For: 3.0.0 > > Attachments: AMBARI-21033.patch > > > Instead of parsing the input configuration jsons in logfeeder the > configuration api should return POJOs with the input and filter descriptions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21011) Append PATH to YARN config 'yarn.nodemanager.admin-env' for HDP 2.6
[
https://issues.apache.org/jira/browse/AMBARI-21011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019407#comment-16019407
]
Hudson commented on AMBARI-21011:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7511 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7511/])
Revert "ADDENDUM. AMBARI-21011. Upgrade Code. Append PATH to YARN config
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1603cd6840852b69567523f74a4b708aa4bd6d73])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml
> Append PATH to YARN config 'yarn.nodemanager.admin-env' for HDP 2.6
> ---
>
> Key: AMBARI-21011
> URL: https://issues.apache.org/jira/browse/AMBARI-21011
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-21011.freshInstallHDP2.6.patch,
> AMBARI-21011.patch, AMBARI-21011.UpgradePathTo2.6.patch
>
>
> Need to append the PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin to
> {{yarn.nodemanager.admin-env}}, as the PATH now is not passed into YARN
> containers by default, as part of security fix in YARN.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-21057) Change Storage of Data on Request/Stage/Task To Reduce Redundency (trunk)
[ https://issues.apache.org/jira/browse/AMBARI-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019408#comment-16019408 ] Hudson commented on AMBARI-21057: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7511 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7511/]) AMBARI-21057. Change Storage of Data on Request/Stage/Task To Reduce (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cbb1e9059669b2af7d63323321980d8cc0f9203f]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StageResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog251.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RequestStageContainerTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/credentialapi/CredentialUtilTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/RangerSSLConfigCheck.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariPamAuthenticationProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/metrics/system/impl/AmbariMetricSinkImpl.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/ServiceCheckValidityCheckTest.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/logging/LogSearchDataRetrievalServiceTest.java > Change Storage of Data on Request/Stage/Task To Reduce Redundency (trunk) > - > > Key: AMBARI-21057 > URL: https://issues.apache.org/jira/browse/AMBARI-21057 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21057-checkstyle.patch, AMBARI-21057.patch > > > Move stage.cluster_host_info to request.cluster_host_info -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Status: Patch Available (was: Open) > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: 3.0.0 >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: AMBARI-20739.patch, script_alert_notification_1.png, > script_alert_notification_2.png > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. > So now on web ui we will two ways to configure the script location for > script-based alert dispatchers: > 1.By script dispatch property (ambari.dispatch-property.script).This is > already supported in previous ambari release. > Please see > https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(ambari.dispatch-property.script.filename). > This new way will lookup the script by filename in script directory,default > in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by > ambari.dispatch-property.script.directory property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Affects Version/s: (was: 3.0.0) trunk > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: AMBARI-20739.patch, script_alert_notification_1.png, > script_alert_notification_2.png > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. > So now on web ui we will two ways to configure the script location for > script-based alert dispatchers: > 1.By script dispatch property (ambari.dispatch-property.script).This is > already supported in previous ambari release. > Please see > https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(ambari.dispatch-property.script.filename). > This new way will lookup the script by filename in script directory,default > in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by > ambari.dispatch-property.script.directory property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Attachment: AMBARI-20739.patch > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: 3.0.0 >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: AMBARI-20739.patch, script_alert_notification_1.png, > script_alert_notification_2.png > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. > So now on web ui we will two ways to configure the script location for > script-based alert dispatchers: > 1.By script dispatch property (ambari.dispatch-property.script).This is > already supported in previous ambari release. > Please see > https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(ambari.dispatch-property.script.filename). > This new way will lookup the script by filename in script directory,default > in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by > ambari.dispatch-property.script.directory property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21057) Change Storage of Data on Request/Stage/Task To Reduce Redundency (trunk)
[ https://issues.apache.org/jira/browse/AMBARI-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019342#comment-16019342 ] Doroszlai, Attila commented on AMBARI-21057: Thanks! > Change Storage of Data on Request/Stage/Task To Reduce Redundency (trunk) > - > > Key: AMBARI-21057 > URL: https://issues.apache.org/jira/browse/AMBARI-21057 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21057-checkstyle.patch, AMBARI-21057.patch > > > Move stage.cluster_host_info to request.cluster_host_info -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21057) Change Storage of Data on Request/Stage/Task To Reduce Redundency (trunk)
[ https://issues.apache.org/jira/browse/AMBARI-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019328#comment-16019328 ] Dmytro Grinenko commented on AMBARI-21057: -- [~adoroszlai] committed in cbb1e9059669b2af7d63323321980d8cc0f9203f > Change Storage of Data on Request/Stage/Task To Reduce Redundency (trunk) > - > > Key: AMBARI-21057 > URL: https://issues.apache.org/jira/browse/AMBARI-21057 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21057-checkstyle.patch, AMBARI-21057.patch > > > Move stage.cluster_host_info to request.cluster_host_info -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-21057) Change Storage of Data on Request/Stage/Task To Reduce Redundency (trunk)
[ https://issues.apache.org/jira/browse/AMBARI-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko resolved AMBARI-21057. -- Resolution: Fixed > Change Storage of Data on Request/Stage/Task To Reduce Redundency (trunk) > - > > Key: AMBARI-21057 > URL: https://issues.apache.org/jira/browse/AMBARI-21057 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21057-checkstyle.patch, AMBARI-21057.patch > > > Move stage.cluster_host_info to request.cluster_host_info -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-3524) Set up generic puppet module architecture to manage both HDP and CDH (and Apache?) stacks
[ https://issues.apache.org/jira/browse/AMBARI-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019324#comment-16019324 ] tianbaochao commented on AMBARI-3524: - why did this issue not assigned for so long a time?? Is there no one had concern on this issue? > Set up generic puppet module architecture to manage both HDP and CDH (and > Apache?) stacks > - > > Key: AMBARI-3524 > URL: https://issues.apache.org/jira/browse/AMBARI-3524 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent >Reporter: Thibaut Marmin > Labels: agent, cdh, cloudera, hdp, puppet, stack > > Currently ambari-agent manages stacks via puppet modules. These modules are > specific to HDP stacks in the sens that scripts strongly depend on it special > features: > - Some packages only exists in HDP stack (e.g. hadoop-sbin, hadoop-pipes, > etc.) > - Some scripts doesn’t exists in CDH stack (e.g. > /usr/lib/hadoop/bin/hadoop-daemon.sh) > - Etc. > To allow ambari to manage CDH stacks, two ways are possible according to my > point of view : > - Consider CDH services as new services. This includes development of new > puppet modules named cdh instead hdp. > - Make the current puppet modules more generic by removing all hdp references > in their names and develop an additional conditional level to handle cases as > you deploy CDH or HDP stack. > The second method seems to be more attractive because it abstracts the tool > from HDP naming. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-21011) Append PATH to YARN config 'yarn.nodemanager.admin-env' for HDP 2.6
[
https://issues.apache.org/jira/browse/AMBARI-21011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019306#comment-16019306
]
Hudson commented on AMBARI-21011:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7510 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7510/])
Revert "Revert "ADDENDUM. AMBARI-21011. Upgrade Code. Append PATH to
(sshridhar:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ccd6b25ed2f053a9b1b2045fd0cf41f4472e657e])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/nonrolling-upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.6.xml
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.6.xml
> Append PATH to YARN config 'yarn.nodemanager.admin-env' for HDP 2.6
> ---
>
> Key: AMBARI-21011
> URL: https://issues.apache.org/jira/browse/AMBARI-21011
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.5.0
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Blocker
> Fix For: trunk, 2.5.1
>
> Attachments: AMBARI-21011.freshInstallHDP2.6.patch,
> AMBARI-21011.patch, AMBARI-21011.UpgradePathTo2.6.patch
>
>
> Need to append the PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin to
> {{yarn.nodemanager.admin-env}}, as the PATH now is not passed into YARN
> containers by default, as part of security fix in YARN.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-21057) Change Storage of Data on Request/Stage/Task To Reduce Redundency (trunk)
[ https://issues.apache.org/jira/browse/AMBARI-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-21057: - Attachment: AMBARI-21057-checkstyle.patch > Change Storage of Data on Request/Stage/Task To Reduce Redundency (trunk) > - > > Key: AMBARI-21057 > URL: https://issues.apache.org/jira/browse/AMBARI-21057 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk >Reporter: Dmytro Grinenko >Assignee: Dmytro Grinenko >Priority: Critical > Fix For: trunk > > Attachments: AMBARI-21057-checkstyle.patch, AMBARI-21057.patch > > > Move stage.cluster_host_info to request.cluster_host_info -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Description: Although we can create the alert target of type ALERT_SCRIPT by web ui, we still need access to ambari.properties to add the new script and then restart ambari server to make this function take effect.It is better specify the script directly in alert target rather than in ambari.properties.In this way,we also don't need to restart ambari server. So now on web ui we will two ways to configure the script location for script-based alert dispatchers: 1.By script dispatch property (ambari.dispatch-property.script).This is already supported in previous ambari release. Please see https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 2.By script filename(ambari.dispatch-property.script.filename). This new way will lookup the script by filename in script directory,default in /var/lib/ambari-server/resources/scripts. We can change the directory in ambari.properties by ambari.dispatch-property.script.directory property. was: Although we can create the alert target of type ALERT_SCRIPT by web ui, we still need access to ambari.properties to add the new script and then restart ambari server to make this function take effect.It is better specify the script directly in alert target rather than in ambari.properties.In this way,we also don't need to restart ambari server. > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: 3.0.0 >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: script_alert_notification_1.png, > script_alert_notification_2.png > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. > So now on web ui we will two ways to configure the script location for > script-based alert dispatchers: > 1.By script dispatch property (ambari.dispatch-property.script).This is > already supported in previous ambari release. > Please see > https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0 > 2.By script filename(ambari.dispatch-property.script.filename). > This new way will lookup the script by filename in script directory,default > in /var/lib/ambari-server/resources/scripts. > We can change the directory in ambari.properties by > ambari.dispatch-property.script.directory property. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20739) Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-20739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yao Lei updated AMBARI-20739: - Attachment: script_alert_notification_2.png script_alert_notification_1.png > Specify the script directly in alert target for script-based alert dispatchers > -- > > Key: AMBARI-20739 > URL: https://issues.apache.org/jira/browse/AMBARI-20739 > Project: Ambari > Issue Type: Task > Components: alerts, ambari-web >Affects Versions: 3.0.0 >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: script_alert_notification_1.png, > script_alert_notification_2.png > > > Although we can create the alert target of type ALERT_SCRIPT by web ui, we > still need access to ambari.properties to add the new script and then > restart ambari server to make this function take effect.It is better specify > the script directly in alert target rather than in ambari.properties.In this > way,we also don't need to restart ambari server. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
