[jira] [Updated] (AMBARI-18805) Bulk delete hosts: sending a force option to delete all components
[ https://issues.apache.org/jira/browse/AMBARI-18805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18805: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk 5494b6a82e36401d271fb2339101b7b5c46cb488 > Bulk delete hosts: sending a force option to delete all components > -- > > Key: AMBARI-18805 > URL: https://issues.apache.org/jira/browse/AMBARI-18805 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18805.v0.patch > > > Send a force option to delete all components when delete hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18805) Bulk delete hosts: sending a force option to delete all components
[ https://issues.apache.org/jira/browse/AMBARI-18805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18805: Status: Patch Available (was: Open) > Bulk delete hosts: sending a force option to delete all components > -- > > Key: AMBARI-18805 > URL: https://issues.apache.org/jira/browse/AMBARI-18805 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18805.v0.patch > > > Send a force option to delete all components when delete hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18805) Bulk delete hosts: sending a force option to delete all components
[ https://issues.apache.org/jira/browse/AMBARI-18805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18805: Attachment: AMBARI-18805.v0.patch Local ambari-web test passed. 30351 tests complete (34 seconds) 151 tests pending Manual testing done > Bulk delete hosts: sending a force option to delete all components > -- > > Key: AMBARI-18805 > URL: https://issues.apache.org/jira/browse/AMBARI-18805 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-18805.v0.patch > > > Send a force option to delete all components when delete hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18805) Bulk delete hosts: sending a force option to delete all components
Zhe (Joe) Wang created AMBARI-18805: --- Summary: Bulk delete hosts: sending a force option to delete all components Key: AMBARI-18805 URL: https://issues.apache.org/jira/browse/AMBARI-18805 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Priority: Critical Fix For: 3.0.0 Send a force option to delete all components when delete hosts -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18777) Component actions confirmation window (from host details page) don't have the details about action to be confirmed
[ https://issues.apache.org/jira/browse/AMBARI-18777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18777: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk 556b285e591211a2abf8a90830ee9d8bffc79562 > Component actions confirmation window (from host details page) don't have the > details about action to be confirmed > --- > > Key: AMBARI-18777 > URL: https://issues.apache.org/jira/browse/AMBARI-18777 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18777.v0.patch > > > Component actions confirmation modal window (from host details page) don't > have the details about action to be confirmed. > The window asks the user "Are you sure" only for any action selected except > delete e.g Stop, Start, Turn On Maintenance Mode, Restart. > Steps to reproduce the issue: > 1. Login to Ambari > 2. Navigate to Hosts Tab > 3. Click on Service action drop down of any service available > 4. Click on any component action e.g Restart/Stop/Start > 5. The confirmation window should have the action to be performed E.g In Case > of Restart, "You are about to Restart Service NodeManager, Confirm?". > But it just have text "Are you sure" for any action selected except delete -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
[ https://issues.apache.org/jira/browse/AMBARI-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18595: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk f29ab2bdf4b33702316018692179572d7fd1a077 and branch-2.5 5069100f64f0ee9007b7688a881fdac49f31fb24 > Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11 > > > Key: AMBARI-18595 > URL: https://issues.apache.org/jira/browse/AMBARI-18595 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: Microsoft Windows 10 > - Microsoft Edge > - Microsoft Internet Explorer 11 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18595.v0.patch, AMBARI-18595.v1.patch, > AMBARI-18595.v1Trunk.patch, Capture.PNG > > > Icons do not display in any page as shown in the screen-shot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18775) Host Page filter not working properly
[ https://issues.apache.org/jira/browse/AMBARI-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang resolved AMBARI-18775. - Resolution: Not A Bug > Host Page filter not working properly > - > > Key: AMBARI-18775 > URL: https://issues.apache.org/jira/browse/AMBARI-18775 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Vivek Rathod >Assignee: Zhe (Joe) Wang > Fix For: 2.4.2 > > > STR: > Go to hosts page and filter by Resourcemanager. The hosts filtered does not > contain resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-18775) Host Page filter not working properly
[ https://issues.apache.org/jira/browse/AMBARI-18775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang reassigned AMBARI-18775: --- Assignee: Zhe (Joe) Wang > Host Page filter not working properly > - > > Key: AMBARI-18775 > URL: https://issues.apache.org/jira/browse/AMBARI-18775 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Vivek Rathod >Assignee: Zhe (Joe) Wang > Fix For: 2.4.2 > > > STR: > Go to hosts page and filter by Resourcemanager. The hosts filtered does not > contain resourcemanager. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18346) SmartSense Mandatory Install
[ https://issues.apache.org/jira/browse/AMBARI-18346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18346: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk 950d1db879b203a9d8090f414cc75fb54a5deb55 and branch-2.5 6ed95d5d6981b3c6b28f7260887742b4eda8d525 > SmartSense Mandatory Install > > > Key: AMBARI-18346 > URL: https://issues.apache.org/jira/browse/AMBARI-18346 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18346.v0.patch, AMBARI-18346.v1.patch, > AMBARI-18346.v1Trunk.patch > > > Perform a UI hack to force selection of SmartSense for HDP stacks (the user > cannot deselect). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
[ https://issues.apache.org/jira/browse/AMBARI-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang reopened AMBARI-18595: - Reverted on trunk 780bf944aa02ef2c075ddcd3215ff9fb81ee025d and branch-2.5 e5f0dfc8d73c35fe08a3a66d479aabda48f8ec5e > Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11 > > > Key: AMBARI-18595 > URL: https://issues.apache.org/jira/browse/AMBARI-18595 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: Microsoft Windows 10 > - Microsoft Edge > - Microsoft Internet Explorer 11 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18595.v0.patch, Capture.PNG > > > Icons do not display in any page as shown in the screen-shot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18245) Upgrade node to version 4.x
[ https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18245: Fix Version/s: (was: trunk) 2.5.0 > Upgrade node to version 4.x > --- > > Key: AMBARI-18245 > URL: https://issues.apache.org/jira/browse/AMBARI-18245 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: trunk >Reporter: Yusaku Sako >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18245.v0.patch, AMBARI-18245.v1.patch > > > We are currently using 0.10, which is very old and going EOL 2016-10-01: > https://github.com/nodejs/LTS > We should look into upgrading to Node 4.x: > * Upgrade Node on Ambari Web > * Upgrade Node on Ambari Admin > * Upgrade Node on contrib/views/* modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18245) Upgrade node to version 4.x
[ https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18245: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to branch-2.5 1b32cd0427e4a7de0cc5af65746d620cb2db448c and trunk 7be041894a6384a211aee965be36b1d429103fb3 > Upgrade node to version 4.x > --- > > Key: AMBARI-18245 > URL: https://issues.apache.org/jira/browse/AMBARI-18245 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: trunk >Reporter: Yusaku Sako >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18245.v0.patch, AMBARI-18245.v1.patch > > > We are currently using 0.10, which is very old and going EOL 2016-10-01: > https://github.com/nodejs/LTS > We should look into upgrading to Node 4.x: > * Upgrade Node on Ambari Web > * Upgrade Node on Ambari Admin > * Upgrade Node on contrib/views/* modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18245) Upgrade node to version 4.x
[ https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587234#comment-15587234 ] Zhe (Joe) Wang commented on AMBARI-18245: - The failure is due to: Could not find artifact org.apache.ambari.contrib.views:ambari-views-commons:jar:2.0.0.0-SNAPSHOT in oss.sonatype.org (https://oss.sonatype.org/content/groups/staging) which is not related to this patch. > Upgrade node to version 4.x > --- > > Key: AMBARI-18245 > URL: https://issues.apache.org/jira/browse/AMBARI-18245 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: trunk >Reporter: Yusaku Sako >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18245.v0.patch, AMBARI-18245.v1.patch > > > We are currently using 0.10, which is very old and going EOL 2016-10-01: > https://github.com/nodejs/LTS > We should look into upgrading to Node 4.x: > * Upgrade Node on Ambari Web > * Upgrade Node on Ambari Admin > * Upgrade Node on contrib/views/* modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18245) Upgrade node to version 4.x
[ https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18245: Attachment: AMBARI-18245.v1.patch > Upgrade node to version 4.x > --- > > Key: AMBARI-18245 > URL: https://issues.apache.org/jira/browse/AMBARI-18245 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: trunk >Reporter: Yusaku Sako >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18245.v0.patch, AMBARI-18245.v1.patch > > > We are currently using 0.10, which is very old and going EOL 2016-10-01: > https://github.com/nodejs/LTS > We should look into upgrading to Node 4.x: > * Upgrade Node on Ambari Web > * Upgrade Node on Ambari Admin > * Upgrade Node on contrib/views/* modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18595) Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11
[ https://issues.apache.org/jira/browse/AMBARI-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18595: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk and branch-2.5 fdda172fed36ae3e156dc2757a09f85d0a379175 > Icons don't display in Windows 10 Microsoft Edge or Internet Explorer 11 > > > Key: AMBARI-18595 > URL: https://issues.apache.org/jira/browse/AMBARI-18595 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 > Environment: Microsoft Windows 10 > - Microsoft Edge > - Microsoft Internet Explorer 11 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18595.v0.patch, Capture.PNG > > > Icons do not display in any page as shown in the screen-shot attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown
[ https://issues.apache.org/jira/browse/AMBARI-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17636: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to branch-2.5 e41a036c5ee8891fd19f027c825e067914ab65fc and trunk 89d964e0e0e5b6285d8207420720cd54888c > Service Configs page: can't see all config versions in dropdown > --- > > Key: AMBARI-17636 > URL: https://issues.apache.org/jira/browse/AMBARI-17636 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, > AMBARI-17636.v4.patch, AMBARI-17636.v5.patch, AMBARI-17636.v6.patch, > AMBARI-17636.v7.patch, bugfix.gif > > > * Go to Service->Configs page (that have more than ~ 30 versions) > * Open versions dropdown > *Result:* > Number of visible versions limited by window height. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18535) Ambari is not picking up the latest repo for HDP-2.4
[ https://issues.apache.org/jira/browse/AMBARI-18535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18535: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk and branch-2.5 96d66e0d41d49e67d11d5ea558c24d858f4b9577 > Ambari is not picking up the latest repo for HDP-2.4 > > > Key: AMBARI-18535 > URL: https://issues.apache.org/jira/browse/AMBARI-18535 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18535.v0.patch > > > During fresh deployment, if HDP-2.4 is chosen then Ambari does not default to > the latest 2.4 release, HDP-2.4.2. This is likely because VDF files do not > exist for HDP-2.4 release and the older mechanism of picking the latest repo > URL form the hdp_urlinfo.json does not work. HDP-2.4.0 is chosen where as the > latest is HDP-2.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18566: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk, branch-2.4 and branch-2.5 2709304c50a934679069c2ac63e1dfe64e7dfc3c > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18566: Comment: was deleted (was: The failure is not related to the patch.) > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15569782#comment-15569782 ] Zhe (Joe) Wang commented on AMBARI-18566: - The failure is not related to the patch. > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15569781#comment-15569781 ] Zhe (Joe) Wang commented on AMBARI-18566: - The failure is not related to the patch. > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch, AMBARI-18566.v1.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18559) At "Add Service Wizard", when the installation is going on, if I click the close (X) on the wizard, the service will only get INSTALLED not STARTED.
[ https://issues.apache.org/jira/browse/AMBARI-18559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18559: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk 6587fda470bcf063027e55b315292018dc1e64b4 > At "Add Service Wizard", when the installation is going on, if I click the > close (X) on the wizard, the service will only get INSTALLED not STARTED. > > > Key: AMBARI-18559 > URL: https://issues.apache.org/jira/browse/AMBARI-18559 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18559.v0.patch > > > - Typically being in "Add Service Wizard", user expects the INSTALL and START > of sevices components. > - However, if user clicks on the close (X) on the wizard, the service will > only get INSTALLED not STARTED. > - Either apprising the user that only INSTALL will take place and START will > be skipped will help OR even if the close (X) on the wizard is hit, context > for START is still maintained. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18534) Advanced storm-atlas-application.properties panel is not opened by default upon filtering
[ https://issues.apache.org/jira/browse/AMBARI-18534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18534: Resolution: Fixed Status: Resolved (was: Patch Available) Patch committed to trunk and branch-2.5 8f51c9324a407fa8ce8e92e2e77ee0a250c5cbc9 > Advanced storm-atlas-application.properties panel is not opened by default > upon filtering > - > > Key: AMBARI-18534 > URL: https://issues.apache.org/jira/browse/AMBARI-18534 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Dhanya Balasundaran >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18534.v0.patch > > > - Navigate to Storm configs page > - Type "hook" in the property filter > - Its expected that Advanced storm-atlas-application.properties panel opens > up by default > - Actual: its still closed. please see the screenshot attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18566: Status: Patch Available (was: Open) > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
[ https://issues.apache.org/jira/browse/AMBARI-18566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18566: Attachment: AMBARI-18566.v0.patch Local ambari-web test passed. 30374 tests complete (27 seconds) 151 tests pending Manual testing done > Installer wizard-> Select Versions page: Selecting Red Hat Satellite option > and clicking next button makes wizard stuck > --- > > Key: AMBARI-18566 > URL: https://issues.apache.org/jira/browse/AMBARI-18566 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18566.v0.patch > > > *STR:* > # Got to select versions page > # Choose "Use Local Repository" option and then choose "Use RedHat > Satellite/Spacewalk" option > # Next button will get enabled. click on next button. > *Expected Result:* wizard goes to next page > *Actual Result:* On clicking next button, next button gets disabled and > wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18566) Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck
Zhe (Joe) Wang created AMBARI-18566: --- Summary: Installer wizard-> Select Versions page: Selecting Red Hat Satellite option and clicking next button makes wizard stuck Key: AMBARI-18566 URL: https://issues.apache.org/jira/browse/AMBARI-18566 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Priority: Critical Fix For: 2.4.2 *STR:* # Got to select versions page # Choose "Use Local Repository" option and then choose "Use RedHat Satellite/Spacewalk" option # Next button will get enabled. click on next button. *Expected Result:* wizard goes to next page *Actual Result:* On clicking next button, next button gets disabled and wizard does not go to next page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18245) Upgrade node to version 4.x
[ https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15558782#comment-15558782 ] Zhe (Joe) Wang commented on AMBARI-18245: - I'm running some system tests on it. It should be in with one or two days. > Upgrade node to version 4.x > --- > > Key: AMBARI-18245 > URL: https://issues.apache.org/jira/browse/AMBARI-18245 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: trunk >Reporter: Yusaku Sako >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18245.v0.patch > > > We are currently using 0.10, which is very old and going EOL 2016-10-01: > https://github.com/nodejs/LTS > We should look into upgrading to Node 4.x: > * Upgrade Node on Ambari Web > * Upgrade Node on Ambari Admin > * Upgrade Node on contrib/views/* modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-18245) Upgrade node to version 4.x
[ https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15558782#comment-15558782 ] Zhe (Joe) Wang edited comment on AMBARI-18245 at 10/8/16 9:56 PM: -- I'm running some system tests on it. It should be in within one or two days. was (Author: jwang): I'm running some system tests on it. It should be in with one or two days. > Upgrade node to version 4.x > --- > > Key: AMBARI-18245 > URL: https://issues.apache.org/jira/browse/AMBARI-18245 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: trunk >Reporter: Yusaku Sako >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18245.v0.patch > > > We are currently using 0.10, which is very old and going EOL 2016-10-01: > https://github.com/nodejs/LTS > We should look into upgrading to Node 4.x: > * Upgrade Node on Ambari Web > * Upgrade Node on Ambari Admin > * Upgrade Node on contrib/views/* modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-14958) Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB
[ https://issues.apache.org/jira/browse/AMBARI-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang reassigned AMBARI-14958: --- Assignee: Zhe (Joe) Wang (was: Oleg Nechiporenko) > Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB > - > > Key: AMBARI-14958 > URL: https://issues.apache.org/jira/browse/AMBARI-14958 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-14958.patch, AMBARI-14958.v0.patch > > > 1) Rename current notification type "SNMP" to "Custom SNMP" > 2) Create a new notification type "SNMP" that prompts for version, community, > hosts, ports > 3) When this is chosen, Ambari under-the-hood generates the SNMP traps based > on the MIB. > 4) The MIB file should be shipped with Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14958) Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB
[ https://issues.apache.org/jira/browse/AMBARI-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-14958: Attachment: AMBARI-14958.v0.patch Local ambari-web test passed. 30373 tests complete (26 seconds) 151 tests pending Manual testing done > Alerts: Create new Alerts Notification type for SNMP to handle Ambari MIB > - > > Key: AMBARI-14958 > URL: https://issues.apache.org/jira/browse/AMBARI-14958 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-14958.patch, AMBARI-14958.v0.patch > > > 1) Rename current notification type "SNMP" to "Custom SNMP" > 2) Create a new notification type "SNMP" that prompts for version, community, > hosts, ports > 3) When this is chosen, Ambari under-the-hood generates the SNMP traps based > on the MIB. > 4) The MIB file should be shipped with Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18535) Ambari is not picking up the latest repo for HDP-2.4
[ https://issues.apache.org/jira/browse/AMBARI-18535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18535: Status: Patch Available (was: Open) > Ambari is not picking up the latest repo for HDP-2.4 > > > Key: AMBARI-18535 > URL: https://issues.apache.org/jira/browse/AMBARI-18535 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18535.v0.patch > > > During fresh deployment, if HDP-2.4 is chosen then Ambari does not default to > the latest 2.4 release, HDP-2.4.2. This is likely because VDF files do not > exist for HDP-2.4 release and the older mechanism of picking the latest repo > URL form the hdp_urlinfo.json does not work. HDP-2.4.0 is chosen where as the > latest is HDP-2.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18535) Ambari is not picking up the latest repo for HDP-2.4
[ https://issues.apache.org/jira/browse/AMBARI-18535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18535: Attachment: AMBARI-18535.v0.patch Local ambari-web test passed. 30374 tests complete (27 seconds) 151 tests pending Manual testing done > Ambari is not picking up the latest repo for HDP-2.4 > > > Key: AMBARI-18535 > URL: https://issues.apache.org/jira/browse/AMBARI-18535 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18535.v0.patch > > > During fresh deployment, if HDP-2.4 is chosen then Ambari does not default to > the latest 2.4 release, HDP-2.4.2. This is likely because VDF files do not > exist for HDP-2.4 release and the older mechanism of picking the latest repo > URL form the hdp_urlinfo.json does not work. HDP-2.4.0 is chosen where as the > latest is HDP-2.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18535) Ambari is not picking up the latest repo for HDP-2.4
Zhe (Joe) Wang created AMBARI-18535: --- Summary: Ambari is not picking up the latest repo for HDP-2.4 Key: AMBARI-18535 URL: https://issues.apache.org/jira/browse/AMBARI-18535 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: 2.5.0 During fresh deployment, if HDP-2.4 is chosen then Ambari does not default to the latest 2.4 release, HDP-2.4.2. This is likely because VDF files do not exist for HDP-2.4 release and the older mechanism of picking the latest repo URL form the hdp_urlinfo.json does not work. HDP-2.4.0 is chosen where as the latest is HDP-2.4.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18245) Upgrade node to version 4.x
[ https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18245: Status: Patch Available (was: Open) > Upgrade node to version 4.x > --- > > Key: AMBARI-18245 > URL: https://issues.apache.org/jira/browse/AMBARI-18245 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: trunk >Reporter: Yusaku Sako >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18245.v0.patch > > > We are currently using 0.10, which is very old and going EOL 2016-10-01: > https://github.com/nodejs/LTS > We should look into upgrading to Node 4.x: > * Upgrade Node on Ambari Web > * Upgrade Node on Ambari Admin > * Upgrade Node on contrib/views/* modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18245) Upgrade node to version 4.x
[ https://issues.apache.org/jira/browse/AMBARI-18245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18245: Attachment: AMBARI-18245.v0.patch Local test passed. Manual testing done. > Upgrade node to version 4.x > --- > > Key: AMBARI-18245 > URL: https://issues.apache.org/jira/browse/AMBARI-18245 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-views, ambari-web >Affects Versions: trunk >Reporter: Yusaku Sako >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18245.v0.patch > > > We are currently using 0.10, which is very old and going EOL 2016-10-01: > https://github.com/nodejs/LTS > We should look into upgrading to Node 4.x: > * Upgrade Node on Ambari Web > * Upgrade Node on Ambari Admin > * Upgrade Node on contrib/views/* modules -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18449) Ambari create widget does not show what the error is
[ https://issues.apache.org/jira/browse/AMBARI-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18449: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk 69e8f6fa89b5b2a4e6246e0e32b23c314a12df5c > Ambari create widget does not show what the error is > > > Key: AMBARI-18449 > URL: https://issues.apache.org/jira/browse/AMBARI-18449 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.2 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18449.v0.patch > > > Tried to create a custom widget but the next button was disabled. However the > UI did not show what the error was -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18408) Configuration Groups popup: Tooltip over properties number has too much content
[ https://issues.apache.org/jira/browse/AMBARI-18408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18408: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.5 e54c31e8900773dc46a80b2f18e111798709d536 > Configuration Groups popup: Tooltip over properties number has too much > content > --- > > Key: AMBARI-18408 > URL: https://issues.apache.org/jira/browse/AMBARI-18408 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-18408.v0.patch, AMBARI-18408.v1.patch, > config-group-properties.jpg > > > Configuration Groups popup contains a link with number of overridden > properties for every group. On click all these properties are listed in > popup, while on hover the same info is contained in tooltip. In some cases > there's [too much content|^config-group-properties.jpg] for tooltip. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
[ https://issues.apache.org/jira/browse/AMBARI-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488332#comment-15488332 ] Zhe (Joe) Wang commented on AMBARI-18281: - Committed to trunk 9595706527b924cb273723fd1906c6a4b5d3d686 > Expose Disabling of Alert Targets in Web Client > --- > > Key: AMBARI-18281 > URL: https://issues.apache.org/jira/browse/AMBARI-18281 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18281.v0.patch, AMBARI-18281.v1.patch, > AMBARI-18281.v2.patch > > > Add an option to Enable/ Disable alert notifications in Manage Notifications > popup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-10908) Usability: ability to perform bulk delete host
[ https://issues.apache.org/jira/browse/AMBARI-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-10908: Fix Version/s: (was: trunk) 2.5.0 > Usability: ability to perform bulk delete host > -- > > Key: AMBARI-10908 > URL: https://issues.apache.org/jira/browse/AMBARI-10908 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Jeff Sposetti >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-10908.v0.patch, AMBARI-10908.v1.patch > > > On Hosts page, provide ability to delete hosts in bulk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-10908) Usability: ability to perform bulk delete host
[ https://issues.apache.org/jira/browse/AMBARI-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488268#comment-15488268 ] Zhe (Joe) Wang commented on AMBARI-10908: - backported to branch-2.5 > Usability: ability to perform bulk delete host > -- > > Key: AMBARI-10908 > URL: https://issues.apache.org/jira/browse/AMBARI-10908 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Jeff Sposetti >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-10908.v0.patch, AMBARI-10908.v1.patch > > > On Hosts page, provide ability to delete hosts in bulk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count
[ https://issues.apache.org/jira/browse/AMBARI-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488262#comment-15488262 ] Zhe (Joe) Wang commented on AMBARI-18280: - backported to branch-2.5 > Ambari widget graph is not aggregating the data correctly for Total Request > Count > - > > Key: AMBARI-18280 > URL: https://issues.apache.org/jira/browse/AMBARI-18280 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18280.v0.patch > > > *PROBLEM:* Total Request Count is not growing exponentially > *IMPACT:* User is not able to monitor the data correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count
[ https://issues.apache.org/jira/browse/AMBARI-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18280: Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari widget graph is not aggregating the data correctly for Total Request > Count > - > > Key: AMBARI-18280 > URL: https://issues.apache.org/jira/browse/AMBARI-18280 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18280.v0.patch > > > *PROBLEM:* Total Request Count is not growing exponentially > *IMPACT:* User is not able to monitor the data correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count
[ https://issues.apache.org/jira/browse/AMBARI-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15453877#comment-15453877 ] Zhe (Joe) Wang commented on AMBARI-18280: - Committed to trunk f4ce46f0bbe1ed78182b3f56a03f69a8c68af432 > Ambari widget graph is not aggregating the data correctly for Total Request > Count > - > > Key: AMBARI-18280 > URL: https://issues.apache.org/jira/browse/AMBARI-18280 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18280.v0.patch > > > *PROBLEM:* Total Request Count is not growing exponentially > *IMPACT:* User is not able to monitor the data correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18281) Expose Disabling of Alert Targets in Web Client
[ https://issues.apache.org/jira/browse/AMBARI-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18281: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk 4f84718b691641a1293f677f3b1abc873f1dc07b > Expose Disabling of Alert Targets in Web Client > --- > > Key: AMBARI-18281 > URL: https://issues.apache.org/jira/browse/AMBARI-18281 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18281.v0.patch, AMBARI-18281.v1.patch > > > Add an option to Enable/ Disable alert notifications in Manage Notifications > popup. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count
[ https://issues.apache.org/jira/browse/AMBARI-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18280: Status: Patch Available (was: Open) > Ambari widget graph is not aggregating the data correctly for Total Request > Count > - > > Key: AMBARI-18280 > URL: https://issues.apache.org/jira/browse/AMBARI-18280 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18280.v0.patch > > > *PROBLEM:* Total Request Count is not growing exponentially > *IMPACT:* User is not able to monitor the data correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count
[ https://issues.apache.org/jira/browse/AMBARI-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18280: Attachment: AMBARI-18280.v0.patch Local ambari-web test passed. 30014 tests complete (27 seconds) 154 tests pending Manual testing done. > Ambari widget graph is not aggregating the data correctly for Total Request > Count > - > > Key: AMBARI-18280 > URL: https://issues.apache.org/jira/browse/AMBARI-18280 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-18280.v0.patch > > > *PROBLEM:* Total Request Count is not growing exponentially > *IMPACT:* User is not able to monitor the data correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18280) Ambari widget graph is not aggregating the data correctly for Total Request Count
Zhe (Joe) Wang created AMBARI-18280: --- Summary: Ambari widget graph is not aggregating the data correctly for Total Request Count Key: AMBARI-18280 URL: https://issues.apache.org/jira/browse/AMBARI-18280 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.2.2 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: 2.5.0 *PROBLEM:* Total Request Count is not growing exponentially *IMPACT:* User is not able to monitor the data correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15309) UI: ability to perform bulk delete host components
[ https://issues.apache.org/jira/browse/AMBARI-15309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-15309: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk 16e04b2ba3eaeedf6d6633b43c6e001593de9198 > UI: ability to perform bulk delete host components > -- > > Key: AMBARI-15309 > URL: https://issues.apache.org/jira/browse/AMBARI-15309 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 3.0.0 > > Attachments: AMBARI-15309.v0.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15309) UI: ability to perform bulk delete host components
[ https://issues.apache.org/jira/browse/AMBARI-15309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-15309: Fix Version/s: (was: 2.5.0) 3.0.0 > UI: ability to perform bulk delete host components > -- > > Key: AMBARI-15309 > URL: https://issues.apache.org/jira/browse/AMBARI-15309 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 3.0.0 > > Attachments: AMBARI-15309.v0.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15309) UI: ability to perform bulk delete host components
[ https://issues.apache.org/jira/browse/AMBARI-15309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-15309: Status: Patch Available (was: Open) > UI: ability to perform bulk delete host components > -- > > Key: AMBARI-15309 > URL: https://issues.apache.org/jira/browse/AMBARI-15309 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-15309.v0.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15309) UI: ability to perform bulk delete host components
[ https://issues.apache.org/jira/browse/AMBARI-15309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-15309: Attachment: AMBARI-15309.v0.patch Local ambari-web test passed. 30014 tests complete (26 seconds) 154 tests pending Manual testing done. > UI: ability to perform bulk delete host components > -- > > Key: AMBARI-15309 > URL: https://issues.apache.org/jira/browse/AMBARI-15309 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.5.0 > > Attachments: AMBARI-15309.v0.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18247) Capacity scheduler's dependent config suggestion is incomprehensible
[ https://issues.apache.org/jira/browse/AMBARI-18247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18247: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk 5dbb43e7ff9fedf9b35718a1980ec70fbf7b0cd2 > Capacity scheduler's dependent config suggestion is incomprehensible > > > Key: AMBARI-18247 > URL: https://issues.apache.org/jira/browse/AMBARI-18247 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18247.v0.patch > > > Dependent configs dialog shows recommended values for capacity scheduler > which is incomprehensible to read. It will be good to breakdown the specific > changes into separate rows. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18257) graphView test case failed in Ambari Web Build on trunk
[
https://issues.apache.org/jira/browse/AMBARI-18257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-18257:
Affects Version/s: (was: trunk)
2.5.0
> graphView test case failed in Ambari Web Build on trunk
> ---
>
> Key: AMBARI-18257
> URL: https://issues.apache.org/jira/browse/AMBARI-18257
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: trunk
>
> Attachments: AMBARI-18257.v0.patch
>
>
> Intermittent test failure
> {code}
> Metrics with name "m1" not found to compute expression
> [91m ✖[0m[31m 2 of 30013 tests failed[0m[90m:[0m
> [0m 1) Ambari Web Unit tests
> test/views/common/widget/graph_widget_view_test App.GraphWidgetView
> #graphView #didInsertElement() setYAxisFormatter should be called:
> [0m[31m TypeError: '<(subclass of App.ChartLinearTimeView):ember61864>'
> is not a function (evaluating 'callback()')
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/javascripts/app.js:179147)[0m[90m
>
> [0m
> [0m 2) Ambari Web Unit tests
> test/views/common/widget/graph_widget_view_test App.GraphWidgetView
> #graphView #didInsertElement() "after each" hook:
> [0m[31m TypeError: 'undefined' is not a function (evaluating
> 'graphView.setYAxisFormatter.restore()')[0m[90m
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/test/javascripts/test.js:108452
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4039
> at next
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4303)
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4307
> at timeslice
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:5279)
> [0m
> npm ERR! Test failed. See above for more details.
> npm ERR! not ok code 0
> {code}
> https://builds.apache.org/job/Ambari-trunk-Commit/5576/ and several others.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18257) graphView test case failed in Ambari Web Build on trunk
[
https://issues.apache.org/jira/browse/AMBARI-18257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436017#comment-15436017
]
Zhe (Joe) Wang commented on AMBARI-18257:
-
Committed to trunk 4ffb4929a2bb0b3260da2babcab815620090e076
> graphView test case failed in Ambari Web Build on trunk
> ---
>
> Key: AMBARI-18257
> URL: https://issues.apache.org/jira/browse/AMBARI-18257
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: trunk
>
> Attachments: AMBARI-18257.v0.patch
>
>
> Intermittent test failure
> {code}
> Metrics with name "m1" not found to compute expression
> [91m ✖[0m[31m 2 of 30013 tests failed[0m[90m:[0m
> [0m 1) Ambari Web Unit tests
> test/views/common/widget/graph_widget_view_test App.GraphWidgetView
> #graphView #didInsertElement() setYAxisFormatter should be called:
> [0m[31m TypeError: '<(subclass of App.ChartLinearTimeView):ember61864>'
> is not a function (evaluating 'callback()')
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/javascripts/app.js:179147)[0m[90m
>
> [0m
> [0m 2) Ambari Web Unit tests
> test/views/common/widget/graph_widget_view_test App.GraphWidgetView
> #graphView #didInsertElement() "after each" hook:
> [0m[31m TypeError: 'undefined' is not a function (evaluating
> 'graphView.setYAxisFormatter.restore()')[0m[90m
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/test/javascripts/test.js:108452
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4039
> at next
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4303)
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4307
> at timeslice
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:5279)
> [0m
> npm ERR! Test failed. See above for more details.
> npm ERR! not ok code 0
> {code}
> https://builds.apache.org/job/Ambari-trunk-Commit/5576/ and several others.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18257) graphView test case failed in Ambari Web Build on trunk
[
https://issues.apache.org/jira/browse/AMBARI-18257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-18257:
Status: Patch Available (was: Open)
> graphView test case failed in Ambari Web Build on trunk
> ---
>
> Key: AMBARI-18257
> URL: https://issues.apache.org/jira/browse/AMBARI-18257
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: trunk
>
> Attachments: AMBARI-18257.v0.patch
>
>
> Intermittent test failure
> {code}
> Metrics with name "m1" not found to compute expression
> [91m ✖[0m[31m 2 of 30013 tests failed[0m[90m:[0m
> [0m 1) Ambari Web Unit tests
> test/views/common/widget/graph_widget_view_test App.GraphWidgetView
> #graphView #didInsertElement() setYAxisFormatter should be called:
> [0m[31m TypeError: '<(subclass of App.ChartLinearTimeView):ember61864>'
> is not a function (evaluating 'callback()')
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/javascripts/app.js:179147)[0m[90m
>
> [0m
> [0m 2) Ambari Web Unit tests
> test/views/common/widget/graph_widget_view_test App.GraphWidgetView
> #graphView #didInsertElement() "after each" hook:
> [0m[31m TypeError: 'undefined' is not a function (evaluating
> 'graphView.setYAxisFormatter.restore()')[0m[90m
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/test/javascripts/test.js:108452
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4039
> at next
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4303)
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4307
> at timeslice
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:5279)
> [0m
> npm ERR! Test failed. See above for more details.
> npm ERR! not ok code 0
> {code}
> https://builds.apache.org/job/Ambari-trunk-Commit/5576/ and several others.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18257) graphView test case failed in Ambari Web Build on trunk
[
https://issues.apache.org/jira/browse/AMBARI-18257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-18257:
Attachment: AMBARI-18257.v0.patch
Modified unit test.
Local ambari-web test passed.
30012 tests complete (27 seconds)
154 tests pending
> graphView test case failed in Ambari Web Build on trunk
> ---
>
> Key: AMBARI-18257
> URL: https://issues.apache.org/jira/browse/AMBARI-18257
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: trunk
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: trunk
>
> Attachments: AMBARI-18257.v0.patch
>
>
> Intermittent test failure
> {code}
> Metrics with name "m1" not found to compute expression
> [91m ✖[0m[31m 2 of 30013 tests failed[0m[90m:[0m
> [0m 1) Ambari Web Unit tests
> test/views/common/widget/graph_widget_view_test App.GraphWidgetView
> #graphView #didInsertElement() setYAxisFormatter should be called:
> [0m[31m TypeError: '<(subclass of App.ChartLinearTimeView):ember61864>'
> is not a function (evaluating 'callback()')
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/javascripts/app.js:179147)[0m[90m
>
> [0m
> [0m 2) Ambari Web Unit tests
> test/views/common/widget/graph_widget_view_test App.GraphWidgetView
> #graphView #didInsertElement() "after each" hook:
> [0m[31m TypeError: 'undefined' is not a function (evaluating
> 'graphView.setYAxisFormatter.restore()')[0m[90m
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/test/javascripts/test.js:108452
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4039
> at next
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4303)
> at
> file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4307
> at timeslice
> (file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:5279)
> [0m
> npm ERR! Test failed. See above for more details.
> npm ERR! not ok code 0
> {code}
> https://builds.apache.org/job/Ambari-trunk-Commit/5576/ and several others.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18257) graphView test case failed in Ambari Web Build on trunk
Zhe (Joe) Wang created AMBARI-18257:
---
Summary: graphView test case failed in Ambari Web Build on trunk
Key: AMBARI-18257
URL: https://issues.apache.org/jira/browse/AMBARI-18257
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: trunk
Reporter: Zhe (Joe) Wang
Assignee: Zhe (Joe) Wang
Fix For: trunk
Intermittent test failure
{code}
Metrics with name "m1" not found to compute expression
[91m ✖[0m[31m 2 of 30013 tests failed[0m[90m:[0m
[0m 1) Ambari Web Unit tests test/views/common/widget/graph_widget_view_test
App.GraphWidgetView #graphView #didInsertElement() setYAxisFormatter should be
called:
[0m[31m TypeError: '<(subclass of App.ChartLinearTimeView):ember61864>'
is not a function (evaluating 'callback()')
(file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/javascripts/app.js:179147)[0m[90m
[0m
[0m 2) Ambari Web Unit tests test/views/common/widget/graph_widget_view_test
App.GraphWidgetView #graphView #didInsertElement() "after each" hook:
[0m[31m TypeError: 'undefined' is not a function (evaluating
'graphView.setYAxisFormatter.restore()')[0m[90m
at
file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/public/test/javascripts/test.js:108452
at
file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4039
at next
(file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4303)
at
file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:4307
at timeslice
(file:///home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-web/node_modules/mocha/mocha.js:5279)
[0m
npm ERR! Test failed. See above for more details.
npm ERR! not ok code 0
{code}
https://builds.apache.org/job/Ambari-trunk-Commit/5576/ and several others.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18247) Capacity scheduler's dependent config suggestion is incomprehensible
[ https://issues.apache.org/jira/browse/AMBARI-18247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18247: Status: Patch Available (was: Open) > Capacity scheduler's dependent config suggestion is incomprehensible > > > Key: AMBARI-18247 > URL: https://issues.apache.org/jira/browse/AMBARI-18247 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18247.v0.patch > > > Dependent configs dialog shows recommended values for capacity scheduler > which is incomprehensible to read. It will be good to breakdown the specific > changes into separate rows. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18247) Capacity scheduler's dependent config suggestion is incomprehensible
[ https://issues.apache.org/jira/browse/AMBARI-18247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18247: Attachment: AMBARI-18247.v0.patch Modified unit test. Local ambari-web test passed. 29244 tests complete (25 seconds) 154 tests pending Manual testing done. > Capacity scheduler's dependent config suggestion is incomprehensible > > > Key: AMBARI-18247 > URL: https://issues.apache.org/jira/browse/AMBARI-18247 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-18247.v0.patch > > > Dependent configs dialog shows recommended values for capacity scheduler > which is incomprehensible to read. It will be good to breakdown the specific > changes into separate rows. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18247) Capacity scheduler's dependent config suggestion is incomprehensible
Zhe (Joe) Wang created AMBARI-18247: --- Summary: Capacity scheduler's dependent config suggestion is incomprehensible Key: AMBARI-18247 URL: https://issues.apache.org/jira/browse/AMBARI-18247 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: trunk Dependent configs dialog shows recommended values for capacity scheduler which is incomprehensible to read. It will be good to breakdown the specific changes into separate rows. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18172) Hive Service check is failing after moving webhcat server
[ https://issues.apache.org/jira/browse/AMBARI-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18172: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 849e28e980951b72665677ddb25dcb02d44e4748 > Hive Service check is failing after moving webhcat server > - > > Key: AMBARI-18172 > URL: https://issues.apache.org/jira/browse/AMBARI-18172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Blocker > Labels: 240RMApproved > Fix For: 2.4.0 > > Attachments: AMBARI-18172.v0.patch, AMBARI-18172.v1.patch > > > Moving of webhcat server should change proxyuser configs for hosts in > core-site for webhcat user in non-kerberozed environment. Not doing so is > causing this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18172) Hive Service check is failing after moving webhcat server
[ https://issues.apache.org/jira/browse/AMBARI-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18172: Attachment: (was: 0insecure_private_key) > Hive Service check is failing after moving webhcat server > - > > Key: AMBARI-18172 > URL: https://issues.apache.org/jira/browse/AMBARI-18172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18172.v0.patch, AMBARI-18172.v1.patch > > > Moving of webhcat server should change proxyuser configs for hosts in > core-site for webhcat user in non-kerberozed environment. Not doing so is > causing this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18172) Hive Service check is failing after moving webhcat server
[ https://issues.apache.org/jira/browse/AMBARI-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18172: Attachment: AMBARI-18172.v1.patch Modified unit test. Local ambari-web test passed. 29933 tests complete (27 seconds) 154 tests pending Manual testing done. > Hive Service check is failing after moving webhcat server > - > > Key: AMBARI-18172 > URL: https://issues.apache.org/jira/browse/AMBARI-18172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Blocker > Fix For: 2.4.0 > > Attachments: 0insecure_private_key, AMBARI-18172.v0.patch, > AMBARI-18172.v1.patch > > > Moving of webhcat server should change proxyuser configs for hosts in > core-site for webhcat user in non-kerberozed environment. Not doing so is > causing this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-18172) Hive Service check is failing after moving webhcat server
[ https://issues.apache.org/jira/browse/AMBARI-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18172: Comment: was deleted (was: Modified unit test. Local ambari-web test passed. 29933 tests complete (27 seconds) 154 tests pending Manual testing done.) > Hive Service check is failing after moving webhcat server > - > > Key: AMBARI-18172 > URL: https://issues.apache.org/jira/browse/AMBARI-18172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Blocker > Fix For: 2.4.0 > > Attachments: 0insecure_private_key, AMBARI-18172.v0.patch > > > Moving of webhcat server should change proxyuser configs for hosts in > core-site for webhcat user in non-kerberozed environment. Not doing so is > causing this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18172) Hive Service check is failing after moving webhcat server
[ https://issues.apache.org/jira/browse/AMBARI-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18172: Attachment: 0insecure_private_key Modified unit test. Local ambari-web test passed. 29933 tests complete (27 seconds) 154 tests pending Manual testing done. > Hive Service check is failing after moving webhcat server > - > > Key: AMBARI-18172 > URL: https://issues.apache.org/jira/browse/AMBARI-18172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Blocker > Fix For: 2.4.0 > > Attachments: 0insecure_private_key, AMBARI-18172.v0.patch > > > Moving of webhcat server should change proxyuser configs for hosts in > core-site for webhcat user in non-kerberozed environment. Not doing so is > causing this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18172) Hive Service check is failing after moving webhcat server
[ https://issues.apache.org/jira/browse/AMBARI-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18172: Status: Patch Available (was: Open) > Hive Service check is failing after moving webhcat server > - > > Key: AMBARI-18172 > URL: https://issues.apache.org/jira/browse/AMBARI-18172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18172.v0.patch > > > Moving of webhcat server should change proxyuser configs for hosts in > core-site for webhcat user in non-kerberozed environment. Not doing so is > causing this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18172) Hive Service check is failing after moving webhcat server
[ https://issues.apache.org/jira/browse/AMBARI-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18172: Attachment: AMBARI-18172.v0.patch Modified unit test. Local ambari-web test passed. 29932 tests complete (27 seconds) 154 tests pending Manual testing done. > Hive Service check is failing after moving webhcat server > - > > Key: AMBARI-18172 > URL: https://issues.apache.org/jira/browse/AMBARI-18172 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-18172.v0.patch > > > Moving of webhcat server should change proxyuser configs for hosts in > core-site for webhcat user in non-kerberozed environment. Not doing so is > causing this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18032) UI:Warning message is not present and "Next button" is enabled when all HDP links is empty on Select Version page
[ https://issues.apache.org/jira/browse/AMBARI-18032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18032: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 4eb3c4f9916d339b13a769455b2151c65f7db9e3 > UI:Warning message is not present and "Next button" is enabled when all HDP > links is empty on Select Version page > - > > Key: AMBARI-18032 > URL: https://issues.apache.org/jira/browse/AMBARI-18032 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-18032.v0.patch > > > STR: > 1) Navigate on select stack page > 2)Remo all HDP urls > Actual result: > Warning message is not present and "Next button" is enabled when all HDP > links is empty on Select Version page > Expected behaviour: > 1) Warning message should appear : "Repository Base URLs of at least one OS > are REQUIRED before you can proceed." > 2) Next button should be disabled while some URLS are not posted for one OS > at least -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18032) UI:Warning message is not present and "Next button" is enabled when all HDP links is empty on Select Version page
[ https://issues.apache.org/jira/browse/AMBARI-18032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18032: Status: Patch Available (was: Open) > UI:Warning message is not present and "Next button" is enabled when all HDP > links is empty on Select Version page > - > > Key: AMBARI-18032 > URL: https://issues.apache.org/jira/browse/AMBARI-18032 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-18032.v0.patch > > > STR: > 1) Navigate on select stack page > 2)Remo all HDP urls > Actual result: > Warning message is not present and "Next button" is enabled when all HDP > links is empty on Select Version page > Expected behaviour: > 1) Warning message should appear : "Repository Base URLs of at least one OS > are REQUIRED before you can proceed." > 2) Next button should be disabled while some URLS are not posted for one OS > at least -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18032) UI:Warning message is not present and "Next button" is enabled when all HDP links is empty on Select Version page
[ https://issues.apache.org/jira/browse/AMBARI-18032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18032: Attachment: AMBARI-18032.v0.patch Modified unit test. Local ambari-web test passed. 29246 tests complete (25 seconds) 154 tests pending Manual testing done. > UI:Warning message is not present and "Next button" is enabled when all HDP > links is empty on Select Version page > - > > Key: AMBARI-18032 > URL: https://issues.apache.org/jira/browse/AMBARI-18032 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-18032.v0.patch > > > STR: > 1) Navigate on select stack page > 2)Remo all HDP urls > Actual result: > Warning message is not present and "Next button" is enabled when all HDP > links is empty on Select Version page > Expected behaviour: > 1) Warning message should appear : "Repository Base URLs of at least one OS > are REQUIRED before you can proceed." > 2) Next button should be disabled while some URLS are not posted for one OS > at least -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18029) Duplicate panels are being shown in Kerberos settings page
[ https://issues.apache.org/jira/browse/AMBARI-18029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-18029: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 eace569bd44f682e43446813f1835f2bcb7fd1f4 > Duplicate panels are being shown in Kerberos settings page > -- > > Key: AMBARI-18029 > URL: https://issues.apache.org/jira/browse/AMBARI-18029 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18029.patch, Screen Shot 2016-08-04 at 4.59.22 > PM.png, test_video_part0.flv > > > Duplicate panels are getting displayed in kerberos settings page. The issue > is seen on both 'General' as well as 'Advanced' tabs. > Steps to reproduce : > 1) Take a secured cluster. > 2) Navigate to kerberos page. > 3) Navigate to 'General' or 'Advanced' tab, intermittently duplicate panels > are being shown. > Since its intermittent, its bit tough to reproduce. Try to navigate to > different links on the page like 'Stack and Versions' or 'Service Accounts' > and comeback to kerberos page. > Try this couple of times and issue should be reproducible. > Attaching the screenshot and video. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18029) Duplicate panels are being shown in Kerberos settings page
[ https://issues.apache.org/jira/browse/AMBARI-18029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408540#comment-15408540 ] Zhe (Joe) Wang commented on AMBARI-18029: - Local ambari-web test passed. 29426 tests complete (25 seconds) 154 tests pending Hadoop QA failure is unrelated to the patch > Duplicate panels are being shown in Kerberos settings page > -- > > Key: AMBARI-18029 > URL: https://issues.apache.org/jira/browse/AMBARI-18029 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-18029.patch, Screen Shot 2016-08-04 at 4.59.22 > PM.png, test_video_part0.flv > > > Duplicate panels are getting displayed in kerberos settings page. The issue > is seen on both 'General' as well as 'Advanced' tabs. > Steps to reproduce : > 1) Take a secured cluster. > 2) Navigate to kerberos page. > 3) Navigate to 'General' or 'Advanced' tab, intermittently duplicate panels > are being shown. > Since its intermittent, its bit tough to reproduce. Try to navigate to > different links on the page like 'Stack and Versions' or 'Service Accounts' > and comeback to kerberos page. > Try this couple of times and issue should be reproducible. > Attaching the screenshot and video. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17936) Log search tab seems to be visible for all user roles
[ https://issues.apache.org/jira/browse/AMBARI-17936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17936: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 176690d9c1cea18d9097fd28d1a2038f1f6ac93f > Log search tab seems to be visible for all user roles > - > > Key: AMBARI-17936 > URL: https://issues.apache.org/jira/browse/AMBARI-17936 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17936.v0.patch > > > Log search tabs (in host details page) must be only visible for service admin > user and above. Right now it is visible to all roles including cluster user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17936) Log search tab seems to be visible for all user roles
[ https://issues.apache.org/jira/browse/AMBARI-17936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17936: Attachment: AMBARI-17936.v0.patch Modified unit test. Local ambari-web test passed. 29414 tests complete (26 seconds) 154 tests pending Manual testing done. > Log search tab seems to be visible for all user roles > - > > Key: AMBARI-17936 > URL: https://issues.apache.org/jira/browse/AMBARI-17936 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17936.v0.patch > > > Log search tabs (in host details page) must be only visible for service admin > user and above. Right now it is visible to all roles including cluster user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17936) Log search tab seems to be visible for all user roles
[ https://issues.apache.org/jira/browse/AMBARI-17936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17936: Status: Patch Available (was: Open) > Log search tab seems to be visible for all user roles > - > > Key: AMBARI-17936 > URL: https://issues.apache.org/jira/browse/AMBARI-17936 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17936.v0.patch > > > Log search tabs (in host details page) must be only visible for service admin > user and above. Right now it is visible to all roles including cluster user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17936) Log search tab seems to be visible for all user roles
Zhe (Joe) Wang created AMBARI-17936: --- Summary: Log search tab seems to be visible for all user roles Key: AMBARI-17936 URL: https://issues.apache.org/jira/browse/AMBARI-17936 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: 2.4.0 Log search tabs (in host details page) must be only visible for service admin user and above. Right now it is visible to all roles including cluster user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17934) UI issue on clicking back while installing a cluster
[ https://issues.apache.org/jira/browse/AMBARI-17934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15396541#comment-15396541 ] Zhe (Joe) Wang commented on AMBARI-17934: - +1 for patch > UI issue on clicking back while installing a cluster > > > Key: AMBARI-17934 > URL: https://issues.apache.org/jira/browse/AMBARI-17934 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17934.patch > > > In the Ambari HDP Install wizard > 1] Go from "Get Started" -> "Select Version" > 2] Remove the debian7 repo and click "Next" > 2] Now click the "Select Version" Page from "Install Options" screen. > Attached screenshot page is displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17907) On AMS collector move the webapp address does not change
[
https://issues.apache.org/jira/browse/AMBARI-17907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-17907:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.4 e7c31f7b0f362c8b70c27c05e688061ae7f341b2
> On AMS collector move the webapp address does not change
>
>
> Key: AMBARI-17907
> URL: https://issues.apache.org/jira/browse/AMBARI-17907
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17907.v0.patch
>
>
> Move collector to a different host. Collector start fails because following
> property is not modified:
> {quote}timeline.metrics.service.webapp.address{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17907) On AMS collector move the webapp address does not change
[
https://issues.apache.org/jira/browse/AMBARI-17907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-17907:
Status: Patch Available (was: Open)
> On AMS collector move the webapp address does not change
>
>
> Key: AMBARI-17907
> URL: https://issues.apache.org/jira/browse/AMBARI-17907
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17907.v0.patch
>
>
> Move collector to a different host. Collector start fails because following
> property is not modified:
> {quote}timeline.metrics.service.webapp.address{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17907) On AMS collector move the webapp address does not change
[
https://issues.apache.org/jira/browse/AMBARI-17907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhe (Joe) Wang updated AMBARI-17907:
Attachment: AMBARI-17907.v0.patch
Modified unit test.
Local ambari-web test passed.
29371 tests complete (25 seconds)
154 tests pending
Manual testing done.
> On AMS collector move the webapp address does not change
>
>
> Key: AMBARI-17907
> URL: https://issues.apache.org/jira/browse/AMBARI-17907
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17907.v0.patch
>
>
> Move collector to a different host. Collector start fails because following
> property is not modified:
> {quote}timeline.metrics.service.webapp.address{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-17907) On AMS collector move the webapp address does not change
Zhe (Joe) Wang created AMBARI-17907:
---
Summary: On AMS collector move the webapp address does not change
Key: AMBARI-17907
URL: https://issues.apache.org/jira/browse/AMBARI-17907
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.2.2
Reporter: Zhe (Joe) Wang
Assignee: Zhe (Joe) Wang
Fix For: 2.4.0
Move collector to a different host. Collector start fails because following
property is not modified:
{quote}timeline.metrics.service.webapp.address{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17865) incorrect text for disabled "Change Password" button
[ https://issues.apache.org/jira/browse/AMBARI-17865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17865: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 661ee4cd72c083814a727a8850f4ac151e07067b > incorrect text for disabled "Change Password" button > -- > > Key: AMBARI-17865 > URL: https://issues.apache.org/jira/browse/AMBARI-17865 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17865.v0.patch > > > Incorrect "users.changePassword" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17865) incorrect text for disabled "Change Password" button
[ https://issues.apache.org/jira/browse/AMBARI-17865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17865: Status: Patch Available (was: Open) > incorrect text for disabled "Change Password" button > -- > > Key: AMBARI-17865 > URL: https://issues.apache.org/jira/browse/AMBARI-17865 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17865.v0.patch > > > Incorrect "users.changePassword" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17865) incorrect text for disabled "Change Password" button
[ https://issues.apache.org/jira/browse/AMBARI-17865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17865: Attachment: AMBARI-17865.v0.patch ambari-admin: Executed 76 of 76 SUCCESS (0.166 secs / 0.381 secs) Manual testing done > incorrect text for disabled "Change Password" button > -- > > Key: AMBARI-17865 > URL: https://issues.apache.org/jira/browse/AMBARI-17865 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-17865.v0.patch > > > Incorrect "users.changePassword" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17865) incorrect text for disabled "Change Password" button
Zhe (Joe) Wang created AMBARI-17865: --- Summary: incorrect text for disabled "Change Password" button Key: AMBARI-17865 URL: https://issues.apache.org/jira/browse/AMBARI-17865 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: 2.4.0 Incorrect "users.changePassword" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17820) UI sometimes stucks while deleting service due to JS error
[
https://issues.apache.org/jira/browse/AMBARI-17820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15386527#comment-15386527
]
Zhe (Joe) Wang commented on AMBARI-17820:
-
+1 for patch
> UI sometimes stucks while deleting service due to JS error
> --
>
> Key: AMBARI-17820
> URL: https://issues.apache.org/jira/browse/AMBARI-17820
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17820.1.patch
>
>
> Patch includes following change:
> {code}
> sourceIds.forEach(function(item, index) {
> if (!dataIds.contains(item)) {
> - source.removeAt(index);
> + var sourceItem = source.findProperty('id',item);
> + source.removeObject(sourceItem);
> }
>});
> {code}
> The issue was because sourceIds array being iterated was assumed to have same
> length as source array whose elements are being conditionally removed.
> The bug was that when condition was satisfied and an element was removed,
> source array became smaller and its elements were shifted left due to element
> removal. This made possibility that on last iteration of the loop if the
> condition to remove element is again satisfied then source array will not
> have element on the index. So source.removeAt(index); will throw no element
> at index exception
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17777) Unexpected behavior on Select Version page
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-1: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 47f4e1c490f569ff93234b17a502331f2d5cae20 > Unexpected behavior on Select Version page > -- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-1.v0.patch > > > STR: > # Go to SelectVersion page > # Clear any input with Base URL (for ex. ubuntu14) > # Click on next button > Expected: input has now red borders and warning message appears below > "Attention: All repo URLs are required before you can proceed." > Actually: Next button became to disabled state. Next page wasn't loaded. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17777) Unexpected behavior on Select Version page
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-1: Status: Patch Available (was: Open) > Unexpected behavior on Select Version page > -- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > Attachments: AMBARI-1.v0.patch > > > STR: > # Go to SelectVersion page > # Clear any input with Base URL (for ex. ubuntu14) > Expected: input has now red borders and warning message appears below > "Attention: All repo URLs are required before you can proceed." > Actually: no red borders and warning message appears > *Then:* > # Click on next button > Expected: error like "No Base URL specified for someOS" > Result: ubuntu14 disappears from OS-list automatically (like after clicking > on remove) and Next button became to disabled state. Next page wasn't loaded. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17777) Unexpected behavior on Select Version page
Zhe (Joe) Wang created AMBARI-1: --- Summary: Unexpected behavior on Select Version page Key: AMBARI-1 URL: https://issues.apache.org/jira/browse/AMBARI-1 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Fix For: 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17777) Unexpected behavior on Select Version page
[ https://issues.apache.org/jira/browse/AMBARI-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-1: Description: STR: # Go to SelectVersion page # Clear any input with Base URL (for ex. ubuntu14) Expected: input has now red borders and warning message appears below "Attention: All repo URLs are required before you can proceed." Actually: no red borders and warning message appears *Then:* # Click on next button Expected: error like "No Base URL specified for someOS" Result: ubuntu14 disappears from OS-list automatically (like after clicking on remove) and Next button became to disabled state. Next page wasn't loaded. > Unexpected behavior on Select Version page > -- > > Key: AMBARI-1 > URL: https://issues.apache.org/jira/browse/AMBARI-1 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang > Fix For: 2.4.0 > > > STR: > # Go to SelectVersion page > # Clear any input with Base URL (for ex. ubuntu14) > Expected: input has now red borders and warning message appears below > "Attention: All repo URLs are required before you can proceed." > Actually: no red borders and warning message appears > *Then:* > # Click on next button > Expected: error like "No Base URL specified for someOS" > Result: ubuntu14 disappears from OS-list automatically (like after clicking > on remove) and Next button became to disabled state. Next page wasn't loaded. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown
[ https://issues.apache.org/jira/browse/AMBARI-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17636: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk f67c9cf3a776dd3a96bacfc44c722fbc44f2ab3e > Service Configs page: can't see all config versions in dropdown > --- > > Key: AMBARI-17636 > URL: https://issues.apache.org/jira/browse/AMBARI-17636 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: trunk > > Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, > AMBARI-17636.v4.patch, bugfix.gif > > > * Go to Service->Configs page (that have more than ~ 30 versions) > * Open versions dropdown > *Result:* > Number of visible versions limited by window height. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown
[ https://issues.apache.org/jira/browse/AMBARI-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17636: Fix Version/s: (was: 2.5.0) trunk > Service Configs page: can't see all config versions in dropdown > --- > > Key: AMBARI-17636 > URL: https://issues.apache.org/jira/browse/AMBARI-17636 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: trunk > > Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, > AMBARI-17636.v4.patch, bugfix.gif > > > * Go to Service->Configs page (that have more than ~ 30 versions) > * Open versions dropdown > *Result:* > Number of visible versions limited by window height. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17636) Service Configs page: can't see all config versions in dropdown
[ https://issues.apache.org/jira/browse/AMBARI-17636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17636: Status: Patch Available (was: Open) > Service Configs page: can't see all config versions in dropdown > --- > > Key: AMBARI-17636 > URL: https://issues.apache.org/jira/browse/AMBARI-17636 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 2.5.0 > > Attachments: AMBARI-17636.v0.patch, AMBARI-17636.v3.patch, > AMBARI-17636.v4.patch, bugfix.gif > > > * Go to Service->Configs page (that have more than ~ 30 versions) > * Open versions dropdown > *Result:* > Number of visible versions limited by window height. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-10908) Usability: ability to perform bulk delete host
[ https://issues.apache.org/jira/browse/AMBARI-10908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-10908: Fix Version/s: (was: 3.0.0) trunk > Usability: ability to perform bulk delete host > -- > > Key: AMBARI-10908 > URL: https://issues.apache.org/jira/browse/AMBARI-10908 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Jeff Sposetti >Assignee: Zhe (Joe) Wang > Fix For: trunk > > Attachments: AMBARI-10908.v0.patch, AMBARI-10908.v1.patch > > > On Hosts page, provide ability to delete hosts in bulk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17598) Permission mismatch b/w 'Cluster user' and 'read only user' from older ambari
[ https://issues.apache.org/jira/browse/AMBARI-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17598: Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.4 9c29d8495fb92806e85d95bc6d2a7e21f86e1b1c > Permission mismatch b/w 'Cluster user' and 'read only user' from older ambari > -- > > Key: AMBARI-17598 > URL: https://issues.apache.org/jira/browse/AMBARI-17598 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17598.v0.patch > > > In ambari 2.2.2 "Show only my widgets" check box was not shown for 'read > only' user. > But in ambari-2.4.0, cluster user is being shown with this particular > checkbox. > Steps to reproduce : > 1) Create a cluster user. > 2) Login as cluster user. > 3) Go to browse widget. > 4) Check that "Show only my widgets" is not shown for cluster user. > Since 'read only user' in ambari 2.2.2 corresponds to the cluster user in > 2.4.0, even the permissions should remain intact. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs
[ https://issues.apache.org/jira/browse/AMBARI-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365345#comment-15365345 ] Zhe (Joe) Wang commented on AMBARI-17285: - [~bhuvnesh2703], let me reach out to [~ncole] tomorrow and get back to you tomorrow. Thank you. > Custom service repos in repoinfo.xml got overwritten by public VDFs > --- > > Key: AMBARI-17285 > URL: https://issues.apache.org/jira/browse/AMBARI-17285 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov > Fix For: 2.4.0 > > > Ambari 2.4 introduced Version Definition Files that break the functionality > of adding a custom service repo, since custom services do not have an entry > in the public VDF. > In the case of HAWQ, the plugin is installed on Ambari host and it adds the > new repo information to the repoinfo.xml of all available stacks on the file > system. Once Ambari cluster creation wizard queries the latest repo info from > the public URLs, it will get the info for all stack repos, but not the custom > ones. > So, the logic should be: > 1. Use default repoinfo (from file system) as the base > 2. Query public VDF, if available > 3. For each entry in public VDF overwrite values in the default repoinfo > 4. Entries in default repoinfo that do not have corresponding entries in VDF > should stay intact > This way custom services can be added via file edit and the latest > information can still be retrieved and applied for the standard stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17598) Permission mismatch b/w 'Cluster user' and 'read only user' from older ambari
[ https://issues.apache.org/jira/browse/AMBARI-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17598: Attachment: AMBARI-17598.v0.patch Local ambari-web test passed. 28944 tests complete (24 seconds) 154 tests pending Manual testing done. > Permission mismatch b/w 'Cluster user' and 'read only user' from older ambari > -- > > Key: AMBARI-17598 > URL: https://issues.apache.org/jira/browse/AMBARI-17598 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17598.v0.patch > > > In ambari 2.2.2 "Show only my widgets" check box was not shown for 'read > only' user. > But in ambari-2.4.0, cluster user is being shown with this particular > checkbox. > Steps to reproduce : > 1) Create a cluster user. > 2) Login as cluster user. > 3) Go to browse widget. > 4) Check that "Show only my widgets" is not shown for cluster user. > Since 'read only user' in ambari 2.2.2 corresponds to the cluster user in > 2.4.0, even the permissions should remain intact. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-17598) Permission mismatch b/w 'Cluster user' and 'read only user' from older ambari
[ https://issues.apache.org/jira/browse/AMBARI-17598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe (Joe) Wang updated AMBARI-17598: Status: Patch Available (was: Open) > Permission mismatch b/w 'Cluster user' and 'read only user' from older ambari > -- > > Key: AMBARI-17598 > URL: https://issues.apache.org/jira/browse/AMBARI-17598 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Zhe (Joe) Wang >Assignee: Zhe (Joe) Wang >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17598.v0.patch > > > In ambari 2.2.2 "Show only my widgets" check box was not shown for 'read > only' user. > But in ambari-2.4.0, cluster user is being shown with this particular > checkbox. > Steps to reproduce : > 1) Create a cluster user. > 2) Login as cluster user. > 3) Go to browse widget. > 4) Check that "Show only my widgets" is not shown for cluster user. > Since 'read only user' in ambari 2.2.2 corresponds to the cluster user in > 2.4.0, even the permissions should remain intact. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-17598) Permission mismatch b/w 'Cluster user' and 'read only user' from older ambari
Zhe (Joe) Wang created AMBARI-17598: --- Summary: Permission mismatch b/w 'Cluster user' and 'read only user' from older ambari Key: AMBARI-17598 URL: https://issues.apache.org/jira/browse/AMBARI-17598 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Zhe (Joe) Wang Assignee: Zhe (Joe) Wang Priority: Critical Fix For: 2.4.0 In ambari 2.2.2 "Show only my widgets" check box was not shown for 'read only' user. But in ambari-2.4.0, cluster user is being shown with this particular checkbox. Steps to reproduce : 1) Create a cluster user. 2) Login as cluster user. 3) Go to browse widget. 4) Check that "Show only my widgets" is not shown for cluster user. Since 'read only user' in ambari 2.2.2 corresponds to the cluster user in 2.4.0, even the permissions should remain intact. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17285) Custom service repos in repoinfo.xml got overwritten by public VDFs
[ https://issues.apache.org/jira/browse/AMBARI-17285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15351575#comment-15351575 ] Zhe (Joe) Wang commented on AMBARI-17285: - Hi [~ncole], I believe for adding custom service to repo, users should provide their own VDF file with added services and urls. We should not do that in Repoinfo.xml any more. Am I right? If so, can you provide [~adenissov] instructions on how to create own VDF file? Thank you. > Custom service repos in repoinfo.xml got overwritten by public VDFs > --- > > Key: AMBARI-17285 > URL: https://issues.apache.org/jira/browse/AMBARI-17285 > Project: Ambari > Issue Type: Bug >Reporter: Alexander Denissov > Fix For: 2.4.0 > > > Ambari 2.4 introduced Version Definition Files that break the functionality > of adding a custom service repo, since custom services do not have an entry > in the public VDF. > In the case of HAWQ, the plugin is installed on Ambari host and it adds the > new repo information to the repoinfo.xml of all available stacks on the file > system. Once Ambari cluster creation wizard queries the latest repo info from > the public URLs, it will get the info for all stack repos, but not the custom > ones. > So, the logic should be: > 1. Use default repoinfo (from file system) as the base > 2. Query public VDF, if available > 3. For each entry in public VDF overwrite values in the default repoinfo > 4. Entries in default repoinfo that do not have corresponding entries in VDF > should stay intact > This way custom services can be added via file edit and the latest > information can still be retrieved and applied for the standard stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
