[jira] [Updated] (AMBARI-21609) Unable to view HDP or HDF stack version.
[ https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21609: -- Attachment: AMBARI-21609.patch > Unable to view HDP or HDF stack version. > > > Key: AMBARI-21609 > URL: https://issues.apache.org/jira/browse/AMBARI-21609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.6.0 > > Attachments: AMBARI-21609.patch > > > The problem is that we get empty "operating_systems" section when the cluster > is installed through installer AND using RedHat Satellite. Blueprint install > or installation without using RedHat Satellite does not have this problem. > The javascript console show an exception after a call to an API endpoint: > app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of > undefined > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21609) Unable to view HDP or HDF stack version.
[ https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21609: -- Status: Patch Available (was: Open) > Unable to view HDP or HDF stack version. > > > Key: AMBARI-21609 > URL: https://issues.apache.org/jira/browse/AMBARI-21609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.6.0 > > Attachments: AMBARI-21609.patch > > > The problem is that we get empty "operating_systems" section when the cluster > is installed through installer AND using RedHat Satellite. Blueprint install > or installation without using RedHat Satellite does not have this problem. > The javascript console show an exception after a call to an API endpoint: > app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of > undefined > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21609) Unable to view HDP or HDF stack version.
[ https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21609: -- Status: Open (was: Patch Available) > Unable to view HDP or HDF stack version. > > > Key: AMBARI-21609 > URL: https://issues.apache.org/jira/browse/AMBARI-21609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.6.0 > > Attachments: AMBARI-21609.patch > > > The problem is that we get empty "operating_systems" section when the cluster > is installed through installer AND using RedHat Satellite. Blueprint install > or installation without using RedHat Satellite does not have this problem. > The javascript console show an exception after a call to an API endpoint: > app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of > undefined > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21609) Unable to view HDP or HDF stack version.
[ https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21609: -- Attachment: (was: AMBARI-21609.patch) > Unable to view HDP or HDF stack version. > > > Key: AMBARI-21609 > URL: https://issues.apache.org/jira/browse/AMBARI-21609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.6.0 > > > The problem is that we get empty "operating_systems" section when the cluster > is installed through installer AND using RedHat Satellite. Blueprint install > or installation without using RedHat Satellite does not have this problem. > The javascript console show an exception after a call to an API endpoint: > app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of > undefined > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21609) Unable to view HDP or HDF stack version.
[ https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21609: -- Attachment: AMBARI-21609.patch > Unable to view HDP or HDF stack version. > > > Key: AMBARI-21609 > URL: https://issues.apache.org/jira/browse/AMBARI-21609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.6.0 > > Attachments: AMBARI-21609.patch > > > The problem is that we get empty "operating_systems" section when the cluster > is installed through installer AND using RedHat Satellite. Blueprint install > or installation without using RedHat Satellite does not have this problem. > The javascript console show an exception after a call to an API endpoint: > app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of > undefined > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21609) Unable to view HDP or HDF stack version.
[ https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21609: -- Attachment: AMBARI-21609.patch > Unable to view HDP or HDF stack version. > > > Key: AMBARI-21609 > URL: https://issues.apache.org/jira/browse/AMBARI-21609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.6.0 > > > The problem is that we get empty "operating_systems" section when the cluster > is installed through installer AND using RedHat Satellite. Blueprint install > or installation without using RedHat Satellite does not have this problem. > The javascript console show an exception after a call to an API endpoint: > app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of > undefined > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21609) Unable to view HDP or HDF stack version.
[ https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21609: -- Attachment: (was: AMBARI-21609.patch) > Unable to view HDP or HDF stack version. > > > Key: AMBARI-21609 > URL: https://issues.apache.org/jira/browse/AMBARI-21609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.6.0 > > > The problem is that we get empty "operating_systems" section when the cluster > is installed through installer AND using RedHat Satellite. Blueprint install > or installation without using RedHat Satellite does not have this problem. > The javascript console show an exception after a call to an API endpoint: > app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of > undefined > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21609) Unable to view HDP or HDF stack version.
[ https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21609: -- Attachment: (was: AMBARI-21609.patch) > Unable to view HDP or HDF stack version. > > > Key: AMBARI-21609 > URL: https://issues.apache.org/jira/browse/AMBARI-21609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.6.0 > > > The problem is that we get empty "operating_systems" section when the cluster > is installed through installer AND using RedHat Satellite. Blueprint install > or installation without using RedHat Satellite does not have this problem. > The javascript console show an exception after a call to an API endpoint: > app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of > undefined > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21609) Unable to view HDP or HDF stack version.
[ https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21609: -- Status: Patch Available (was: Open) > Unable to view HDP or HDF stack version. > > > Key: AMBARI-21609 > URL: https://issues.apache.org/jira/browse/AMBARI-21609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.6.0 > > Attachments: AMBARI-21609.patch > > > The problem is that we get empty "operating_systems" section when the cluster > is installed through installer AND using RedHat Satellite. Blueprint install > or installation without using RedHat Satellite does not have this problem. > The javascript console show an exception after a call to an API endpoint: > app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of > undefined > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21609) Unable to view HDP or HDF stack version.
[ https://issues.apache.org/jira/browse/AMBARI-21609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21609: -- Attachment: AMBARI-21609.patch > Unable to view HDP or HDF stack version. > > > Key: AMBARI-21609 > URL: https://issues.apache.org/jira/browse/AMBARI-21609 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.6.0 > > Attachments: AMBARI-21609.patch > > > The problem is that we get empty "operating_systems" section when the cluster > is installed through installer AND using RedHat Satellite. Blueprint install > or installation without using RedHat Satellite does not have this problem. > The javascript console show an exception after a call to an API endpoint: > app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of > undefined > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at Class. > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) > at Array.forEach (native) > at Class.map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) > at Class.newFunc as map > (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) > at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21609) Unable to view HDP or HDF stack version.
Richard Zang created AMBARI-21609: - Summary: Unable to view HDP or HDF stack version. Key: AMBARI-21609 URL: https://issues.apache.org/jira/browse/AMBARI-21609 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.2 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.6.0 The problem is that we get empty "operating_systems" section when the cluster is installed through installer AND using RedHat Satellite. Blueprint install or installation without using RedHat Satellite does not have this problem. The javascript console show an exception after a call to an API endpoint: app.js:56537 Uncaught TypeError: Cannot read property 'OperatingSystems' of undefined at Class. (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56537:64) at Array.forEach (native) at Class.map (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:56491:18) at Class.newFunc as map (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) at Class. (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57996:33) at Array.forEach (native) at Class.map (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:57966:18) at Class.newFunc as map (https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/vendor.js:2627:16) at https://mtl‐hdfmgmt11x.cnppd.lab:8443/javascripts/app.js:179795:18 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21371) Adding ranger failed when user has custom properties
[ https://issues.apache.org/jira/browse/AMBARI-21371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21371: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 777434efbc8159f12800eda711258eea11cefcd5 > Adding ranger failed when user has custom properties > > > Key: AMBARI-21371 > URL: https://issues.apache.org/jira/browse/AMBARI-21371 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21371.patch > > > Add Ranger service failed when custom core-site has the following properties > defined: > hadoop.proxyuser.root.groups > hadoop.proxyuser.root.hosts > JS NPE after clicking next on service configuration step, unselect all > recommended settings and click OK. > app.js:67983 Uncaught TypeError: Cannot read property 'propertyDependsOn' of > undefined > at Class. > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67983:123) > at Array.forEach (native) > at Class.undoRedoRecommended > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67970:24) > at Class.onSaveRecommendedPopup > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67957:10) > at http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67939:14 > at Class.onPrimary > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:205542:20) > at Class.newFunc as onPrimary > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:2608:16) > at handler > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:21208:35) > at HTMLButtonElement. > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:13000:16) > at HTMLDivElement.dispatch > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:107:4816) > when we get a "delete property" recommendation on a custom property and we > unselect it in the popup window, we will trigger this NPE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21371) Adding ranger failed when user has custom properties
[ https://issues.apache.org/jira/browse/AMBARI-21371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21371: -- Attachment: AMBARI-21371.patch > Adding ranger failed when user has custom properties > > > Key: AMBARI-21371 > URL: https://issues.apache.org/jira/browse/AMBARI-21371 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21371.patch > > > Add Ranger service failed when custom core-site has the following properties > defined: > hadoop.proxyuser.root.groups > hadoop.proxyuser.root.hosts > JS NPE after clicking next on service configuration step, unselect all > recommended settings and click OK. > app.js:67983 Uncaught TypeError: Cannot read property 'propertyDependsOn' of > undefined > at Class. > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67983:123) > at Array.forEach (native) > at Class.undoRedoRecommended > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67970:24) > at Class.onSaveRecommendedPopup > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67957:10) > at http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67939:14 > at Class.onPrimary > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:205542:20) > at Class.newFunc as onPrimary > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:2608:16) > at handler > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:21208:35) > at HTMLButtonElement. > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:13000:16) > at HTMLDivElement.dispatch > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:107:4816) > when we get a "delete property" recommendation on a custom property and we > unselect it in the popup window, we will trigger this NPE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21371) Adding ranger failed when user has custom properties
[ https://issues.apache.org/jira/browse/AMBARI-21371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21371: -- Status: Patch Available (was: Open) > Adding ranger failed when user has custom properties > > > Key: AMBARI-21371 > URL: https://issues.apache.org/jira/browse/AMBARI-21371 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21371.patch > > > Add Ranger service failed when custom core-site has the following properties > defined: > hadoop.proxyuser.root.groups > hadoop.proxyuser.root.hosts > JS NPE after clicking next on service configuration step, unselect all > recommended settings and click OK. > app.js:67983 Uncaught TypeError: Cannot read property 'propertyDependsOn' of > undefined > at Class. > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67983:123) > at Array.forEach (native) > at Class.undoRedoRecommended > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67970:24) > at Class.onSaveRecommendedPopup > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67957:10) > at http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67939:14 > at Class.onPrimary > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:205542:20) > at Class.newFunc as onPrimary > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:2608:16) > at handler > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:21208:35) > at HTMLButtonElement. > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:13000:16) > at HTMLDivElement.dispatch > (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:107:4816) > when we get a "delete property" recommendation on a custom property and we > unselect it in the popup window, we will trigger this NPE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21371) Adding ranger failed when user has custom properties
Richard Zang created AMBARI-21371: - Summary: Adding ranger failed when user has custom properties Key: AMBARI-21371 URL: https://issues.apache.org/jira/browse/AMBARI-21371 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.2 Reporter: Richard Zang Assignee: Richard Zang Priority: Critical Fix For: 2.5.2 Add Ranger service failed when custom core-site has the following properties defined: hadoop.proxyuser.root.groups hadoop.proxyuser.root.hosts JS NPE after clicking next on service configuration step, unselect all recommended settings and click OK. app.js:67983 Uncaught TypeError: Cannot read property 'propertyDependsOn' of undefined at Class. (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67983:123) at Array.forEach (native) at Class.undoRedoRecommended (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67970:24) at Class.onSaveRecommendedPopup (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67957:10) at http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:67939:14 at Class.onPrimary (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/app.js:205542:20) at Class.newFunc as onPrimary (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:2608:16) at handler (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:21208:35) at HTMLButtonElement. (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:13000:16) at HTMLDivElement.dispatch (http://horton-amb.vip.lvs.paypal.com:8080/javascripts/vendor.js:107:4816) when we get a "delete property" recommendation on a custom property and we unselect it in the popup window, we will trigger this NPE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21324) Ambari 3.0: Outstanding Services page issues
[ https://issues.apache.org/jira/browse/AMBARI-21324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21324: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk 6305fb6ab9839f20eb871eca5d933e6590f20981 > Ambari 3.0: Outstanding Services page issues > > > Key: AMBARI-21324 > URL: https://issues.apache.org/jira/browse/AMBARI-21324 > Project: Ambari > Issue Type: Task > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 3.0.0 > > Attachments: AMBARI-21324.patch, services_page.png > > > Following are the outstanding issues with Services page: > Remove QuickLinks- relocate them on the page > Implement panel design guidelines > Design Service Configuration page- Remove the history timestamps > Design Heatmap page > Can we make it responsive? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21248) Exception needs to be handled properly for mail alert
[
https://issues.apache.org/jira/browse/AMBARI-21248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-21248:
--
Priority: Critical (was: Major)
> Exception needs to be handled properly for mail alert
> -
>
> Key: AMBARI-21248
> URL: https://issues.apache.org/jira/browse/AMBARI-21248
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Richard Zang
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.5.2
>
>
> In org.apache.ambari.server.state.services.AlertNoticeDispatchService, we
> have below code snippet:
> {code}
> ...
> protected void runOneIteration() throws Exception {
> …
> String targetType = target.getNotificationType();
> NotificationDispatcher dispatcher =
> m_dispatchFactory.getDispatcher(targetType);
> …
> if (dispatcher.isDigestSupported()) {
> ...
> {code}
> If the database has a change to AlertTargetEntity's targetType column
> (unlikely but let's assume it happened), then dispatcher can be null and the
> subsequent if clause will throw an exception. In
> https://github.com/google/guava/blob/master/guava/src/com/google/common/util/concurrent/AbstractScheduledService.java,
> we see that the exception may happen silently since shutDown() and
> notifyFailed() does not log anything.
> ...
> {code}
> class Task implements Runnable {
> @Override
> public void run() {
> lock.lock();
> try {
> if (runningTask.isCancelled()) { // task may have been cancelled
> while blocked on the lock. return; }
> AbstractScheduledService.this.runOneIteration();
> } catch (Throwable t) {
> try {
> shutDown();
> } catch (Exception ignored) {
> logger.log(Level.WARNING, "Error while attempting to shut
> down the service after failure.", ignored);
> }
> notifyFailed(t);
> runningTask.cancel(false); // prevent future invocations.
> } finally {
> lock.unlock();
> }
> }
> }
> }
> {code}
> So, runOneIteration will shutdown the scheduler if it hits an uncaught
> exception. We should wrap a try/catch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21248) Exception needs to be handled properly for mail alert
Richard Zang created AMBARI-21248:
-
Summary: Exception needs to be handled properly for mail alert
Key: AMBARI-21248
URL: https://issues.apache.org/jira/browse/AMBARI-21248
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.2
Reporter: Richard Zang
Assignee: Dmytro Sen
Fix For: 2.5.2
In org.apache.ambari.server.state.services.AlertNoticeDispatchService, we have
below code snippet:
{code}
...
protected void runOneIteration() throws Exception {
…
String targetType = target.getNotificationType();
NotificationDispatcher dispatcher =
m_dispatchFactory.getDispatcher(targetType);
…
if (dispatcher.isDigestSupported()) {
...
{code}
If the database has a change to AlertTargetEntity's targetType column (unlikely
but let's assume it happened), then dispatcher can be null and the subsequent
if clause will throw an exception. In
https://github.com/google/guava/blob/master/guava/src/com/google/common/util/concurrent/AbstractScheduledService.java,
we see that the exception may happen silently since shutDown() and
notifyFailed() does not log anything.
...
{code}
class Task implements Runnable {
@Override
public void run() {
lock.lock();
try {
if (runningTask.isCancelled()) { // task may have been cancelled
while blocked on the lock. return; }
AbstractScheduledService.this.runOneIteration();
} catch (Throwable t) {
try {
shutDown();
} catch (Exception ignored) {
logger.log(Level.WARNING, "Error while attempting to shut
down the service after failure.", ignored);
}
notifyFailed(t);
runningTask.cancel(false); // prevent future invocations.
} finally {
lock.unlock();
}
}
}
}
{code}
So, runOneIteration will shutdown the scheduler if it hits an uncaught
exception. We should wrap a try/catch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21123) Part Two: Specify the script directly in alert target for script-based alert dispatchers
[ https://issues.apache.org/jira/browse/AMBARI-21123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21123: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk 62f4432cc35e39a8fdd7540e6cfc4f5edbac19cb > Part Two: Specify the script directly in alert target for script-based alert > dispatchers > > > Key: AMBARI-21123 > URL: https://issues.apache.org/jira/browse/AMBARI-21123 > Project: Ambari > Issue Type: Technical task > Components: alerts, ambari-web >Affects Versions: trunk >Reporter: Yao Lei >Assignee: Yao Lei > Fix For: 3.0.0 > > Attachments: AMBARI-21123.patch, script_alert_notification_1.png, > script_alert_notification_2.png > > > *Web Codes Part* > This patch amis to support creating alert target that inclueds property > *ambari.dispatch-property.script.filename* on web UI -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21205) Make ToggleKerberos and AddDeleteService experimental features
[ https://issues.apache.org/jira/browse/AMBARI-21205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21205: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 > Make ToggleKerberos and AddDeleteService experimental features > -- > > Key: AMBARI-21205 > URL: https://issues.apache.org/jira/browse/AMBARI-21205 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0, 2.5.0 >Reporter: Duc Anh Le >Assignee: Duc Anh Le > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-21205_1.patch, AMBARI-21205.patch > > > Toggling Kerberos and Adding/Deleting Services might not be supported for > some cloud environments (e.g. Azure). This Jira enables the ability to make > these features experimental in those environments. These features are still > enabled by default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-21205) Make ToggleKerberos and AddDeleteService experimental features
[ https://issues.apache.org/jira/browse/AMBARI-21205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043613#comment-16043613 ] Richard Zang edited comment on AMBARI-21205 at 6/8/17 11:22 PM: Committed to trunk and 2.5 57bb1365e414c1f110d2d142fa198fb8e043af95 was (Author: rzang): Committed to trunk and 2.5 > Make ToggleKerberos and AddDeleteService experimental features > -- > > Key: AMBARI-21205 > URL: https://issues.apache.org/jira/browse/AMBARI-21205 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0, 2.5.0 >Reporter: Duc Anh Le >Assignee: Duc Anh Le > Fix For: 3.0.0, 2.5.0 > > Attachments: AMBARI-21205_1.patch, AMBARI-21205.patch > > > Toggling Kerberos and Adding/Deleting Services might not be supported for > some cloud environments (e.g. Azure). This Jira enables the ability to make > these features experimental in those environments. These features are still > enabled by default. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21082) Ambari 3.0: Outstanding wizard issues
[ https://issues.apache.org/jira/browse/AMBARI-21082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21082: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk 9415478dca03caf7f55ba21e8f00d954dc117757 > Ambari 3.0: Outstanding wizard issues > - > > Key: AMBARI-21082 > URL: https://issues.apache.org/jira/browse/AMBARI-21082 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 3.0.0 > > Attachments: AMBARI-21082.patch > > > On Ambari 3.0.0, the following are issues related to wizard: > The step number indicator is not center-aligned. Each step number is > positioned inside of a circle, and should always be centered in the circle. > This issue happened when you do command +/- to resize browser window view. > Install wizard step 4, should be able to select the service on clicking > anywhere within the row. Currently you can select the service ONLY clicking > on the checkbox. This is a regression from 2.5 > In install wizard, page footer was in wrong position. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21082) Ambari 3.0: Outstanding wizard issues
[ https://issues.apache.org/jira/browse/AMBARI-21082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21082: -- Status: Patch Available (was: Open) > Ambari 3.0: Outstanding wizard issues > - > > Key: AMBARI-21082 > URL: https://issues.apache.org/jira/browse/AMBARI-21082 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 3.0.0 > > Attachments: AMBARI-21082.patch > > > On Ambari 3.0.0, the following are issues related to wizard: > The step number indicator is not center-aligned. Each step number is > positioned inside of a circle, and should always be centered in the circle. > This issue happened when you do command +/- to resize browser window view. > Install wizard step 4, should be able to select the service on clicking > anywhere within the row. Currently you can select the service ONLY clicking > on the checkbox. This is a regression from 2.5 > In install wizard, page footer was in wrong position. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21082) Ambari 3.0: Outstanding wizard issues
[ https://issues.apache.org/jira/browse/AMBARI-21082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-21082: -- Attachment: AMBARI-21082.patch > Ambari 3.0: Outstanding wizard issues > - > > Key: AMBARI-21082 > URL: https://issues.apache.org/jira/browse/AMBARI-21082 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 3.0.0 > > Attachments: AMBARI-21082.patch > > > On Ambari 3.0.0, the following are issues related to wizard: > The step number indicator is not center-aligned. Each step number is > positioned inside of a circle, and should always be centered in the circle. > This issue happened when you do command +/- to resize browser window view. > Install wizard step 4, should be able to select the service on clicking > anywhere within the row. Currently you can select the service ONLY clicking > on the checkbox. This is a regression from 2.5 > In install wizard, page footer was in wrong position. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-21082) Ambari 3.0: Outstanding wizard issues
Richard Zang created AMBARI-21082: - Summary: Ambari 3.0: Outstanding wizard issues Key: AMBARI-21082 URL: https://issues.apache.org/jira/browse/AMBARI-21082 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 3.0.0 On Ambari 3.0.0, the following are issues related to wizard: The step number indicator is not center-aligned. Each step number is positioned inside of a circle, and should always be centered in the circle. This issue happened when you do command +/- to resize browser window view. Install wizard step 4, should be able to select the service on clicking anywhere within the row. Currently you can select the service ONLY clicking on the checkbox. This is a regression from 2.5 In install wizard, page footer was in wrong position. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20897) JDBC Driver Class and URL not updated automatically while selecting each database type
[ https://issues.apache.org/jira/browse/AMBARI-20897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15989608#comment-15989608 ] Richard Zang commented on AMBARI-20897: --- +1 for patch > JDBC Driver Class and URL not updated automatically while selecting each > database type > -- > > Key: AMBARI-20897 > URL: https://issues.apache.org/jira/browse/AMBARI-20897 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Xi Wang >Assignee: Xi Wang >Priority: Blocker > Fix For: 2.5.1 > > Attachments: AMBARI-20897-branch-2.5.patch > > > On selecting each database type, the JDBC Driver Class and URL should be > updated automatically. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20896) Provide ability to visualize per cluster data from Grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-20896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang resolved AMBARI-20896. --- Resolution: Fixed Committed to trunk and 2.5 7d1850fd3b3d9d476aa9641ac41957caf61925bc > Provide ability to visualize per cluster data from Grafana dashboards > - > > Key: AMBARI-20896 > URL: https://issues.apache.org/jira/browse/AMBARI-20896 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20896.patch > > > Provide ability to visualize per cluster data from Grafana dashboards -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20896) Provide ability to visualize per cluster data from Grafana dashboards
[ https://issues.apache.org/jira/browse/AMBARI-20896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20896: -- Attachment: AMBARI-20896.patch > Provide ability to visualize per cluster data from Grafana dashboards > - > > Key: AMBARI-20896 > URL: https://issues.apache.org/jira/browse/AMBARI-20896 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20896.patch > > > Provide ability to visualize per cluster data from Grafana dashboards -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20896) Provide ability to visualize per cluster data from Grafana dashboards
Richard Zang created AMBARI-20896: - Summary: Provide ability to visualize per cluster data from Grafana dashboards Key: AMBARI-20896 URL: https://issues.apache.org/jira/browse/AMBARI-20896 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.1 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.1 Provide ability to visualize per cluster data from Grafana dashboards -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20826) HIVE "Quick Links" section showing Graphana related quicklinks when Graphana is not installed
[ https://issues.apache.org/jira/browse/AMBARI-20826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20826: -- Status: Patch Available (was: Open) > HIVE "Quick Links" section showing Graphana related quicklinks when Graphana > is not installed > - > > Key: AMBARI-20826 > URL: https://issues.apache.org/jira/browse/AMBARI-20826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-20826.patch > > > Cluster doesn't include either Grafana or HSI but HIVE "Quick Links" show > shows these two links. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20826) HIVE "Quick Links" section showing Graphana related quicklinks when Graphana is not installed
[ https://issues.apache.org/jira/browse/AMBARI-20826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20826: -- Attachment: AMBARI-20826.patch > HIVE "Quick Links" section showing Graphana related quicklinks when Graphana > is not installed > - > > Key: AMBARI-20826 > URL: https://issues.apache.org/jira/browse/AMBARI-20826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.1 > > Attachments: AMBARI-20826.patch > > > Cluster doesn't include either Grafana or HSI but HIVE "Quick Links" show > shows these two links. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20826) HIVE "Quick Links" section showing Graphana related quicklinks when Graphana is not installed
Richard Zang created AMBARI-20826: - Summary: HIVE "Quick Links" section showing Graphana related quicklinks when Graphana is not installed Key: AMBARI-20826 URL: https://issues.apache.org/jira/browse/AMBARI-20826 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Priority: Critical Fix For: 2.5.1 Cluster doesn't include either Grafana or HSI but HIVE "Quick Links" show shows these two links. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20738) Cannot add repo for additional OS to an existing HDP version
[ https://issues.apache.org/jira/browse/AMBARI-20738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20738: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 7bb94a010dddb0574f5dad4f3a44fb503bc3a2fb > Cannot add repo for additional OS to an existing HDP version > > > Key: AMBARI-20738 > URL: https://issues.apache.org/jira/browse/AMBARI-20738 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20738.patch > > > When trying to add a repo for rhel7, to an already registered HDP version > that only has a repo for rhel6, I get a JS error when trying to click Save. > STR > Install a cluster with HDP 2.6 - that only has a rhel6 repo defined (remove > all others during install). > Post install try to add a rhel7 repo. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20738) Cannot add repo for additional OS to an existing HDP version
[ https://issues.apache.org/jira/browse/AMBARI-20738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20738: -- Status: Patch Available (was: Open) > Cannot add repo for additional OS to an existing HDP version > > > Key: AMBARI-20738 > URL: https://issues.apache.org/jira/browse/AMBARI-20738 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20738.patch > > > When trying to add a repo for rhel7, to an already registered HDP version > that only has a repo for rhel6, I get a JS error when trying to click Save. > STR > Install a cluster with HDP 2.6 - that only has a rhel6 repo defined (remove > all others during install). > Post install try to add a rhel7 repo. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20738) Cannot add repo for additional OS to an existing HDP version
[ https://issues.apache.org/jira/browse/AMBARI-20738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20738: -- Attachment: AMBARI-20738.patch > Cannot add repo for additional OS to an existing HDP version > > > Key: AMBARI-20738 > URL: https://issues.apache.org/jira/browse/AMBARI-20738 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20738.patch > > > When trying to add a repo for rhel7, to an already registered HDP version > that only has a repo for rhel6, I get a JS error when trying to click Save. > STR > Install a cluster with HDP 2.6 - that only has a rhel6 repo defined (remove > all others during install). > Post install try to add a rhel7 repo. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert dispatch targets for script-based alert dispatchers by web wizard instead of command line
[
https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-18423:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk 68b7b56479dbc22d16e96570e27616a59c96a98a
> Support creating/editing alert dispatch targets for script-based alert
> dispatchers by web wizard instead of command line
>
>
> Key: AMBARI-18423
> URL: https://issues.apache.org/jira/browse/AMBARI-18423
> Project: Ambari
> Issue Type: Task
> Components: alerts, ambari-web
>Affects Versions: 3.0.0
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: alert_script_target_1.png, alert_script_target_2.png,
> alert_script_target_3.png, AMBARI-18423_1.patch, AMBARI-18423_2.patch,
> AMBARI-18423_3.patch
>
>
> Ambari now support creating/editing three kinds of alert dispatch targets by
> web wizard, including EMAIL,SNMP,Custom SNMP.
> If we want to create another kind of alert dispatch target ALERT_SCRIPT for
> script-based alert dispatcher,we have to execute a command manually like
> following:
> {code}
> POST api/v1/alert_targets
>
> {
> "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": true
> }
> }
> {code}
> or
> {code}
> POST api/v1/alert_targets
> {
> "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
> "ambari.dispatch-property.script":
> "com.mycompany.dispatch.syslog.script"
> }
> }
> }
> {code}
> More details, please see
> https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0
> We should do this by web wizard rather than command line, which will lead
> to more convenience
> We think it is really helpeful for us when using script-based alert
> dispatcher.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert dispatch targets for script-based alert dispatchers by web wizard instead of command line
[
https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-18423:
--
Affects Version/s: (was: trunk)
3.0.0
Fix Version/s: (was: trunk)
3.0.0
> Support creating/editing alert dispatch targets for script-based alert
> dispatchers by web wizard instead of command line
>
>
> Key: AMBARI-18423
> URL: https://issues.apache.org/jira/browse/AMBARI-18423
> Project: Ambari
> Issue Type: Improvement
> Components: alerts, ambari-web
>Affects Versions: 3.0.0
>Reporter: Yao Lei
>Assignee: Yao Lei
>Priority: Minor
> Fix For: 3.0.0
>
> Attachments: alert_script_target_1.png, alert_script_target_2.png,
> alert_script_target_3.png, AMBARI-18423_1.patch, AMBARI-18423_2.patch
>
>
> Ambari now support creating/editing three kinds of alert dispatch targets by
> web wizard, including EMAIL,SNMP,Custom SNMP.
> If we want to create another kind of alert dispatch target ALERT_SCRIPT for
> script-based alert dispatcher,we have to execute a command manually like
> following:
> {code}
> POST api/v1/alert_targets
>
> {
> "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": true
> }
> }
> {code}
> or
> {code}
> POST api/v1/alert_targets
> {
> "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
> "ambari.dispatch-property.script":
> "com.mycompany.dispatch.syslog.script"
> }
> }
> }
> {code}
> More details, please see
> https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0
> We should do this by web wizard rather than command line, which will lead
> to more convenience
> We think it is really helpeful for us when using script-based alert
> dispatcher.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-18423) Support creating/editing alert dispatch targets for script-based alert dispatchers by web wizard instead of command line
[
https://issues.apache.org/jira/browse/AMBARI-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-18423:
--
Priority: Major (was: Minor)
Issue Type: Task (was: Improvement)
> Support creating/editing alert dispatch targets for script-based alert
> dispatchers by web wizard instead of command line
>
>
> Key: AMBARI-18423
> URL: https://issues.apache.org/jira/browse/AMBARI-18423
> Project: Ambari
> Issue Type: Task
> Components: alerts, ambari-web
>Affects Versions: 3.0.0
>Reporter: Yao Lei
>Assignee: Yao Lei
> Fix For: 3.0.0
>
> Attachments: alert_script_target_1.png, alert_script_target_2.png,
> alert_script_target_3.png, AMBARI-18423_1.patch, AMBARI-18423_2.patch
>
>
> Ambari now support creating/editing three kinds of alert dispatch targets by
> web wizard, including EMAIL,SNMP,Custom SNMP.
> If we want to create another kind of alert dispatch target ALERT_SCRIPT for
> script-based alert dispatcher,we have to execute a command manually like
> following:
> {code}
> POST api/v1/alert_targets
>
> {
> "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": true
> }
> }
> {code}
> or
> {code}
> POST api/v1/alert_targets
> {
> "AlertTarget": {
> "name": "syslogger",
> "description": "Syslog Target",
> "notification_type": "ALERT_SCRIPT",
> "global": false,
> "groups":[1,3]
> "alert_states":["WARNING","CRITICAL","UNKNOWN"],
> "properties": {
> "ambari.dispatch-property.script":
> "com.mycompany.dispatch.syslog.script"
> }
> }
> }
> {code}
> More details, please see
> https://cwiki.apache.org/confluence/display/AMBARI/Creating+a+Script-based+Alert+Dispatcher+-+2.4.0
> We should do this by web wizard rather than command line, which will lead
> to more convenience
> We think it is really helpeful for us when using script-based alert
> dispatcher.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20738) Cannot add repo for additional OS to an existing HDP version
Richard Zang created AMBARI-20738: - Summary: Cannot add repo for additional OS to an existing HDP version Key: AMBARI-20738 URL: https://issues.apache.org/jira/browse/AMBARI-20738 Project: Ambari Issue Type: Bug Components: ambari-admin Affects Versions: 2.5.1 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.1 When trying to add a repo for rhel7, to an already registered HDP version that only has a repo for rhel6, I get a JS error when trying to click Save. STR Install a cluster with HDP 2.6 - that only has a rhel6 repo defined (remove all others during install). Post install try to add a rhel7 repo. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20700) UI should use the URL as-given by the backend
[ https://issues.apache.org/jira/browse/AMBARI-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20700: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 7643475cd058711f9c6b07c8dcf1c04560dc49d1 > UI should use the URL as-given by the backend > - > > Key: AMBARI-20700 > URL: https://issues.apache.org/jira/browse/AMBARI-20700 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20700.patch > > > The UI should be using repositories based on VDF exactly as the backend is > presenting them. There should be no need to assume that HDP and HDP-UTILS are > always going to be there. > Other developers have reported that using their own VDF also does not change > the base URL to what is defined in the VDF. > Any fixes made should be consistent between the installer and the Admin view > that manages repositories. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20700) UI should use the URL as-given by the backend
[ https://issues.apache.org/jira/browse/AMBARI-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20700: -- Attachment: AMBARI-20700.patch > UI should use the URL as-given by the backend > - > > Key: AMBARI-20700 > URL: https://issues.apache.org/jira/browse/AMBARI-20700 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20700.patch > > > The UI should be using repositories based on VDF exactly as the backend is > presenting them. There should be no need to assume that HDP and HDP-UTILS are > always going to be there. > Other developers have reported that using their own VDF also does not change > the base URL to what is defined in the VDF. > Any fixes made should be consistent between the installer and the Admin view > that manages repositories. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20700) UI should use the URL as-given by the backend
[ https://issues.apache.org/jira/browse/AMBARI-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20700: -- Status: Patch Available (was: Open) > UI should use the URL as-given by the backend > - > > Key: AMBARI-20700 > URL: https://issues.apache.org/jira/browse/AMBARI-20700 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20700.patch > > > The UI should be using repositories based on VDF exactly as the backend is > presenting them. There should be no need to assume that HDP and HDP-UTILS are > always going to be there. > Other developers have reported that using their own VDF also does not change > the base URL to what is defined in the VDF. > Any fixes made should be consistent between the installer and the Admin view > that manages repositories. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20700) UI should use the URL as-given by the backend
[ https://issues.apache.org/jira/browse/AMBARI-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang reassigned AMBARI-20700: - Assignee: Richard Zang Affects Version/s: 2.5.1 Fix Version/s: 2.5.1 Component/s: ambari-web > UI should use the URL as-given by the backend > - > > Key: AMBARI-20700 > URL: https://issues.apache.org/jira/browse/AMBARI-20700 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > > The UI should be using repositories based on VDF exactly as the backend is > presenting them. There should be no need to assume that HDP and HDP-UTILS are > always going to be there. > Other developers have reported that using their own VDF also does not change > the base URL to what is defined in the VDF. > Any fixes made should be consistent between the installer and the Admin view > that manages repositories. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20700) UI should use the URL as-given by the backend
Richard Zang created AMBARI-20700: - Summary: UI should use the URL as-given by the backend Key: AMBARI-20700 URL: https://issues.apache.org/jira/browse/AMBARI-20700 Project: Ambari Issue Type: Bug Reporter: Richard Zang The UI should be using repositories based on VDF exactly as the backend is presenting them. There should be no need to assume that HDP and HDP-UTILS are always going to be there. Other developers have reported that using their own VDF also does not change the base URL to what is defined in the VDF. Any fixes made should be consistent between the installer and the Admin view that manages repositories. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20651) When in Upgrade paused state, links should be disabled for less privileged user
[ https://issues.apache.org/jira/browse/AMBARI-20651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20651: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 174c0402f76abc88b08ad9a2b4b2cdf1653c4902 > When in Upgrade paused state, links should be disabled for less privileged > user > --- > > Key: AMBARI-20651 > URL: https://issues.apache.org/jira/browse/AMBARI-20651 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20651.patch > > > When in Upgrade paused state, links should be disabled for less privileged > user -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20651) When in Upgrade paused state, links should be disabled for less privileged user
[ https://issues.apache.org/jira/browse/AMBARI-20651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20651: -- Attachment: AMBARI-20651.patch > When in Upgrade paused state, links should be disabled for less privileged > user > --- > > Key: AMBARI-20651 > URL: https://issues.apache.org/jira/browse/AMBARI-20651 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20651.patch > > > When in Upgrade paused state, links should be disabled for less privileged > user -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20651) When in Upgrade paused state, links should be disabled for less privileged user
[ https://issues.apache.org/jira/browse/AMBARI-20651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20651: -- Status: Patch Available (was: Open) > When in Upgrade paused state, links should be disabled for less privileged > user > --- > > Key: AMBARI-20651 > URL: https://issues.apache.org/jira/browse/AMBARI-20651 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20651.patch > > > When in Upgrade paused state, links should be disabled for less privileged > user -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20651) When in Upgrade paused state, links should be disabled for less privileged user
Richard Zang created AMBARI-20651: - Summary: When in Upgrade paused state, links should be disabled for less privileged user Key: AMBARI-20651 URL: https://issues.apache.org/jira/browse/AMBARI-20651 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.1 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.1 When in Upgrade paused state, links should be disabled for less privileged user -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20613) Host Filtering interaction is confusing and cumbersome to perform simple filtering
[ https://issues.apache.org/jira/browse/AMBARI-20613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20613: -- Status: Patch Available (was: Open) > Host Filtering interaction is confusing and cumbersome to perform simple > filtering > -- > > Key: AMBARI-20613 > URL: https://issues.apache.org/jira/browse/AMBARI-20613 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20613.patch > > > The new Host filtering was implemented for 2.4.0. > This allowed for more sophisticated filtering, but made certain tasks more > difficult, like a simple substring match on hostnames, which is part of a > typical workflow and doing bulk ops on hosts. > The major challenge from the user standpoint is that the new host filter > aggressively pushes typeahead selections to the user, so it is really > difficult to enter a simple search term that the user wants to enter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20613) Host Filtering interaction is confusing and cumbersome to perform simple filtering
[ https://issues.apache.org/jira/browse/AMBARI-20613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20613: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk fa2beead902a95ba4db3332f6e24c77e929062cf > Host Filtering interaction is confusing and cumbersome to perform simple > filtering > -- > > Key: AMBARI-20613 > URL: https://issues.apache.org/jira/browse/AMBARI-20613 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.1 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20613.patch > > > The new Host filtering was implemented for 2.4.0. > This allowed for more sophisticated filtering, but made certain tasks more > difficult, like a simple substring match on hostnames, which is part of a > typical workflow and doing bulk ops on hosts. > The major challenge from the user standpoint is that the new host filter > aggressively pushes typeahead selections to the user, so it is really > difficult to enter a simple search term that the user wants to enter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20613) Host Filtering interaction is confusing and cumbersome to perform simple filtering
Richard Zang created AMBARI-20613: - Summary: Host Filtering interaction is confusing and cumbersome to perform simple filtering Key: AMBARI-20613 URL: https://issues.apache.org/jira/browse/AMBARI-20613 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.1 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.1 The new Host filtering was implemented for 2.4.0. This allowed for more sophisticated filtering, but made certain tasks more difficult, like a simple substring match on hostnames, which is part of a typical workflow and doing bulk ops on hosts. The major challenge from the user standpoint is that the new host filter aggressively pushes typeahead selections to the user, so it is really difficult to enter a simple search term that the user wants to enter. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-20429) Warn users about pending requests while trying to enable Interactive Query immediately after disabling it
[ https://issues.apache.org/jira/browse/AMBARI-20429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang resolved AMBARI-20429. --- Resolution: Fixed Committed to trunk and 2.5 dd7f46f10df8b31476bb17e427775c4acf8c303d > Warn users about pending requests while trying to enable Interactive Query > immediately after disabling it > - > > Key: AMBARI-20429 > URL: https://issues.apache.org/jira/browse/AMBARI-20429 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Attachments: AMBARI-20429.v0.branch-2.5.patch > > > There is no warning or protection for the user to avoid enabling of > Interactive Query immediately after disabling it. Showing a popup to warn the > user about a pending batch request would be helpful here. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AMBARI-19145) Namenodes failed to start while adding a Jouralnode
[
https://issues.apache.org/jira/browse/AMBARI-19145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang resolved AMBARI-19145.
---
Resolution: Cannot Reproduce
> Namenodes failed to start while adding a Jouralnode
> ---
>
> Key: AMBARI-19145
> URL: https://issues.apache.org/jira/browse/AMBARI-19145
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
>Assignee: Richard Zang
>Priority: Blocker
> Fix For: 2.5.0
>
>
> STR:
> 1) Install cluster and Enable HA with 3 Journalnodes
> 2) Add a Journal node using manage JN wizard (This goes through fine)
> 3) Add another Journal node
> This time go to hosts page, and click add component-> JN and use the manage
> JN wizard
> Namenodes fail to start in the final step.
> Both the namenodes fail to connect to each other
> {noformat}
> java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at
> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at
> org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
> at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:495)
> at
> org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:650)
> at
> org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:745)
> at org.apache.hadoop.ipc.Client$Connection.access$3200(Client.java:397)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1618)
> at org.apache.hadoop.ipc.Client.call(Client.java:1449)
> at org.apache.hadoop.ipc.Client.call(Client.java:1396)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:233)
> at com.sun.proxy.$Proxy8.getServiceStatus(Unknown Source)
> at
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AMBARI-20287) Filter in Customize Services Page doesn't bring up all properties that matches
[ https://issues.apache.org/jira/browse/AMBARI-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang resolved AMBARI-20287. --- Resolution: Fixed Committed to trunk and 2.5 fcad14b39e55137912fee51a946b2b85f5140d0e > Filter in Customize Services Page doesn't bring up all properties that matches > -- > > Key: AMBARI-20287 > URL: https://issues.apache.org/jira/browse/AMBARI-20287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-20287.patch > > > - Navigate to Add Service Wizard to Add Ranger > - At Customize Services page, change Sync Source to LDAP/AD > - try to filter out few properties like: > - Enable Group Sync, Incremental Sync etc > They are not getting filtered out. As there are multiple tabs and tabs inside > first level tabs, its not easy to find the values of these properties without > the help of filter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20287) Filter in Customize Services Page doesn't bring up all properties that matches
[ https://issues.apache.org/jira/browse/AMBARI-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20287: -- Attachment: AMBARI-20287.patch > Filter in Customize Services Page doesn't bring up all properties that matches > -- > > Key: AMBARI-20287 > URL: https://issues.apache.org/jira/browse/AMBARI-20287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran > Fix For: 2.5.0 > > Attachments: AMBARI-20287.patch > > > - Navigate to Add Service Wizard to Add Ranger > - At Customize Services page, change Sync Source to LDAP/AD > - try to filter out few properties like: > - Enable Group Sync, Incremental Sync etc > They are not getting filtered out. As there are multiple tabs and tabs inside > first level tabs, its not easy to find the values of these properties without > the help of filter -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.
[
https://issues.apache.org/jira/browse/AMBARI-20265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-20265:
--
Resolution: Invalid
Status: Resolved (was: Patch Available)
> Blueprint deployment with auto-restart settings enabled, auto-restart UI is
> incomplete.
> ---
>
> Key: AMBARI-20265
> URL: https://issues.apache.org/jira/browse/AMBARI-20265
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
>
> Attached screenshot of UI post blueprint deployment.
> Attached blueprint used for deployment.
> Here is a snipped of blueprint to enable the auto-restart feature:
> {noformat}
> "settings" : [
> {
> "recovery_settings" : [
> {
> "recovery_enabled" : "true"
> }
> ]
> },
> {
> "service_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "YARN"
> }
> ]
> },
> {
> "component_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "APP_TIMELINE_SERVER"
> }
> ]
> }
> ],
> {noformat}
> The expectation is that only the YARN App_timeline_server should be
> auto-restart enabled. The overall property would also show enabled.
> {noformat}
> {
> "blueprint": "bugbash",
> "default_password": "password",
> "config_recommendation_strategy":
> "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
> "host_groups": [
> {
> "name": "host_group_1",
> "hosts": [
> {
> "fqdn": "c6401.apache.ambari.org",
> "ip": "192.168.64.101"
> }
> ]
> },
> {
> "name": "host_group_2",
> "hosts": [
> {
> "fqdn": "c6402.apache.ambari.org",
> "ip": "192.168.64.102"
> }
> ]
> },
> {
> "name": "host_group_3",
> "hosts": [
> {
> "fqdn": "c6403.apache.ambari.org",
> "ip": "192.168.64.103"
> }
> ]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.
[
https://issues.apache.org/jira/browse/AMBARI-20265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-20265:
--
Attachment: (was: AMBARI-20265.patch)
> Blueprint deployment with auto-restart settings enabled, auto-restart UI is
> incomplete.
> ---
>
> Key: AMBARI-20265
> URL: https://issues.apache.org/jira/browse/AMBARI-20265
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
>
> Attached screenshot of UI post blueprint deployment.
> Attached blueprint used for deployment.
> Here is a snipped of blueprint to enable the auto-restart feature:
> {noformat}
> "settings" : [
> {
> "recovery_settings" : [
> {
> "recovery_enabled" : "true"
> }
> ]
> },
> {
> "service_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "YARN"
> }
> ]
> },
> {
> "component_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "APP_TIMELINE_SERVER"
> }
> ]
> }
> ],
> {noformat}
> The expectation is that only the YARN App_timeline_server should be
> auto-restart enabled. The overall property would also show enabled.
> {noformat}
> {
> "blueprint": "bugbash",
> "default_password": "password",
> "config_recommendation_strategy":
> "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
> "host_groups": [
> {
> "name": "host_group_1",
> "hosts": [
> {
> "fqdn": "c6401.apache.ambari.org",
> "ip": "192.168.64.101"
> }
> ]
> },
> {
> "name": "host_group_2",
> "hosts": [
> {
> "fqdn": "c6402.apache.ambari.org",
> "ip": "192.168.64.102"
> }
> ]
> },
> {
> "name": "host_group_3",
> "hosts": [
> {
> "fqdn": "c6403.apache.ambari.org",
> "ip": "192.168.64.103"
> }
> ]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.
[
https://issues.apache.org/jira/browse/AMBARI-20265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-20265:
--
Attachment: AMBARI-20265.patch
> Blueprint deployment with auto-restart settings enabled, auto-restart UI is
> incomplete.
> ---
>
> Key: AMBARI-20265
> URL: https://issues.apache.org/jira/browse/AMBARI-20265
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-20265.patch
>
>
> Attached screenshot of UI post blueprint deployment.
> Attached blueprint used for deployment.
> Here is a snipped of blueprint to enable the auto-restart feature:
> {noformat}
> "settings" : [
> {
> "recovery_settings" : [
> {
> "recovery_enabled" : "true"
> }
> ]
> },
> {
> "service_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "YARN"
> }
> ]
> },
> {
> "component_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "APP_TIMELINE_SERVER"
> }
> ]
> }
> ],
> {noformat}
> The expectation is that only the YARN App_timeline_server should be
> auto-restart enabled. The overall property would also show enabled.
> {noformat}
> {
> "blueprint": "bugbash",
> "default_password": "password",
> "config_recommendation_strategy":
> "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
> "host_groups": [
> {
> "name": "host_group_1",
> "hosts": [
> {
> "fqdn": "c6401.apache.ambari.org",
> "ip": "192.168.64.101"
> }
> ]
> },
> {
> "name": "host_group_2",
> "hosts": [
> {
> "fqdn": "c6402.apache.ambari.org",
> "ip": "192.168.64.102"
> }
> ]
> },
> {
> "name": "host_group_3",
> "hosts": [
> {
> "fqdn": "c6403.apache.ambari.org",
> "ip": "192.168.64.103"
> }
> ]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.
[
https://issues.apache.org/jira/browse/AMBARI-20265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-20265:
--
Status: Patch Available (was: Open)
> Blueprint deployment with auto-restart settings enabled, auto-restart UI is
> incomplete.
> ---
>
> Key: AMBARI-20265
> URL: https://issues.apache.org/jira/browse/AMBARI-20265
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-20265.patch
>
>
> Attached screenshot of UI post blueprint deployment.
> Attached blueprint used for deployment.
> Here is a snipped of blueprint to enable the auto-restart feature:
> {noformat}
> "settings" : [
> {
> "recovery_settings" : [
> {
> "recovery_enabled" : "true"
> }
> ]
> },
> {
> "service_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "YARN"
> }
> ]
> },
> {
> "component_settings" : [
> {
> "recovery_enabled" : "true",
> "name" : "APP_TIMELINE_SERVER"
> }
> ]
> }
> ],
> {noformat}
> The expectation is that only the YARN App_timeline_server should be
> auto-restart enabled. The overall property would also show enabled.
> {noformat}
> {
> "blueprint": "bugbash",
> "default_password": "password",
> "config_recommendation_strategy":
> "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
> "host_groups": [
> {
> "name": "host_group_1",
> "hosts": [
> {
> "fqdn": "c6401.apache.ambari.org",
> "ip": "192.168.64.101"
> }
> ]
> },
> {
> "name": "host_group_2",
> "hosts": [
> {
> "fqdn": "c6402.apache.ambari.org",
> "ip": "192.168.64.102"
> }
> ]
> },
> {
> "name": "host_group_3",
> "hosts": [
> {
> "fqdn": "c6403.apache.ambari.org",
> "ip": "192.168.64.103"
> }
> ]
> }
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20265) Blueprint deployment with auto-restart settings enabled, auto-restart UI is incomplete.
Richard Zang created AMBARI-20265:
-
Summary: Blueprint deployment with auto-restart settings enabled,
auto-restart UI is incomplete.
Key: AMBARI-20265
URL: https://issues.apache.org/jira/browse/AMBARI-20265
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.5.0
Reporter: Richard Zang
Assignee: Richard Zang
Fix For: 2.5.0
Attached screenshot of UI post blueprint deployment.
Attached blueprint used for deployment.
Here is a snipped of blueprint to enable the auto-restart feature:
{noformat}
"settings" : [
{
"recovery_settings" : [
{
"recovery_enabled" : "true"
}
]
},
{
"service_settings" : [
{
"recovery_enabled" : "true",
"name" : "YARN"
}
]
},
{
"component_settings" : [
{
"recovery_enabled" : "true",
"name" : "APP_TIMELINE_SERVER"
}
]
}
],
{noformat}
The expectation is that only the YARN App_timeline_server should be
auto-restart enabled. The overall property would also show enabled.
{noformat}
{
"blueprint": "bugbash",
"default_password": "password",
"config_recommendation_strategy": "ALWAYS_APPLY_DONT_OVERRIDE_CUSTOM_VALUES",
"host_groups": [
{
"name": "host_group_1",
"hosts": [
{
"fqdn": "c6401.apache.ambari.org",
"ip": "192.168.64.101"
}
]
},
{
"name": "host_group_2",
"hosts": [
{
"fqdn": "c6402.apache.ambari.org",
"ip": "192.168.64.102"
}
]
},
{
"name": "host_group_3",
"hosts": [
{
"fqdn": "c6403.apache.ambari.org",
"ip": "192.168.64.103"
}
]
}
]
}
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-20194) Enable/Disable UI objects related to managing alert targets based on user's privileges
[ https://issues.apache.org/jira/browse/AMBARI-20194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20194: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 b53fc82a7184fb8b54c290b523f9146c19227a87 > Enable/Disable UI objects related to managing alert targets based on user's > privileges > -- > > Key: AMBARI-20194 > URL: https://issues.apache.org/jira/browse/AMBARI-20194 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20194.patch > > > UI objects related to managing alert targets need to be enabled or disabled > based on user's privileges. > The relevant privilege name is CLUSTER.MANAGE_ALERT_NOTIFICATIONS. If this > exists in the users's set of privileges, the user should be able to manage > alert targets and relevant details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20194) Enable/Disable UI objects related to managing alert targets based on user's privileges
[ https://issues.apache.org/jira/browse/AMBARI-20194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20194: -- Attachment: AMBARI-20194.patch > Enable/Disable UI objects related to managing alert targets based on user's > privileges > -- > > Key: AMBARI-20194 > URL: https://issues.apache.org/jira/browse/AMBARI-20194 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20194.patch > > > UI objects related to managing alert targets need to be enabled or disabled > based on user's privileges. > The relevant privilege name is CLUSTER.MANAGE_ALERT_NOTIFICATIONS. If this > exists in the users's set of privileges, the user should be able to manage > alert targets and relevant details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20194) Enable/Disable UI objects related to managing alert targets based on user's privileges
[ https://issues.apache.org/jira/browse/AMBARI-20194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20194: -- Status: Patch Available (was: Open) > Enable/Disable UI objects related to managing alert targets based on user's > privileges > -- > > Key: AMBARI-20194 > URL: https://issues.apache.org/jira/browse/AMBARI-20194 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20194.patch > > > UI objects related to managing alert targets need to be enabled or disabled > based on user's privileges. > The relevant privilege name is CLUSTER.MANAGE_ALERT_NOTIFICATIONS. If this > exists in the users's set of privileges, the user should be able to manage > alert targets and relevant details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20194) Enable/Disable UI objects related to managing alert targets based on user's privileges
Richard Zang created AMBARI-20194: - Summary: Enable/Disable UI objects related to managing alert targets based on user's privileges Key: AMBARI-20194 URL: https://issues.apache.org/jira/browse/AMBARI-20194 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Priority: Critical Fix For: 2.5.0 UI objects related to managing alert targets need to be enabled or disabled based on user's privileges. The relevant privilege name is CLUSTER.MANAGE_ALERT_NOTIFICATIONS. If this exists in the users's set of privileges, the user should be able to manage alert targets and relevant details. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19907) On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19907: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 424949b95cafead9754cd87ea1a379f21995b5af > On certain actions, there's no feedback from the UI when API takes a long > time to respond - not reassuring and the user is encouraged to keep > triggering the same heavy action to make the problem worse > > > Key: AMBARI-19907 > URL: https://issues.apache.org/jira/browse/AMBARI-19907 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19907_branch-2.5_final.patch, > AMBARI-19907_fix1.patch, AMBARI-19907_trunk_final.patch, > AMBARI-19907.v0.branch-2.5.patch, AMBARI-19907.v1.patch > > > On a big cluster, it takes the server a long time to process the API request > for certain operations, like "Stop All", "Start All", etc. > On a small cluster, the "background operations" popup appears within a few > seconds to acknowledge to the user that the server is working on handling the > request. > However, when the cluster gets bigger and the request API takes the server > much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no > indication on the UI that the server received the request. This is not > reassuring to the user and the user is tempted to keep re-triggering the > action and overwhelming the server. > This problem is not just for "Start All", "Stop All". This problem actually > happens for "Stop" and "Start" of a single service as well (and likely other > places, like Hosts / Host Detail pages.) On the 1000-node cluster, this > takes about 6-7 seconds, enough to make the user wonder if the request got to > the server or not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19907) On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19907: -- Attachment: AMBARI-19907_trunk_final.patch AMBARI-19907_branch-2.5_final.patch > On certain actions, there's no feedback from the UI when API takes a long > time to respond - not reassuring and the user is encouraged to keep > triggering the same heavy action to make the problem worse > > > Key: AMBARI-19907 > URL: https://issues.apache.org/jira/browse/AMBARI-19907 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19907_branch-2.5_final.patch, > AMBARI-19907_fix1.patch, AMBARI-19907_trunk_final.patch, > AMBARI-19907.v0.branch-2.5.patch, AMBARI-19907.v1.patch > > > On a big cluster, it takes the server a long time to process the API request > for certain operations, like "Stop All", "Start All", etc. > On a small cluster, the "background operations" popup appears within a few > seconds to acknowledge to the user that the server is working on handling the > request. > However, when the cluster gets bigger and the request API takes the server > much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no > indication on the UI that the server received the request. This is not > reassuring to the user and the user is tempted to keep re-triggering the > action and overwhelming the server. > This problem is not just for "Start All", "Stop All". This problem actually > happens for "Stop" and "Start" of a single service as well (and likely other > places, like Hosts / Host Detail pages.) On the 1000-node cluster, this > takes about 6-7 seconds, enough to make the user wonder if the request got to > the server or not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
[ https://issues.apache.org/jira/browse/AMBARI-20158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20158: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed fix1 patch to trunk and 2.5 df47fa77bfa591f7c8da955b6959f8f12d662889 > Host filter is missing for admin user after upgrading to ambari 2.4.2 or above > -- > > Key: AMBARI-20158 > URL: https://issues.apache.org/jira/browse/AMBARI-20158 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20158-fix1.patch, AMBARI-20158.patch > > > *STR:* > # Deploy ambari cluster and customize ambari behavior for "admin user" via > experimental page (For example: opsDuringUpgrade. Note this flag is most > frequently enabled by the customer for previous versions of ambari) > # Upgrade ambari to 2.4.2 or above > *Expected behavior:* Admin user should be able to use new combo box for > filtering hosts on Hosts page > *Actual behavior:* new combobox is missing for "admin user" and there is no > way to filter hosts via ambari-web. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
[ https://issues.apache.org/jira/browse/AMBARI-20158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20158: -- Attachment: AMBARI-20158-fix1.patch > Host filter is missing for admin user after upgrading to ambari 2.4.2 or above > -- > > Key: AMBARI-20158 > URL: https://issues.apache.org/jira/browse/AMBARI-20158 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20158-fix1.patch, AMBARI-20158.patch > > > *STR:* > # Deploy ambari cluster and customize ambari behavior for "admin user" via > experimental page (For example: opsDuringUpgrade. Note this flag is most > frequently enabled by the customer for previous versions of ambari) > # Upgrade ambari to 2.4.2 or above > *Expected behavior:* Admin user should be able to use new combo box for > filtering hosts on Hosts page > *Actual behavior:* new combobox is missing for "admin user" and there is no > way to filter hosts via ambari-web. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
[ https://issues.apache.org/jira/browse/AMBARI-20158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20158: -- Status: Patch Available (was: Reopened) > Host filter is missing for admin user after upgrading to ambari 2.4.2 or above > -- > > Key: AMBARI-20158 > URL: https://issues.apache.org/jira/browse/AMBARI-20158 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20158-fix1.patch, AMBARI-20158.patch > > > *STR:* > # Deploy ambari cluster and customize ambari behavior for "admin user" via > experimental page (For example: opsDuringUpgrade. Note this flag is most > frequently enabled by the customer for previous versions of ambari) > # Upgrade ambari to 2.4.2 or above > *Expected behavior:* Admin user should be able to use new combo box for > filtering hosts on Hosts page > *Actual behavior:* new combobox is missing for "admin user" and there is no > way to filter hosts via ambari-web. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
[ https://issues.apache.org/jira/browse/AMBARI-20158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20158: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 7ce52f7035450d3cd72e35eaf5a158ae7f825c55 > Host filter is missing for admin user after upgrading to ambari 2.4.2 or above > -- > > Key: AMBARI-20158 > URL: https://issues.apache.org/jira/browse/AMBARI-20158 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20158.patch > > > *STR:* > # Deploy ambari cluster and customize ambari behavior for "admin user" via > experimental page (For example: opsDuringUpgrade. Note this flag is most > frequently enabled by the customer for previous versions of ambari) > # Upgrade ambari to 2.4.2 or above > *Expected behavior:* Admin user should be able to use new combo box for > filtering hosts on Hosts page > *Actual behavior:* new combobox is missing for "admin user" and there is no > way to filter hosts via ambari-web. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
[ https://issues.apache.org/jira/browse/AMBARI-20158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20158: -- Status: Patch Available (was: Open) > Host filter is missing for admin user after upgrading to ambari 2.4.2 or above > -- > > Key: AMBARI-20158 > URL: https://issues.apache.org/jira/browse/AMBARI-20158 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20158.patch > > > *STR:* > # Deploy ambari cluster and customize ambari behavior for "admin user" via > experimental page (For example: opsDuringUpgrade. Note this flag is most > frequently enabled by the customer for previous versions of ambari) > # Upgrade ambari to 2.4.2 or above > *Expected behavior:* Admin user should be able to use new combo box for > filtering hosts on Hosts page > *Actual behavior:* new combobox is missing for "admin user" and there is no > way to filter hosts via ambari-web. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
[ https://issues.apache.org/jira/browse/AMBARI-20158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20158: -- Attachment: AMBARI-20158.patch > Host filter is missing for admin user after upgrading to ambari 2.4.2 or above > -- > > Key: AMBARI-20158 > URL: https://issues.apache.org/jira/browse/AMBARI-20158 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20158.patch > > > *STR:* > # Deploy ambari cluster and customize ambari behavior for "admin user" via > experimental page (For example: opsDuringUpgrade. Note this flag is most > frequently enabled by the customer for previous versions of ambari) > # Upgrade ambari to 2.4.2 or above > *Expected behavior:* Admin user should be able to use new combo box for > filtering hosts on Hosts page > *Actual behavior:* new combobox is missing for "admin user" and there is no > way to filter hosts via ambari-web. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20158) Host filter is missing for admin user after upgrading to ambari 2.4.2 or above
Richard Zang created AMBARI-20158: - Summary: Host filter is missing for admin user after upgrading to ambari 2.4.2 or above Key: AMBARI-20158 URL: https://issues.apache.org/jira/browse/AMBARI-20158 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Priority: Critical Fix For: 2.5.0 *STR:* # Deploy ambari cluster and customize ambari behavior for "admin user" via experimental page (For example: opsDuringUpgrade. Note this flag is most frequently enabled by the customer for previous versions of ambari) # Upgrade ambari to 2.4.2 or above *Expected behavior:* Admin user should be able to use new combo box for filtering hosts on Hosts page *Actual behavior:* new combobox is missing for "admin user" and there is no way to filter hosts via ambari-web. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20125) DataNode Storage alert is duplicated
[ https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20125: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 602e0a3e23a3a0cab0ac0dd27bda6374017b1d43 > DataNode Storage alert is duplicated > > > Key: AMBARI-20125 > URL: https://issues.apache.org/jira/browse/AMBARI-20125 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20125.patch > > > In the HDFS alert popup, "DataNode Storage" item is duplicated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20125) DataNode Storage alert is duplicated
[ https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20125: -- Attachment: AMBARI-20125.patch > DataNode Storage alert is duplicated > > > Key: AMBARI-20125 > URL: https://issues.apache.org/jira/browse/AMBARI-20125 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20125.patch > > > In the HDFS alert popup, "DataNode Storage" item is duplicated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20125) DataNode Storage alert is duplicated
[ https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20125: -- Status: Patch Available (was: Open) > DataNode Storage alert is duplicated > > > Key: AMBARI-20125 > URL: https://issues.apache.org/jira/browse/AMBARI-20125 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20125.patch > > > In the HDFS alert popup, "DataNode Storage" item is duplicated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20125) DataNode Storage alert is duplicated
[
https://issues.apache.org/jira/browse/AMBARI-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879624#comment-15879624
]
Richard Zang commented on AMBARI-20125:
---
When we try to sort alert collection in the order of "critical, warning, ok,
unknown, other", we made modification to original looping collection
"serviceDefinitions" during the forEach loop. Also, alert definition with
multiple alert instances distributed in different categories got pushed
multiple times during the sort. This led to duplicated entries after
processing.
{code}
var property = context.get('componentName') ? 'componentName' :
'serviceName';
var serviceDefinitions =
this.get('controller.content').filterProperty(property, context.get(property));
// definitions should be sorted in order: critical, warning, ok,
unknown, other
var definitionTypes = {
"isCritical": [],
"isWarning": [],
"isOK": [],
"isUnknown": []
};
serviceDefinitions.forEach(function (definition) {
Object.keys(definitionTypes).forEach(function (type) {
if (definition.get(type)) {
definition.set('isCollapsed', true);
definitionTypes[type].push(definition);
serviceDefinitions = serviceDefinitions.without(definition);
}
});
});
serviceDefinitions =
definitionTypes.isCritical.concat(definitionTypes.isWarning,
definitionTypes.isOK, definitionTypes.isUnknown, serviceDefinitions);
return serviceDefinitions;
{code}
> DataNode Storage alert is duplicated
>
>
> Key: AMBARI-20125
> URL: https://issues.apache.org/jira/browse/AMBARI-20125
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
>
> In the HDFS alert popup, "DataNode Storage" item is duplicated.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (AMBARI-20125) DataNode Storage alert is duplicated
Richard Zang created AMBARI-20125: - Summary: DataNode Storage alert is duplicated Key: AMBARI-20125 URL: https://issues.apache.org/jira/browse/AMBARI-20125 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Priority: Critical Fix For: 2.5.0 In the HDFS alert popup, "DataNode Storage" item is duplicated. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20058) 'Final' is not shown correctly in config diff tool and in older versions
[ https://issues.apache.org/jira/browse/AMBARI-20058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20058: -- Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk and 2.5 75c359350c86c0eecebc25ea8ad23b6ee65b3db8 > 'Final' is not shown correctly in config diff tool and in older versions > - > > Key: AMBARI-20058 > URL: https://issues.apache.org/jira/browse/AMBARI-20058 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-20058.patch > > > - Issue1 > From api call we can see that fs.defaultFS is set to final in version 2 where > as we cant see that on UI when we navigate to V2 > - Issue2 > Compare V6 to V2 > V2 shows final for fs.defaultFS > Compare V2 to V6 > V2 doesnt show final for the property > - Issue3 > Set final to any of the properties > Make sure its shown on UI > Compare it with an older version > Diff doesnt show final for this property -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20058) 'Final' is not shown correctly in config diff tool and in older versions
[ https://issues.apache.org/jira/browse/AMBARI-20058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20058: -- Attachment: AMBARI-20058.patch > 'Final' is not shown correctly in config diff tool and in older versions > - > > Key: AMBARI-20058 > URL: https://issues.apache.org/jira/browse/AMBARI-20058 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-20058.patch > > > - Issue1 > From api call we can see that fs.defaultFS is set to final in version 2 where > as we cant see that on UI when we navigate to V2 > - Issue2 > Compare V6 to V2 > V2 shows final for fs.defaultFS > Compare V2 to V6 > V2 doesnt show final for the property > - Issue3 > Set final to any of the properties > Make sure its shown on UI > Compare it with an older version > Diff doesnt show final for this property -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20058) 'Final' is not shown correctly in config diff tool and in older versions
[ https://issues.apache.org/jira/browse/AMBARI-20058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-20058: -- Status: Patch Available (was: Open) > 'Final' is not shown correctly in config diff tool and in older versions > - > > Key: AMBARI-20058 > URL: https://issues.apache.org/jira/browse/AMBARI-20058 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-20058.patch > > > - Issue1 > From api call we can see that fs.defaultFS is set to final in version 2 where > as we cant see that on UI when we navigate to V2 > - Issue2 > Compare V6 to V2 > V2 shows final for fs.defaultFS > Compare V2 to V6 > V2 doesnt show final for the property > - Issue3 > Set final to any of the properties > Make sure its shown on UI > Compare it with an older version > Diff doesnt show final for this property -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20058) 'Final' is not shown correctly in config diff tool and in older versions
[ https://issues.apache.org/jira/browse/AMBARI-20058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang reassigned AMBARI-20058: - Assignee: Richard Zang > 'Final' is not shown correctly in config diff tool and in older versions > - > > Key: AMBARI-20058 > URL: https://issues.apache.org/jira/browse/AMBARI-20058 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Dhanya Balasundaran >Assignee: Richard Zang > Fix For: 2.5.0 > > > - Issue1 > From api call we can see that fs.defaultFS is set to final in version 2 where > as we cant see that on UI when we navigate to V2 > - Issue2 > Compare V6 to V2 > V2 shows final for fs.defaultFS > Compare V2 to V6 > V2 doesnt show final for the property > - Issue3 > Set final to any of the properties > Make sure its shown on UI > Compare it with an older version > Diff doesnt show final for this property -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871_fix1.patch, AMBARI-19871_fix2.patch, > AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Status: Patch Available (was: Reopened) > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871_fix1.patch, AMBARI-19871_fix2.patch, > AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang reopened AMBARI-19871: --- > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871_fix1.patch, AMBARI-19871_fix2.patch, > AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Attachment: AMBARI-19871_fix2.patch > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871_fix1.patch, AMBARI-19871_fix2.patch, > AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (AMBARI-19871) Config version switch/compare/revert doesn't work
[
https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864905#comment-15864905
]
Richard Zang edited comment on AMBARI-19871 at 2/14/17 2:31 AM:
Found another problem caused by action parameter binding. Ember always invokes
action with the parameter bind in the first rendering. Only action parameter
from template is having this problem, direct text parameter binding is working
fine. So, right now if you click cross button and open the pulldown version
list, hover a version and click some action on its right popup. The following
action will alway be invoked with the first version you hovered as it's action
parameter. We did not have this problem on version pull down list or the
horizontal version box list because we had separate version popup generated for
each version box/item, yet now we are reusing a single box for all versions
from pulldown list.
{code}
{{action doAction view.parentView.hoveredServiceVersion
view.parentView.actionTypes.SWITCH target="view.parentView"}}
{code}
was (Author: rzang):
Found another problem caused by action parameter binding. Ember always invokes
action with the parameter bind in the first rendering. Only action parameter
from template is having this problem, direct text parameter binding is working
fine. So, right now if you click cross button and open the pulldown version
list. The following action will alway be invoked with the first version you
hovered as it's action parameter. We did not have this problem on version pull
down list or the horizontal version box list because we had separate version
popup generated for each version box/item, yet now we are reusing a single box
for all versions from pulldown list.
{code}
{{action doAction view.parentView.hoveredServiceVersion
view.parentView.actionTypes.SWITCH target="view.parentView"}}
{code}
> Config version switch/compare/revert doesn't work
> -
>
> Key: AMBARI-19871
> URL: https://issues.apache.org/jira/browse/AMBARI-19871
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19871_fix1.patch, AMBARI-19871.patch
>
>
> *Steps to reproduce:*
> 1. Go to any service with multiple config versions.
> 2. On the bottom left of the config history bar(the cross button), select an
> older version and click View.
> *Actual result:*
> Now direct clicking on other config version block will not be able to switch
> version. Only through the cross button can you switch to other version.
> Compare configs also does not work, it always compare to the current version
> and end up with empty diff.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (AMBARI-19871) Config version switch/compare/revert doesn't work
[
https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864905#comment-15864905
]
Richard Zang commented on AMBARI-19871:
---
Found another problem caused by action parameter binding. Ember always invokes
action with the parameter bind in the first rendering. Only action parameter
from template is having this problem, direct text parameter binding is working
fine. So, right now if you click cross button and open the pulldown version
list. The following action will alway be invoked with the first version you
hovered as it's action parameter. We did not have this problem on version pull
down list or the horizontal version box list because we had separate version
popup generated for each version box/item, yet now we are reusing a single box
for all versions from pulldown list.
{code}
{{action doAction view.parentView.hoveredServiceVersion
view.parentView.actionTypes.SWITCH target="view.parentView"}}
{code}
> Config version switch/compare/revert doesn't work
> -
>
> Key: AMBARI-19871
> URL: https://issues.apache.org/jira/browse/AMBARI-19871
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19871_fix1.patch, AMBARI-19871.patch
>
>
> *Steps to reproduce:*
> 1. Go to any service with multiple config versions.
> 2. On the bottom left of the config history bar(the cross button), select an
> older version and click View.
> *Actual result:*
> Now direct clicking on other config version block will not be able to switch
> version. Only through the cross button can you switch to other version.
> Compare configs also does not work, it always compare to the current version
> and end up with empty diff.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (AMBARI-19907) On certain actions, there's no feedback from the UI when API takes a long time to respond - not reassuring and the user is encouraged to keep triggering the same heavy
[ https://issues.apache.org/jira/browse/AMBARI-19907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19907: -- Attachment: AMBARI-19907_fix1.patch > On certain actions, there's no feedback from the UI when API takes a long > time to respond - not reassuring and the user is encouraged to keep > triggering the same heavy action to make the problem worse > > > Key: AMBARI-19907 > URL: https://issues.apache.org/jira/browse/AMBARI-19907 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19907_fix1.patch, > AMBARI-19907.v0.branch-2.5.patch, AMBARI-19907.v1.patch > > > On a big cluster, it takes the server a long time to process the API request > for certain operations, like "Stop All", "Start All", etc. > On a small cluster, the "background operations" popup appears within a few > seconds to acknowledge to the user that the server is working on handling the > request. > However, when the cluster gets bigger and the request API takes the server > much longer (e.g., on a 1000-node cluster, it took ~35 seconds), there's no > indication on the UI that the server received the request. This is not > reassuring to the user and the user is tempted to keep re-triggering the > action and overwhelming the server. > This problem is not just for "Start All", "Stop All". This problem actually > happens for "Stop" and "Start" of a single service as well (and likely other > places, like Hosts / Host Detail pages.) On the 1000-node cluster, this > takes about 6-7 seconds, enough to make the user wonder if the request got to > the server or not. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Attachment: AMBARI-19871_fix1.patch AMBARI-19871.patch > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871_fix1.patch, AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19912) Manage Config Group host list is not sorted
[ https://issues.apache.org/jira/browse/AMBARI-19912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19912: -- Status: Patch Available (was: Open) > Manage Config Group host list is not sorted > > > Key: AMBARI-19912 > URL: https://issues.apache.org/jira/browse/AMBARI-19912 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19912.patch > > > The host list in the Manage Config Group popup is not sorted so it is very > difficult to see which hosts are in the group when you have a large number of > hosts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19912) Manage Config Group host list is not sorted
[ https://issues.apache.org/jira/browse/AMBARI-19912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19912: -- Attachment: AMBARI-19912.patch > Manage Config Group host list is not sorted > > > Key: AMBARI-19912 > URL: https://issues.apache.org/jira/browse/AMBARI-19912 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang > Fix For: 2.5.0 > > Attachments: AMBARI-19912.patch > > > The host list in the Manage Config Group popup is not sorted so it is very > difficult to see which hosts are in the group when you have a large number of > hosts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19912) Manage Config Group host list is not sorted
Richard Zang created AMBARI-19912: - Summary: Manage Config Group host list is not sorted Key: AMBARI-19912 URL: https://issues.apache.org/jira/browse/AMBARI-19912 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.0 The host list in the Manage Config Group popup is not sorted so it is very difficult to see which hosts are in the group when you have a large number of hosts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and 2.5 e35bfd32b90282eae83fd14bbfaaf50e1bf47c87 > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Status: Patch Available (was: Open) > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Attachment: AMBARI-19871.patch > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-19871.patch > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-19871) Config version switch/compare/revert doesn't work
Richard Zang created AMBARI-19871: - Summary: Config version switch/compare/revert doesn't work Key: AMBARI-19871 URL: https://issues.apache.org/jira/browse/AMBARI-19871 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.5.0 Reporter: Richard Zang Assignee: Richard Zang Fix For: 2.5.0 *Steps to reproduce:* 1. Go to any service with multiple config versions. 2. On the bottom left of the config history bar(the cross button), select an older version and click View. *Actual result:* Now direct clicking on other config version block will not be able to switch version. Only through the cross button can you switch to other version. Compare configs also does not work, it always compare to the current version and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-19871) Config version switch/compare/revert doesn't work
[ https://issues.apache.org/jira/browse/AMBARI-19871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Zang updated AMBARI-19871: -- Priority: Critical (was: Major) > Config version switch/compare/revert doesn't work > - > > Key: AMBARI-19871 > URL: https://issues.apache.org/jira/browse/AMBARI-19871 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.0 >Reporter: Richard Zang >Assignee: Richard Zang >Priority: Critical > Fix For: 2.5.0 > > > *Steps to reproduce:* > 1. Go to any service with multiple config versions. > 2. On the bottom left of the config history bar(the cross button), select an > older version and click View. > *Actual result:* > Now direct clicking on other config version block will not be able to switch > version. Only through the cross button can you switch to other version. > Compare configs also does not work, it always compare to the current version > and end up with empty diff. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-19701) Provide minimal call context from UI when making stack advisor calls
[
https://issues.apache.org/jira/browse/AMBARI-19701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15838946#comment-15838946
]
Richard Zang commented on AMBARI-19701:
---
fix1 patch committed to trunk and branch-2.5
71b743450442d62192c1aa25ebc0269c3cdd3d2b
> Provide minimal call context from UI when making stack advisor calls
>
>
> Key: AMBARI-19701
> URL: https://issues.apache.org/jira/browse/AMBARI-19701
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-19701-branch-2.5.patch,
> AMBARI-19701-fix1-branch-2.5.patch, AMBARI-19701-fix1.patch,
> AMBARI-19701_trunk.patch
>
>
> We need to identify if call is made when
> * Cluster is being created (first call)
> * Add service
> * Just landing on a page and only need config attributes
> Possible change to the json data send in POST -
> {code}
> {
> "recommend":"configurations",
> "user_context" : { "operation" : "ClusterCreate" } <== add this
> "hosts"
> {code}
> *Cluster create (first call):*
> {code}"user_context": {"operation" : "ClusterCreate"}{code}
> *Add service (first call):*
> {code}"user_context": {"operation" : "AddService", "operation_details" :
> "HDFS,YARN"}{code}
> *Landing on a config page:*
> {code}"user_context": {"operation" : "RecommendAttribute"}{code}
> *Config edit on a config page: (lower priority)*
> {code}"user_context": {"operation" : "EditConfig"}{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-19701) Provide minimal call context from UI when making stack advisor calls
[
https://issues.apache.org/jira/browse/AMBARI-19701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zang updated AMBARI-19701:
--
Attachment: AMBARI-19701-fix1-branch-2.5.patch
> Provide minimal call context from UI when making stack advisor calls
>
>
> Key: AMBARI-19701
> URL: https://issues.apache.org/jira/browse/AMBARI-19701
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.5.0
>
> Attachments: AMBARI-19701-branch-2.5.patch,
> AMBARI-19701-fix1-branch-2.5.patch, AMBARI-19701-fix1.patch,
> AMBARI-19701_trunk.patch
>
>
> We need to identify if call is made when
> * Cluster is being created (first call)
> * Add service
> * Just landing on a page and only need config attributes
> Possible change to the json data send in POST -
> {code}
> {
> "recommend":"configurations",
> "user_context" : { "operation" : "ClusterCreate" } <== add this
> "hosts"
> {code}
> *Cluster create (first call):*
> {code}"user_context": {"operation" : "ClusterCreate"}{code}
> *Add service (first call):*
> {code}"user_context": {"operation" : "AddService", "operation_details" :
> "HDFS,YARN"}{code}
> *Landing on a config page:*
> {code}"user_context": {"operation" : "RecommendAttribute"}{code}
> *Config edit on a config page: (lower priority)*
> {code}"user_context": {"operation" : "EditConfig"}{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
