Re: [VOTE] Apache Ambari 2.7.5 RC0

[Aleksandr Kovalenko]

+1 approve

On Fri, Dec 13, 2019 at 2:36 PM Vitaly Brodetskyi
 wrote:

> +1
>
> On Fri, Dec 13, 2019 at 2:23 PM Akhil Naik 
> wrote:
>
> > +1
> >
> >
> > *Thanks,Akhil Subhash Naik* | Staff Software Engineer (Backline Team)
> > Tel No. (91) 7907412471 <00>
> > e-mail:  asn...@cloudera.com
> > cloudera.com 
> > How am I doing?
> > Please provide feedback to my manager Vinod : v...@cloudera.com
> >
> > [image: Cloudera] 
> >
> > [image: Cloudera on Twitter]  [image:
> > Cloudera on Facebook]  [image:
> Cloudera
> > on LinkedIn] 
> > --
> >
> >
> > On Fri, Dec 13, 2019 at 4:59 PM Myroslav Papyrkovskyy
> >  wrote:
> >
> > > Hi All,
> > >
> > > I have created an apache-ambari-2.7.5 release candidate.
> > >
> > > GIT source tag: (release-2.7.5-rc0):
> > > https://github.com/apache/ambari/commits/release-2.7.5-rc0
> > >
> > >
> > > Staging site:
> > > http://home.apache.org/~mpapirkovskyy/apache-ambari-2.7.5-rc0/
> > >
> > >
> > > PGP release keys (signed using 247A40C6):
> > >
> http://pgp.mit.edu:11371/pks/lookup?search=0x234F09B0247A40C6&op=vindex
> > >
> > > One can look into issues fixed in this release at:
> > > https://issues.apache.org/jira/projects/AMBARI/versions/12346267
> > >
> > > Vote will be open for 72 hours.
> > > [   ] +1 approve
> > > [   ] +0 no opinion
> > > [   ] -1 disapprove (and reasons why)
> > >
> > > Regards,
> > > Myroslav Papyrkovskyy
> > >
> >
>

Re: [VOTE] Apache Ambari 2.7.4 RC0

[Aleksandr Kovalenko]

+1 approve

On Tue, Sep 10, 2019 at 4:39 PM Myroslav Papyrkovskyy
 wrote:

> Hi All,
>
> I have created an apache-ambari-2.7.4 release candidate.
>
> GIT source tag: (release-2.7.4-rc0):
> https://github.com/apache/ambari/commits/release-2.7.4-rc0
>
>
> Staging site:
> http://home.apache.org/~mpapirkovskyy/apache-ambari-2.7.4-rc0/
>
>
> PGP release keys (signed using 247A40C6):
> http://pgp.mit.edu:11371/pks/lookup?search=0x234F09B0247A40C6&op=vindex
>
> One can look into issues fixed in this release at:
> https://issues.apache.org/jira/projects/AMBARI/versions/12344903
>
> Vote will be open for 72 hours.
> [   ] +1 approve
> [   ] +0 no opinion
> [   ] -1 disapprove (and reason why)
>
> Regards,
> Myroslav Papyrkovskyy
>

Bootstrap migration

[Aleksandr Kovalenko]

Hi all,

The work to migrate the very outdated Bootstrap 2 (originally used for
Ambari back in 2012) to Bootstrap 3 has been done via
https://issues.apache.org/jira/browse/AMBARI-18573.

This is mostly library, CSS class names, and some markup changes, with a
small amount of refactoring.

Just a heads up that the plan is to commit this by tomorrow (Oct 14) around
12PM Pacific.

Thanks,
Aleks

[jira] [Commented] (AMBARI-15302) Service deletion should recommend and change configs before deleting service

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180041#comment-15180041
 ] 

Aleksandr Kovalenko commented on AMBARI-15302:
--

+1 for the patch

> Service deletion should recommend and change configs before deleting service
> 
>
> Key: AMBARI-15302
> URL: https://issues.apache.org/jira/browse/AMBARI-15302
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15302.patch
>
>
> There are scenarios in ambari where stack advisor recommends configs for a 
> service depending on the existence of another service.
> For example configs in multiple services are recommended to have different 
> values depending upon presence or absence of Ranger service. Same is true for 
> Kerberos and HDFS service.
> Thus at time of deletion of such services, it is important to make a call to 
> recommendation endpoint and change configs of services that has config 
> dependencies on the service being deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15289) Duplicated config groups after rename

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179822#comment-15179822
 ] 

Aleksandr Kovalenko commented on AMBARI-15289:
--

Patch changes way how rename operation operate with model, it should not change 
unit tests.

committed to trunk

> Duplicated config groups after rename
> -
>
> Key: AMBARI-15289
> URL: https://issues.apache.org/jira/browse/AMBARI-15289
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15289.patch
>
>
> Rename group, save changes and open popup again. You will see two groups with 
> the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15289) Duplicated config groups after rename

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178567#comment-15178567
 ] 

Aleksandr Kovalenko commented on AMBARI-15289:
--

  24554 tests complete (22 seconds)
  146 tests pending


> Duplicated config groups after rename
> -
>
> Key: AMBARI-15289
> URL: https://issues.apache.org/jira/browse/AMBARI-15289
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15289.patch
>
>
> Rename group, save changes and open popup again. You will see two groups with 
> the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15289) Duplicated config groups after rename

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-15289:
-
Attachment: AMBARI-15289.patch

> Duplicated config groups after rename
> -
>
> Key: AMBARI-15289
> URL: https://issues.apache.org/jira/browse/AMBARI-15289
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15289.patch
>
>
> Rename group, save changes and open popup again. You will see two groups with 
> the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-15289) Duplicated config groups after rename

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-15289:


 Summary: Duplicated config groups after rename
 Key: AMBARI-15289
 URL: https://issues.apache.org/jira/browse/AMBARI-15289
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
 Fix For: 2.4.0


Rename group, save changes and open popup again. You will see two groups with 
the same name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15264) Ambari Admin: incorrect alerts on Roles page

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176306#comment-15176306
 ] 

Aleksandr Kovalenko commented on AMBARI-15264:
--

+1 for the patch

> Ambari Admin: incorrect alerts on Roles page
> 
>
> Key: AMBARI-15264
> URL: https://issues.apache.org/jira/browse/AMBARI-15264
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15264.patch, roles-alert.jpg
>
>
> When any role is changed on Roles page using list view, alert with info on 
> this operation is displayed. Text of alert is incorrect (containins previous 
> role instead of new one): [^roles-alert.jpg].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15263) Ambari Admin: redundant scrollbars in Contents section of Version page

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176307#comment-15176307
 ] 

Aleksandr Kovalenko commented on AMBARI-15263:
--

+1 for the patch

> Ambari Admin: redundant scrollbars in Contents section of Version page
> --
>
> Key: AMBARI-15263
> URL: https://issues.apache.org/jira/browse/AMBARI-15263
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15263.patch, versions-scrolling.jpg
>
>
> Contents section of Edit Version and Register Version pages always contains 
> scrollbars (redundant if there's enough space to display all the info).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15261) Hide Admin Settings / Login Message features

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175692#comment-15175692
 ] 

Aleksandr Kovalenko commented on AMBARI-15261:
--

+1 for the patch

> Hide Admin Settings / Login Message features
> 
>
> Key: AMBARI-15261
> URL: https://issues.apache.org/jira/browse/AMBARI-15261
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15261.patch
>
>
> We are no longer shipping the Admin Settings + Login Message/LDAP setup, etc, 
> features in Ambari 2.4.0.
> We need to make sure that these features are hidden by default via 
> App.supports experimental feature flag.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15251) Ambari - Managed KDC Credentials is not saving the Admin Principal and Admin Password when Adding Services.

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174339#comment-15174339
 ] 

Aleksandr Kovalenko commented on AMBARI-15251:
--

+1 for the patch

> Ambari - Managed KDC Credentials is not saving the Admin Principal and Admin 
> Password when Adding Services.
> ---
>
> Key: AMBARI-15251
> URL: https://issues.apache.org/jira/browse/AMBARI-15251
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15251_22.patch, AMBARI-15251_trunk.patch
>
>
> PROBLEM:  Ambari is configured for password encryption and Save Admin 
> Credentials has been enabled after Ambari restart. However, even though we 
> have saved the credentials, we are still getting asked for it in each new 
> service add.
> This seems to be a bug and it will prompts for the KDC principal and password 
> each time adding services.
> STEPS TO REPRODUCE:  On a HDP 2.3.2 and Ambari 2.2.0, Select Amin Tab --> 
> Managed KDC Credentials Tab --> Kerberos and put in Admin principal and Admin 
> password, click save.
> Then when adding a service, it for Admin principal and Admin password again.  
> If we leave it blank and proceed, it errors with the error in the .doc 
> attached.
> EXPECTED RESULT:  Expected result is it should not prompt for principal and 
> password again.
> ACTUAL RESULT:  What the actual result is it is prompting for principal and 
> password again.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15204) Host checks should not be performed if 0 hosts register

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172019#comment-15172019
 ] 

Aleksandr Kovalenko commented on AMBARI-15204:
--

+1 for the patch

> Host checks should not be performed if 0 hosts register
> ---
>
> Key: AMBARI-15204
> URL: https://issues.apache.org/jira/browse/AMBARI-15204
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15204.patch
>
>
> Went to add hosts and mis-typed my ssh info, which means host registration 
> failed...that was expected. But it performing hosts checks even those 0 hosts 
> were registered seems strange.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15225) Write more UI UT

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171974#comment-15171974
 ] 

Aleksandr Kovalenko commented on AMBARI-15225:
--

+1 for the patch

> Write more UI UT
> 
>
> Key: AMBARI-15225
> URL: https://issues.apache.org/jira/browse/AMBARI-15225
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15225.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15221) Gap between top navigation bar and views dropdown

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171884#comment-15171884
 ] 

Aleksandr Kovalenko commented on AMBARI-15221:
--

+1 for the patch

> Gap between top navigation bar and views dropdown
> -
>
> Key: AMBARI-15221
> URL: https://issues.apache.org/jira/browse/AMBARI-15221
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15221.patch, admin-dropdown.jpg, 
> services-dropdown.jpg, views-dropdown.jpg
>
>
> There's ~1px gap between top menu and Views dropdown submenu: 
> [^views-dropdown.jpg].
> Other submenus are located closely to navigation bar: 
> [^services-dropdown.jpg], [^admin-dropdown.jpg].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15207) Settings button doesn't work if cluster is not installed

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170588#comment-15170588
 ] 

Aleksandr Kovalenko commented on AMBARI-15207:
--

committed to trunk

> Settings button doesn't work if cluster is not installed
> 
>
> Key: AMBARI-15207
> URL: https://issues.apache.org/jira/browse/AMBARI-15207
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15207.patch
>
>
> If we open Views page on Ambari without installed cluster and then try to 
> open settings popup from left top dropdown menu nothing happens. As all 
> settings are related to cluster, let's hide this option if cluster is not 
> installed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15207) Settings button doesn't work if cluster is not installed

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170586#comment-15170586
 ] 

Aleksandr Kovalenko commented on AMBARI-15207:
--

 24337 tests complete (21 seconds)
  146 tests pending


> Settings button doesn't work if cluster is not installed
> 
>
> Key: AMBARI-15207
> URL: https://issues.apache.org/jira/browse/AMBARI-15207
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15207.patch
>
>
> If we open Views page on Ambari without installed cluster and then try to 
> open settings popup from left top dropdown menu nothing happens. As all 
> settings are related to cluster, let's hide this option if cluster is not 
> installed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15207) Settings button doesn't work if cluster is not installed

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-15207:
-
Attachment: AMBARI-15207.patch

> Settings button doesn't work if cluster is not installed
> 
>
> Key: AMBARI-15207
> URL: https://issues.apache.org/jira/browse/AMBARI-15207
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>    Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15207.patch
>
>
> If we open Views page on Ambari without installed cluster and then try to 
> open settings popup from left top dropdown menu nothing happens. As all 
> settings are related to cluster, let's hide this option if cluster is not 
> installed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15207) Settings button doesn't work if cluster is not installed

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-15207:
-
Attachment: insecure_private_key

> Settings button doesn't work if cluster is not installed
> 
>
> Key: AMBARI-15207
> URL: https://issues.apache.org/jira/browse/AMBARI-15207
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>    Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15207.patch
>
>
> If we open Views page on Ambari without installed cluster and then try to 
> open settings popup from left top dropdown menu nothing happens. As all 
> settings are related to cluster, let's hide this option if cluster is not 
> installed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15207) Settings button doesn't work if cluster is not installed

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-15207:
-
Attachment: (was: insecure_private_key)

> Settings button doesn't work if cluster is not installed
> 
>
> Key: AMBARI-15207
> URL: https://issues.apache.org/jira/browse/AMBARI-15207
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>    Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15207.patch
>
>
> If we open Views page on Ambari without installed cluster and then try to 
> open settings popup from left top dropdown menu nothing happens. As all 
> settings are related to cluster, let's hide this option if cluster is not 
> installed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-15207) Settings button doesn't work if cluster is not installed

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-15207:


 Summary: Settings button doesn't work if cluster is not installed
 Key: AMBARI-15207
 URL: https://issues.apache.org/jira/browse/AMBARI-15207
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 2.4.0


If we open Views page on Ambari without installed cluster and then try to open 
settings popup from left top dropdown menu nothing happens. As all settings are 
related to cluster, let's hide this option if cluster is not installed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15206) Issues with Login Message dialog Round #3

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169366#comment-15169366
 ] 

Aleksandr Kovalenko commented on AMBARI-15206:
--

+1 for the patch

> Issues with Login Message dialog Round #3
> -
>
> Key: AMBARI-15206
> URL: https://issues.apache.org/jira/browse/AMBARI-15206
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15206.patch
>
>
> Found a couple bugs, and something that was missed from last round of edits.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15188) Status icons in Services dropdown menu aren't centered vertically

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167533#comment-15167533
 ] 

Aleksandr Kovalenko commented on AMBARI-15188:
--

+1 for the patch

> Status icons in Services dropdown menu aren't centered vertically
> -
>
> Key: AMBARI-15188
> URL: https://issues.apache.org/jira/browse/AMBARI-15188
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15188.patch, servicesmenu.jpg
>
>
> Service status icons in top menu are aligned to top. See attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-13946) Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS to fail

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-13946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167471#comment-15167471
 ] 

Aleksandr Kovalenko commented on AMBARI-13946:
--

Ambari-trunk-test-patch -> Service Unavailable
branch-2.2 local UT results after applying patch:
10428 tests complete (15 seconds)
121 tests pending
trunk local UT results after applying patch:
24321 tests complete (29 seconds)
146 tests pending
Rat check passed on trunk and branch-2.2.

> Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer 
> and ATS to fail
> -
>
> Key: AMBARI-13946
> URL: https://issues.apache.org/jira/browse/AMBARI-13946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2, 2.2.0
> Environment: CentOS6.7, HDP2.3-2950
>Reporter: Benoit Perroud
>Assignee: Aleksandr Kovalenko
> Attachments: AMBARI-13946.patch, AMBARI-13946_branch-2.2.patch
>
>
> After enabling NameNode-HA, {{hdfs-site.xml}} does still contain non-HA 
> properties, including
> * dfs.namenode.rpc-address
> * dfs.namenode.http-address
> * dfs.namenode.https-address
> This cause the balancer to fail with the following symptoms in Balancer:
> {code}
> ...
> 15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, 
> hdfs://daplab-rt-11.fri.lan:8020]
> ...
> java.io.IOException: Another Balancer is running..  Exiting ...
> {code}
> And ATS:
> {code}
> _assert_valid
> self.target_status = self._get_file_status(target)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 292, in _get_file_status
> list_status = self.util.run_command(target, 'GETFILESTATUS', 
> method='GET', ignore_status_codes=['404'], assertable_result=False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 210, in run_command
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w 
> '%{http_code}' -X GET 
> 'http://pvvsccmn1-brn1:50070/webhdfs/v1/ats/done?op=GETFILESTATUS&user.name=hdfs''
>  returned status_code=403. 
> {
>   "RemoteException": {
> "exception": "StandbyException", 
> "javaClassName": "org.apache.hadoop.ipc.StandbyException", 
> "message": "Operation category READ is not supported in state standby"
>   }
> }
> {code}
> These should be removed from the config.
> Steps to reproduce: after turning on NameNode HA, {{grep 
> dfs.namenode.rpc-address|dfs.namenode.http-address 
> /etc/hadoop/conf/hdfs-site.xml}} shouldn't return anything



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15185) Cover main controllers with unit tests

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167468#comment-15167468
 ] 

Aleksandr Kovalenko commented on AMBARI-15185:
--

+1 for the patch

> Cover main controllers with unit tests
> --
>
> Key: AMBARI-15185
> URL: https://issues.apache.org/jira/browse/AMBARI-15185
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15185.patch
>
>
> Cover following files with unit tests:
> * ambari-web/app/controllers/main/host
> * ambari-web/app/controllers/main/service
> * ambari-web/app/controllers/main/view_controller
> * ambari-web/app/controllers/main/alert_definitions_controller



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-13946) Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS to fail

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-13946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-13946:
-
Attachment: AMBARI-13946_branch-2.2.patch

> Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer 
> and ATS to fail
> -
>
> Key: AMBARI-13946
> URL: https://issues.apache.org/jira/browse/AMBARI-13946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2, 2.2.0
> Environment: CentOS6.7, HDP2.3-2950
>Reporter: Benoit Perroud
>    Assignee: Aleksandr Kovalenko
> Attachments: AMBARI-13946.patch, AMBARI-13946_branch-2.2.patch
>
>
> After enabling NameNode-HA, {{hdfs-site.xml}} does still contain non-HA 
> properties, including
> * dfs.namenode.rpc-address
> * dfs.namenode.http-address
> * dfs.namenode.https-address
> This cause the balancer to fail with the following symptoms in Balancer:
> {code}
> ...
> 15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, 
> hdfs://daplab-rt-11.fri.lan:8020]
> ...
> java.io.IOException: Another Balancer is running..  Exiting ...
> {code}
> And ATS:
> {code}
> _assert_valid
> self.target_status = self._get_file_status(target)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 292, in _get_file_status
> list_status = self.util.run_command(target, 'GETFILESTATUS', 
> method='GET', ignore_status_codes=['404'], assertable_result=False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 210, in run_command
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w 
> '%{http_code}' -X GET 
> 'http://pvvsccmn1-brn1:50070/webhdfs/v1/ats/done?op=GETFILESTATUS&user.name=hdfs''
>  returned status_code=403. 
> {
>   "RemoteException": {
> "exception": "StandbyException", 
> "javaClassName": "org.apache.hadoop.ipc.StandbyException", 
> "message": "Operation category READ is not supported in state standby"
>   }
> }
> {code}
> These should be removed from the config.
> Steps to reproduce: after turning on NameNode HA, {{grep 
> dfs.namenode.rpc-address|dfs.namenode.http-address 
> /etc/hadoop/conf/hdfs-site.xml}} shouldn't return anything



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-13946) Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS to fail

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-13946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-13946:
-
Attachment: AMBARI-13946.patch

> Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer 
> and ATS to fail
> -
>
> Key: AMBARI-13946
> URL: https://issues.apache.org/jira/browse/AMBARI-13946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2, 2.2.0
> Environment: CentOS6.7, HDP2.3-2950
>Reporter: Benoit Perroud
>    Assignee: Aleksandr Kovalenko
> Attachments: AMBARI-13946.patch
>
>
> After enabling NameNode-HA, {{hdfs-site.xml}} does still contain non-HA 
> properties, including
> * dfs.namenode.rpc-address
> * dfs.namenode.http-address
> * dfs.namenode.https-address
> This cause the balancer to fail with the following symptoms in Balancer:
> {code}
> ...
> 15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, 
> hdfs://daplab-rt-11.fri.lan:8020]
> ...
> java.io.IOException: Another Balancer is running..  Exiting ...
> {code}
> And ATS:
> {code}
> _assert_valid
> self.target_status = self._get_file_status(target)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 292, in _get_file_status
> list_status = self.util.run_command(target, 'GETFILESTATUS', 
> method='GET', ignore_status_codes=['404'], assertable_result=False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 210, in run_command
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w 
> '%{http_code}' -X GET 
> 'http://pvvsccmn1-brn1:50070/webhdfs/v1/ats/done?op=GETFILESTATUS&user.name=hdfs''
>  returned status_code=403. 
> {
>   "RemoteException": {
> "exception": "StandbyException", 
> "javaClassName": "org.apache.hadoop.ipc.StandbyException", 
> "message": "Operation category READ is not supported in state standby"
>   }
> }
> {code}
> These should be removed from the config.
> Steps to reproduce: after turning on NameNode HA, {{grep 
> dfs.namenode.rpc-address|dfs.namenode.http-address 
> /etc/hadoop/conf/hdfs-site.xml}} shouldn't return anything



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (AMBARI-13946) Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer and ATS to fail

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-13946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko reassigned AMBARI-13946:


Assignee: Aleksandr Kovalenko

> Non NameNode-HA properties still in hdfs-site.xml causing (at least) Balancer 
> and ATS to fail
> -
>
> Key: AMBARI-13946
> URL: https://issues.apache.org/jira/browse/AMBARI-13946
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2, 2.2.0
> Environment: CentOS6.7, HDP2.3-2950
>Reporter: Benoit Perroud
>    Assignee: Aleksandr Kovalenko
>
> After enabling NameNode-HA, {{hdfs-site.xml}} does still contain non-HA 
> properties, including
> * dfs.namenode.rpc-address
> * dfs.namenode.http-address
> * dfs.namenode.https-address
> This cause the balancer to fail with the following symptoms in Balancer:
> {code}
> ...
> 15/11/18 15:48:30 INFO balancer.Balancer: namenodes  = [hdfs://daplab2, 
> hdfs://daplab-rt-11.fri.lan:8020]
> ...
> java.io.IOException: Another Balancer is running..  Exiting ...
> {code}
> And ATS:
> {code}
> _assert_valid
> self.target_status = self._get_file_status(target)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 292, in _get_file_status
> list_status = self.util.run_command(target, 'GETFILESTATUS', 
> method='GET', ignore_status_codes=['404'], assertable_result=False)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py",
>  line 210, in run_command
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'curl -sS -L -w 
> '%{http_code}' -X GET 
> 'http://pvvsccmn1-brn1:50070/webhdfs/v1/ats/done?op=GETFILESTATUS&user.name=hdfs''
>  returned status_code=403. 
> {
>   "RemoteException": {
> "exception": "StandbyException", 
> "javaClassName": "org.apache.hadoop.ipc.StandbyException", 
> "message": "Operation category READ is not supported in state standby"
>   }
> }
> {code}
> These should be removed from the config.
> Steps to reproduce: after turning on NameNode HA, {{grep 
> dfs.namenode.rpc-address|dfs.namenode.http-address 
> /etc/hadoop/conf/hdfs-site.xml}} shouldn't return anything



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-13002) Turning on the Maintenance mode wouldn't let you install the additional components properly

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-13002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167360#comment-15167360
 ] 

Aleksandr Kovalenko commented on AMBARI-13002:
--

+1 for patches

> Turning on the Maintenance mode wouldn't let you install the additional 
> components  properly
> 
>
> Key: AMBARI-13002
> URL: https://issues.apache.org/jira/browse/AMBARI-13002
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin, ambari-server
>Affects Versions: 2.0.2
> Environment: RHEL 6.x, HDP2.2.4.12
>Reporter: Basha Shaik
>Assignee: Antonenko Alexander
>  Labels: patch
> Attachments: AMBARI-13002_22.patch, AMBARI-13002_trunk.patch
>
>
> Scenario:
> 1. Turn on the maintenance mode on HDFS service to suppress alerts
> 2. Add Name Node HA
> 3. During the adding addional name nodes and journal nodes, the amabri server 
> supposed to stop the name node service but it wouldn't stop. 
> 4. As a result there is a lock on the HDFS and nameNode initializeEdits steps 
> fail
> Expected Result:
> Even when in maintenance mode, Amabri should be able to add services, start 
> and stop the services as required.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15164) Hide "Add Override" buttons in NameNode HA Wizard on step3

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15166977#comment-15166977
 ] 

Aleksandr Kovalenko commented on AMBARI-15164:
--

committed to trunk

> Hide "Add Override" buttons in NameNode HA Wizard on step3
> --
>
> Key: AMBARI-15164
> URL: https://issues.apache.org/jira/browse/AMBARI-15164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15164.patch, useless_controls.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15164) Hide "Add Override" buttons in NameNode HA Wizard on step3

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-15164:
-
Attachment: AMBARI-15164.patch

> Hide "Add Override" buttons in NameNode HA Wizard on step3
> --
>
> Key: AMBARI-15164
> URL: https://issues.apache.org/jira/browse/AMBARI-15164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-15164.patch, useless_controls.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15164) Hide "Add Override" buttons in NameNode HA Wizard on step3

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-15164:
-
Attachment: useless_controls.png

> Hide "Add Override" buttons in NameNode HA Wizard on step3
> --
>
> Key: AMBARI-15164
> URL: https://issues.apache.org/jira/browse/AMBARI-15164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: useless_controls.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-15164) Hide "Add Override" buttons in NameNode HA Wizard on step3

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-15164:


 Summary: Hide "Add Override" buttons in NameNode HA Wizard on step3
 Key: AMBARI-15164
 URL: https://issues.apache.org/jira/browse/AMBARI-15164
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 2.4.0
 Attachments: useless_controls.png





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15154) Hide LDAP configuration page from Ambari Admin

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162889#comment-15162889
 ] 

Aleksandr Kovalenko commented on AMBARI-15154:
--

+1 for the patch

> Hide LDAP configuration page from Ambari Admin
> --
>
> Key: AMBARI-15154
> URL: https://issues.apache.org/jira/browse/AMBARI-15154
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15154.patch
>
>
> LDAP Configuration UI should be implemented in Ambari 3.0.0, not 2.4.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15143) Display spinner in place of graph while new data loading is in progress

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162853#comment-15162853
 ] 

Aleksandr Kovalenko commented on AMBARI-15143:
--

+1 for the patch

> Display spinner in place of graph while new data loading is in progress
> ---
>
> Key: AMBARI-15143
> URL: https://issues.apache.org/jira/browse/AMBARI-15143
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15143.patch
>
>
> After time range for graph is switched and before new data is received, 
> spinner should be displayed instead of graph with 'old' time range values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15142) Small refactor for configs

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15159020#comment-15159020
 ] 

Aleksandr Kovalenko commented on AMBARI-15142:
--

+1 for the patch

> Small refactor for configs
> --
>
> Key: AMBARI-15142
> URL: https://issues.apache.org/jira/browse/AMBARI-15142
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15142.patch
>
>
> Refactor some methods to make them usable on installer and service info 
> configs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15119) Allow changing log directories for all services

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155044#comment-15155044
 ] 

Aleksandr Kovalenko commented on AMBARI-15119:
--

+1 for the patch

> Allow changing log directories for all services
> ---
>
> Key: AMBARI-15119
> URL: https://issues.apache.org/jira/browse/AMBARI-15119
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15119.patch
>
>
> Deploy the full stack.
> Drop the isReconfigurable flag on all the log directories and make sure that 
> services can start and service checks pass after log directories are changed 
> (post cluster install).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15113) UI does not update alert state

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154501#comment-15154501
 ] 

Aleksandr Kovalenko commented on AMBARI-15113:
--

+1 for patch

> UI does not update alert state
> --
>
> Key: AMBARI-15113
> URL: https://issues.apache.org/jira/browse/AMBARI-15113
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15113.patch, datanode_alert1.png, 
> datanode_alert2.png
>
>
> *STR*
> 1) Install Ambari
> 2) Enable https for Ambari
> 3) Deploy cluster (HDFS, Zookeeper)
> 4) Stop Datanode
> Datanode Process alert is displayed as 'OK' on alerts page and as 'Critical' 
> on alert details page (see screenshots).
> Page refresh fixed the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15070) Graph scale behaviour is incorrect if time range is switched before graph data API call is complete

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150507#comment-15150507
 ] 

Aleksandr Kovalenko commented on AMBARI-15070:
--

+1 for patches

> Graph scale behaviour is incorrect if time range is switched before graph 
> data API call is complete
> ---
>
> Key: AMBARI-15070
> URL: https://issues.apache.org/jira/browse/AMBARI-15070
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15070_222.patch, AMBARI-15070_trunk.patch
>
>
> *STR*
> # Switch metrics time range from 'Last 1 hour' to 'Last 1 year' (for example, 
> on Dashboard; data for 1 year should be available).
> # While metrics API call is pending, switch time range back to 1 hour (can be 
> reproduced if connection rate is low or server is highly loaded so that 
> requests are being processed slowly).
> *Result*
> After request with data for last year is complete, it's displayed on the 
> graph, but the scale is rendered with an accuracy to 1 hour which makes graph 
> unusable 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15059) UI for user home directory creation

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148962#comment-15148962
 ] 

Aleksandr Kovalenko commented on AMBARI-15059:
--

committed to trunk

> UI for user home directory creation
> ---
>
> Key: AMBARI-15059
> URL: https://issues.apache.org/jira/browse/AMBARI-15059
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15059.patch, RP-4908-v1.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15059) UI for user home directory creation

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148952#comment-15148952
 ] 

Aleksandr Kovalenko commented on AMBARI-15059:
--

Unit tests module is not used in Admin View

> UI for user home directory creation
> ---
>
> Key: AMBARI-15059
> URL: https://issues.apache.org/jira/browse/AMBARI-15059
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15059.patch, RP-4908-v1.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15059) UI for user home directory creation

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-15059:
-
Attachment: AMBARI-15059.patch

> UI for user home directory creation
> ---
>
> Key: AMBARI-15059
> URL: https://issues.apache.org/jira/browse/AMBARI-15059
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15059.patch, RP-4908-v1.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15059) UI for user home directory creation

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-15059:
-
Attachment: RP-4908-v1.png

> UI for user home directory creation
> ---
>
> Key: AMBARI-15059
> URL: https://issues.apache.org/jira/browse/AMBARI-15059
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: RP-4908-v1.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-15059) UI for user home directory creation

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-15059:


 Summary: UI for user home directory creation
 Key: AMBARI-15059
 URL: https://issues.apache.org/jira/browse/AMBARI-15059
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
 Fix For: 2.4.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15056) Long hostnames are not truncated in Alerts dialog

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148552#comment-15148552
 ] 

Aleksandr Kovalenko commented on AMBARI-15056:
--

+1 for the patch

> Long hostnames are not truncated in Alerts dialog
> -
>
> Key: AMBARI-15056
> URL: https://issues.apache.org/jira/browse/AMBARI-15056
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15056.patch, hostnames (1).tiff
>
>
> Need to handle hostname truncate in Alerts dialog w/ tooltip hover text for 
> full name (similar to host hostnames are done on Hosts) page.
> hn0-jtsbro.csrgl44nuu4ujklwm1huusuq3b.bx.internal.cloudapp.net
> See attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15049) Sometimes background operations have incorrect order

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147491#comment-15147491
 ] 

Aleksandr Kovalenko commented on AMBARI-15049:
--

+1 for the patch

> Sometimes background operations have incorrect order
> 
>
> Key: AMBARI-15049
> URL: https://issues.apache.org/jira/browse/AMBARI-15049
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: 03.png, 04.png, AMBARI-15049.patch, 
> AMBARI-15049_branch-2.2.patch
>
>
> *Steps to reproduce*:
> # Deploy cluster.
> # Refresh browser.
> # Start all service checks quickly (should be started at least 12-13 checks 
> at the same time).
> # After start last check close Background Operations window.
> # Open Background Operations window.
> # Click "Show more" until all jobs will be opened.
> *Result*: some operations are placed incorrectly or duplicates



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15029) Adding a Service results in deleting Config Group mappings (more than 1 CG present)

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-15029:
-
Attachment: AMBARI-15029.patch

> Adding a Service results in deleting Config Group mappings (more than 1 CG 
> present)
> ---
>
> Key: AMBARI-15029
> URL: https://issues.apache.org/jira/browse/AMBARI-15029
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0, 2.2.1
>Reporter: Aleksandr Kovalenko
>    Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15029.patch, AMBARI-15029_branch-2.2.patch
>
>
> If we add new service and have some config group with custom property (it is 
> absent in default group and is present only in custom config group), this 
> property disappears.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-15029) Adding a Service results in deleting Config Group mappings (more than 1 CG present)

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-15029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-15029:
-
Attachment: AMBARI-15029_branch-2.2.patch

> Adding a Service results in deleting Config Group mappings (more than 1 CG 
> present)
> ---
>
> Key: AMBARI-15029
> URL: https://issues.apache.org/jira/browse/AMBARI-15029
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0, 2.2.1
>Reporter: Aleksandr Kovalenko
>    Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15029.patch, AMBARI-15029_branch-2.2.patch
>
>
> If we add new service and have some config group with custom property (it is 
> absent in default group and is present only in custom config group), this 
> property disappears.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15029) Adding a Service results in deleting Config Group mappings (more than 1 CG present)

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144666#comment-15144666
 ] 

Aleksandr Kovalenko commented on AMBARI-15029:
--

24292 tests complete (22 seconds)
  156 tests pending


> Adding a Service results in deleting Config Group mappings (more than 1 CG 
> present)
> ---
>
> Key: AMBARI-15029
> URL: https://issues.apache.org/jira/browse/AMBARI-15029
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0, 2.2.1
>Reporter: Aleksandr Kovalenko
>    Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15029.patch, AMBARI-15029_branch-2.2.patch
>
>
> If we add new service and have some config group with custom property (it is 
> absent in default group and is present only in custom config group), this 
> property disappears.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-15029) Adding a Service results in deleting Config Group mappings (more than 1 CG present)

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-15029:


 Summary: Adding a Service results in deleting Config Group 
mappings (more than 1 CG present)
 Key: AMBARI-15029
 URL: https://issues.apache.org/jira/browse/AMBARI-15029
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.0, 2.2.1
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
 Fix For: 2.2.2


If we add new service and have some config group with custom property (it is 
absent in default group and is present only in custom config group), this 
property disappears.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15027) Sometimes Yarn graphs,Heatmaps take longer to load

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144618#comment-15144618
 ] 

Aleksandr Kovalenko commented on AMBARI-15027:
--

+1 for the patch

> Sometimes Yarn graphs,Heatmaps take longer to load
> --
>
> Key: AMBARI-15027
> URL: https://issues.apache.org/jira/browse/AMBARI-15027
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
> Environment: ambari-server version: ambari-server-2.2.1.0-66.x86_64
> ambari-server --hash: a659e664cd8b4f05883d8a8a1412e68097bd2b85
> HDP Stack: 2.4
> HDP Version: 2.4.0.0-44
> Ambari DB: :Oracle
> Oozie/Hive DB: Oracle/Oracle
> Security:no
> Security Type:MIT/MIT
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15027.patch, yarnGraphsNotLoading.flv
>
>
> Sometimes YARN graphs, (and summary panel elements sometimes) take long time 
> to load. Please look at the videos of the test that failed because it could 
> not find the yarn graphs,heatmaps in time.
> I was able to reproduce this issue. STR:
> 1) Go to Yarn service page, but navigate away from it before the graphs are 
> loaded
> 2) Try going back again to Yarn page
> The graphs will not load. This was observed on Hbase page as well. Hitting F5 
> or Signing back in solves the problem



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-15014) Incorrect #of required properties at Ranger Customize Services page (Next button not enabled)

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-15014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142721#comment-15142721
 ] 

Aleksandr Kovalenko commented on AMBARI-15014:
--

+1 for patches

> Incorrect #of required properties at Ranger Customize Services page (Next 
> button not enabled)
> -
>
> Key: AMBARI-15014
> URL: https://issues.apache.org/jira/browse/AMBARI-15014
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: AMBARI-15014.patch, AMBARI-15014_branch_2.2.patch
>
>
> At Customize services page of Add Services Wizard while adding Ranger, 
> noticed that the total number of required properties showed at Ranger is 6 
> where as there are only 4 (3 at Admin and 1 at Audit) properties to be filled 
> in. Hence even if all 'required properties' are filled in, UI still shows 
> there are 2 more properties that has issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14993) Log Search: Add Host Log Metrics to Host Details -> Summary

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141051#comment-15141051
 ] 

Aleksandr Kovalenko commented on AMBARI-14993:
--

+1 for the patch

> Log Search: Add Host Log Metrics to Host Details -> Summary
> ---
>
> Key: AMBARI-14993
> URL: https://issues.apache.org/jira/browse/AMBARI-14993
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14993.patch
>
>
> This task covers 
> - Add Right Bottom pane "Host Logs Metrics" to Host Details -> Summary
> - Create Events piechart per service.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14976) Add Grafana QuickLinks for AMS Service in Ambari Web

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141048#comment-15141048
 ] 

Aleksandr Kovalenko commented on AMBARI-14976:
--

+1 for patches

> Add Grafana QuickLinks for AMS Service in Ambari Web
> 
>
> Key: AMBARI-14976
> URL: https://issues.apache.org/jira/browse/AMBARI-14976
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14976.patch, AMBARI-14976_branch-2.2.patch
>
>
> Add quicklink for Grafana to AMS service.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14971) UI - lag in Create Versions page doesn't show confirmation

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15138945#comment-15138945
 ] 

Aleksandr Kovalenko commented on AMBARI-14971:
--

+1 for the patch

> UI - lag in Create Versions page doesn't show confirmation
> --
>
> Key: AMBARI-14971
> URL: https://issues.apache.org/jira/browse/AMBARI-14971
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-admin
>Affects Versions: 2.2.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-14971.patch
>
>
> I've seen this several times where adding a version through the Create 
> Versions page lags.
> I click on the "Save" button, don't get a confirmation, and it actually does 
> end up saving the entity.
> When I click on "Save" again, it shows an error that the version already 
> exists. I remember that before it used to show a confirmation and navigate 
> back to show all of the versions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14957) Paging not working properly when filtering with alerts and hostname

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137157#comment-15137157
 ] 

Aleksandr Kovalenko commented on AMBARI-14957:
--

+1 for the patch

> Paging not working properly when filtering with alerts and hostname
> ---
>
> Key: AMBARI-14957
> URL: https://issues.apache.org/jira/browse/AMBARI-14957
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14957.patch, AMBARI-14957_branch-2.2.patch, 
> filter-not-working.mov
>
>
> On 1200 node cluster I enabled filter for alerts and then put in a hostname 
> filter... which showed hosts that did not match the filter. Also, the paging 
> showed 1 - 10 of 11 at bottom, but when I clicked on the right arrow, it 
> still showed the same page (video attached).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14956) If cluster is not deployed login message is shown 2-3 seconds

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137070#comment-15137070
 ] 

Aleksandr Kovalenko commented on AMBARI-14956:
--

+1 for the patch

> If cluster is not deployed login message is shown 2-3 seconds
> -
>
> Key: AMBARI-14956
> URL: https://issues.apache.org/jira/browse/AMBARI-14956
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14956.patch
>
>
> If you will login to UI that does not have deployed clusters, login message 
> will be displayed 2-3 seconds, after you will be relocated to ambari-admin 
> and message will disappear.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14937) Show error message when installing registered version which does not have repo defined for the OS

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134251#comment-15134251
 ] 

Aleksandr Kovalenko commented on AMBARI-14937:
--

committed to branch-2.2

> Show error message when installing registered version which does not have 
> repo defined for the OS
> -
>
> Key: AMBARI-14937
> URL: https://issues.apache.org/jira/browse/AMBARI-14937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Aleksandr Kovalenko
>    Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14837.patch
>
>
> On my cluster i registered HDP stack 2.4.0.0 but entered URL's for CentOS 6 
> instead of 7. When i tried installing the version no error was shown on the 
> UI and nothing happened.
> We had a 500 returned from the versions api
> {code}
> 28 Jan 2016 04:51:57,296 ERROR [qtp-ambari-client-284] 
> BaseManagementHandler:57 - Caught a system exception while attempting to 
> create a resource: An internal system exception occurred: Stack data, stackN
> ame=HDP, stackVersion= 2.4, osType=redhat7, repoId= HDP-2.4.0.0-142
> org.apache.ambari.server.controller.spi.SystemException: An internal system 
> exception occurred: Stack data, stackName=HDP, stackVersion= 2.4, 
> osType=redhat7, repoId= HDP-2.4.0.0-142
> at 
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:282)
> at 
> org.apache.ambari.server.controller.internal.RepositoryResourceProvider.createResources(RepositoryResourceProvider.java:186)
> at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:289)
> at 
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:76)
> at 
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:36)
> at 
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:72)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at org.apache.ambari.server.api
> {code}
> Which never made it to the end user. We should make sure this gets relayed to 
> the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14937) Show error message when installing registered version which does not have repo defined for the OS

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134248#comment-15134248
 ] 

Aleksandr Kovalenko commented on AMBARI-14937:
--

10367 tests complete (11 seconds)
  121 tests pending

Patch is for branch-2.2.0, so Hadoop QA will not be able to apply patch.

> Show error message when installing registered version which does not have 
> repo defined for the OS
> -
>
> Key: AMBARI-14937
> URL: https://issues.apache.org/jira/browse/AMBARI-14937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Aleksandr Kovalenko
>    Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14837.patch
>
>
> On my cluster i registered HDP stack 2.4.0.0 but entered URL's for CentOS 6 
> instead of 7. When i tried installing the version no error was shown on the 
> UI and nothing happened.
> We had a 500 returned from the versions api
> {code}
> 28 Jan 2016 04:51:57,296 ERROR [qtp-ambari-client-284] 
> BaseManagementHandler:57 - Caught a system exception while attempting to 
> create a resource: An internal system exception occurred: Stack data, stackN
> ame=HDP, stackVersion= 2.4, osType=redhat7, repoId= HDP-2.4.0.0-142
> org.apache.ambari.server.controller.spi.SystemException: An internal system 
> exception occurred: Stack data, stackName=HDP, stackVersion= 2.4, 
> osType=redhat7, repoId= HDP-2.4.0.0-142
> at 
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:282)
> at 
> org.apache.ambari.server.controller.internal.RepositoryResourceProvider.createResources(RepositoryResourceProvider.java:186)
> at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:289)
> at 
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:76)
> at 
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:36)
> at 
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:72)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at org.apache.ambari.server.api
> {code}
> Which never made it to the end user. We should make sure this gets relayed to 
> the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14937) Show error message when installing registered version which does not have repo defined for the OS

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14937:
-
Attachment: AMBARI-14837.patch

> Show error message when installing registered version which does not have 
> repo defined for the OS
> -
>
> Key: AMBARI-14937
> URL: https://issues.apache.org/jira/browse/AMBARI-14937
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Aleksandr Kovalenko
>    Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14837.patch
>
>
> On my cluster i registered HDP stack 2.4.0.0 but entered URL's for CentOS 6 
> instead of 7. When i tried installing the version no error was shown on the 
> UI and nothing happened.
> We had a 500 returned from the versions api
> {code}
> 28 Jan 2016 04:51:57,296 ERROR [qtp-ambari-client-284] 
> BaseManagementHandler:57 - Caught a system exception while attempting to 
> create a resource: An internal system exception occurred: Stack data, stackN
> ame=HDP, stackVersion= 2.4, osType=redhat7, repoId= HDP-2.4.0.0-142
> org.apache.ambari.server.controller.spi.SystemException: An internal system 
> exception occurred: Stack data, stackName=HDP, stackVersion= 2.4, 
> osType=redhat7, repoId= HDP-2.4.0.0-142
> at 
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:282)
> at 
> org.apache.ambari.server.controller.internal.RepositoryResourceProvider.createResources(RepositoryResourceProvider.java:186)
> at 
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:289)
> at 
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:76)
> at 
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:36)
> at 
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:72)
> at 
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
> at 
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
> at org.apache.ambari.server.api
> {code}
> Which never made it to the end user. We should make sure this gets relayed to 
> the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-14937) Show error message when installing registered version which does not have repo defined for the OS

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-14937:


 Summary: Show error message when installing registered version 
which does not have repo defined for the OS
 Key: AMBARI-14937
 URL: https://issues.apache.org/jira/browse/AMBARI-14937
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.2.1
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
 Fix For: 2.2.2


On my cluster i registered HDP stack 2.4.0.0 but entered URL's for CentOS 6 
instead of 7. When i tried installing the version no error was shown on the UI 
and nothing happened.

We had a 500 returned from the versions api

{code}
28 Jan 2016 04:51:57,296 ERROR [qtp-ambari-client-284] BaseManagementHandler:57 
- Caught a system exception while attempting to create a resource: An internal 
system exception occurred: Stack data, stackN
ame=HDP, stackVersion= 2.4, osType=redhat7, repoId= HDP-2.4.0.0-142
org.apache.ambari.server.controller.spi.SystemException: An internal system 
exception occurred: Stack data, stackName=HDP, stackVersion= 2.4, 
osType=redhat7, repoId= HDP-2.4.0.0-142
at 
org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:282)
at 
org.apache.ambari.server.controller.internal.RepositoryResourceProvider.createResources(RepositoryResourceProvider.java:186)
at 
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:289)
at 
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:76)
at 
org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:36)
at 
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:72)
at 
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:135)
at 
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:106)
at org.apache.ambari.server.api
{code}

Which never made it to the end user. We should make sure this gets relayed to 
the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14927) Log Search: Add Host Components Logs tab to Host Details page

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132652#comment-15132652
 ] 

Aleksandr Kovalenko commented on AMBARI-14927:
--

+1 for the patch

> Log Search: Add Host Components Logs tab to Host Details page
> -
>
> Key: AMBARI-14927
> URL: https://issues.apache.org/jira/browse/AMBARI-14927
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14927.patch
>
>
> - Add Tab "Logs" to Host Details
> - Create filter by Service, Component, Extension
> - Create table to display result
> - Pagination for results.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14923) Log Search: Create Log File Search modal popup

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132512#comment-15132512
 ] 

Aleksandr Kovalenko commented on AMBARI-14923:
--

+1 for the patch

> Log Search: Create Log File Search modal popup
> --
>
> Key: AMBARI-14923
> URL: https://issues.apache.org/jira/browse/AMBARI-14923
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14923.patch
>
>
> Top section with filters by keyword, time-range, log level, 
> inclusive/exclusive filter
> Infinite scroll
> Result table with context menu per row to quick open, quick copy.
> Context menu to exclude/include selected text as filter condition
> Navigation to Log Exploration UI



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14916) Issues with Login Message dialog

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132257#comment-15132257
 ] 

Aleksandr Kovalenko commented on AMBARI-14916:
--

+1 for the patch

> Issues with Login Message dialog
> 
>
> Key: AMBARI-14916
> URL: https://issues.apache.org/jira/browse/AMBARI-14916
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14916.patch
>
>
> Using trunk build



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14904) Disable base URL inputs for all OS except one that the cluster is running

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131049#comment-15131049
 ] 

Aleksandr Kovalenko commented on AMBARI-14904:
--

committed to trunk

> Disable base URL inputs for all OS except one that the cluster is running
> -
>
> Key: AMBARI-14904
> URL: https://issues.apache.org/jira/browse/AMBARI-14904
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.2
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14904.patch
>
>
> During upgrade, where we know about the OS on which we are working (eg: 
> Centos 7), we should disable other "OS inputs" on UI, as they are any ways 
> invalid



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14904) Disable base URL inputs for all OS except one that the cluster is running

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14904:
-
Attachment: AMBARI-14904.patch

> Disable base URL inputs for all OS except one that the cluster is running
> -
>
> Key: AMBARI-14904
> URL: https://issues.apache.org/jira/browse/AMBARI-14904
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.2
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14904.patch
>
>
> During upgrade, where we know about the OS on which we are working (eg: 
> Centos 7), we should disable other "OS inputs" on UI, as they are any ways 
> invalid



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-14904) Disable base URL inputs for all OS except one that the cluster is running

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-14904:


 Summary: Disable base URL inputs for all OS except one that the 
cluster is running
 Key: AMBARI-14904
 URL: https://issues.apache.org/jira/browse/AMBARI-14904
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.2.2
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
 Fix For: 2.4.0


During upgrade, where we know about the OS on which we are working (eg: Centos 
7), we should disable other "OS inputs" on UI, as they are any ways invalid



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14898) Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari Web UI

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130512#comment-15130512
 ] 

Aleksandr Kovalenko commented on AMBARI-14898:
--

+1 for the patch

> Alerts: Ability to customize props and thresholds on SCRIPT alerts via Ambari 
> Web UI
> 
>
> Key: AMBARI-14898
> URL: https://issues.apache.org/jira/browse/AMBARI-14898
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14898.patch
>
>
> Script alerts, such as *Ambari Agent / Host Disk Usage* needs to have some 
> metrics Externalized. 
> The Usage screens relies on the alert_disk_space.py script to collect metrics 
> such as Disk utilization (percentage) and directory being checked. 
> The problem is that the directories being check in this script are: 
> 1. ROOT ("/") 
> 2. /usr/hdp 
> If ROOT is OK, then "/usr/hdp" is checked subsequently. However if ROOT is 
> NOT OK (>80% utilization) then "/usr/hdp" is ignored and the "CRITICAL" tag 
> applies to ROOT. 
> This would work on a OOTB standard cluster. However, many users, have 
> Partitions for the hadoop directories. In this instance, "/" is static, no 
> new content will be added. In this instance being at 80 or 90% is OK, this 
> directory will never grow beyond that. 
> "/usr/hdp" is a separate partition that grows in time. 
> Based on the above described check, the 80% of the root partition will 
> trigger a "CRITICAL" message, although the "/usr/hdp" partition is OK. 
> The selection of what directory is being checked should be EXTERNALIZED to a 
> configurable property to avoid these kinds of misleading messages. 
> CONVERSELY --- what constitutes "OK" "WARN" or "CRIT" (the percentage that 
> triggers these) should be left up to the user, not hardcoded in the script. 
> This is a request to externalize the directories that should be checked, as 
> well as the Percentages into an external configurable property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14879) Alerts page pagination issue

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128677#comment-15128677
 ] 

Aleksandr Kovalenko commented on AMBARI-14879:
--

+1 for the patch

> Alerts page pagination issue
> 
>
> Key: AMBARI-14879
> URL: https://issues.apache.org/jira/browse/AMBARI-14879
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-14879.patch
>
>
> 1. Go to alerts page
> 2. Set pagination to 100
> 3. Refresh page - pagination sets to default - 10
> 4. Go to some other page, anf back to alerts - pagination 100 again



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14880) Add popup that will show desired messages upon login

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128545#comment-15128545
 ] 

Aleksandr Kovalenko commented on AMBARI-14880:
--

+1 for the patch

> Add popup that will show desired messages upon login
> 
>
> Key: AMBARI-14880
> URL: https://issues.apache.org/jira/browse/AMBARI-14880
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14880.patch
>
>
> Treat this just as remark:
> We should show this message during page load (view in iframe can be still in 
> loading state),
> because if we will show it after page will be fully rendered, that will 
> require integration to 
> each view. And this is what we definitely don't want to do.
> Because if not logged in user will enter link like
> http://CLUSTER ADDRESS/#/main/views/SLIDER/2.0.0/test, he will be redirected 
> to 
> login page, after he will enter credential, he will be redirected to view 
> that was initially 
> in url /main/views/SLIDER/2.0.0/test. 
> So the url that he entered before login will be loaded. 
> And there is no way, we can determine from ambari, that view inside iframe 
> loaded all 
> needed resources



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14844) Ambari Admin: incorrect 'users' text on the Roles page

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124560#comment-15124560
 ] 

Aleksandr Kovalenko commented on AMBARI-14844:
--

committed to trunk

> Ambari Admin: incorrect 'users' text on the Roles page
> --
>
> Key: AMBARI-14844
> URL: https://issues.apache.org/jira/browse/AMBARI-14844
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14844.patch, no-roles.jpg, roles.jpg
>
>
> Information messages on the Roles page look like it contains users table: 
> no-roles.jpg. This is incorrect because the mentioned table can contain both 
> users and groups: roles.jpg.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14844) Ambari Admin: incorrect 'users' text on the Roles page

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14844:
-
Attachment: AMBARI-14844.patch

> Ambari Admin: incorrect 'users' text on the Roles page
> --
>
> Key: AMBARI-14844
> URL: https://issues.apache.org/jira/browse/AMBARI-14844
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14844.patch, no-roles.jpg, roles.jpg
>
>
> Information messages on the Roles page look like it contains users table: 
> no-roles.jpg. This is incorrect because the mentioned table can contain both 
> users and groups: roles.jpg.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-14844) Ambari Admin: incorrect 'users' text on the Roles page

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-14844:


 Summary: Ambari Admin: incorrect 'users' text on the Roles page
 Key: AMBARI-14844
 URL: https://issues.apache.org/jira/browse/AMBARI-14844
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 2.4.0
 Attachments: no-roles.jpg, roles.jpg

Information messages on the Roles page look like it contains users table: 
no-roles.jpg. This is incorrect because the mentioned table can contain both 
users and groups: roles.jpg.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14844) Ambari Admin: incorrect 'users' text on the Roles page

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14844:
-
Attachment: roles.jpg
no-roles.jpg

> Ambari Admin: incorrect 'users' text on the Roles page
> --
>
> Key: AMBARI-14844
> URL: https://issues.apache.org/jira/browse/AMBARI-14844
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: no-roles.jpg, roles.jpg
>
>
> Information messages on the Roles page look like it contains users table: 
> no-roles.jpg. This is incorrect because the mentioned table can contain both 
> users and groups: roles.jpg.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14843) Admin View: add page "Login Message" with full functionality

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123683#comment-15123683
 ] 

Aleksandr Kovalenko commented on AMBARI-14843:
--

+1 for patch

> Admin View: add page "Login Message" with full functionality
> 
>
> Key: AMBARI-14843
> URL: https://issues.apache.org/jira/browse/AMBARI-14843
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-14843.patch
>
>
> This task should cover "Login Message" page with API integration. Including 
> testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14813) Unable to create config group, when adding override

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14813:
-
Attachment: AMBARI-14813.patch

> Unable to create config group, when adding override
> ---
>
> Key: AMBARI-14813
> URL: https://issues.apache.org/jira/browse/AMBARI-14813
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14813.patch
>
>
> Creating new config group when adding override causes issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-14813) Unable to create config group, when adding override

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-14813:


 Summary: Unable to create config group, when adding override
 Key: AMBARI-14813
 URL: https://issues.apache.org/jira/browse/AMBARI-14813
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 2.4.0


Creating new config group when adding override causes issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14810) When their are multiple Job History Servers in the cluster, QuickLinks should show the URL for all instances

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119239#comment-15119239
 ] 

Aleksandr Kovalenko commented on AMBARI-14810:
--

+1 for the patch

> When their are multiple Job History Servers in the cluster, QuickLinks should 
> show the URL for all instances
> 
>
> Key: AMBARI-14810
> URL: https://issues.apache.org/jira/browse/AMBARI-14810
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-14810.patch, AMBARI-14810_branch-2.2.patch
>
>
> Show QuickLinks for each MR2 Job History Server instance, if there are 
> multiple



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14802) Confusing maintenance mode behaviour for host components

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15118122#comment-15118122
 ] 

Aleksandr Kovalenko commented on AMBARI-14802:
--

committed to trunk

> Confusing maintenance mode behaviour for host components
> 
>
> Key: AMBARI-14802
> URL: https://issues.apache.org/jira/browse/AMBARI-14802
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14802.patch
>
>
> *STR*
> # Turn Maintenance Mode on for some host.
> # Turn Maintenance Mode on for some component on that host.
> *Result*
> # Confusing message is displayed in popup (MM is turned on) - caused by the 
> fact that actually the sent request was to enable MM, not to disable.
> # After the second attempt request is correct, but this is useless: host 
> component MM status isn't actually changed as it's implied from host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14802) Confusing maintenance mode behaviour for host components

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14802:
-
Attachment: AMBARI-14802.patch

> Confusing maintenance mode behaviour for host components
> 
>
> Key: AMBARI-14802
> URL: https://issues.apache.org/jira/browse/AMBARI-14802
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14802.patch
>
>
> *STR*
> # Turn Maintenance Mode on for some host.
> # Turn Maintenance Mode on for some component on that host.
> *Result*
> # Confusing message is displayed in popup (MM is turned on) - caused by the 
> fact that actually the sent request was to enable MM, not to disable.
> # After the second attempt request is correct, but this is useless: host 
> component MM status isn't actually changed as it's implied from host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-14802) Confusing maintenance mode behaviour for host components

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-14802:


 Summary: Confusing maintenance mode behaviour for host components
 Key: AMBARI-14802
 URL: https://issues.apache.org/jira/browse/AMBARI-14802
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 2.4.0


*STR*
# Turn Maintenance Mode on for some host.
# Turn Maintenance Mode on for some component on that host.

*Result*
# Confusing message is displayed in popup (MM is turned on) - caused by the 
fact that actually the sent request was to enable MM, not to disable.
# After the second attempt request is correct, but this is useless: host 
component MM status isn't actually changed as it's implied from host.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14792) Install Wizard: remove persist request after step7

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115714#comment-15115714
 ] 

Aleksandr Kovalenko commented on AMBARI-14792:
--

committed to trunk

> Install Wizard: remove persist request after step7
> --
>
> Key: AMBARI-14792
> URL: https://issues.apache.org/jira/browse/AMBARI-14792
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14792.patch
>
>
> For example a use case, that may cause unexpected behavior:
> 1. Go to Install Wizard.
> 2. Proceed to step7. Change some configs and click next.
> 3. Relogin.
> 4. Proceed to step7 (again, as relogin resets all the progress).
> 5. Go to Manage Ambari.
> 6. Click on Ambari logo on the top left.
> You will be redirected back to step7, but all configs will be changed, like 
> you changed them, when you come to step7 first time (because they were 
> persisted). Also all other settings (hosts, service/components selections and 
> assignments) will be loaded from your first visit of the wizard. It even may 
> be not obvious, that something has changed and user may proceed next and 
> after deploy see, that cluster was deployed with wrong settings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14792) Install Wizard: remove persist request after step7

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115675#comment-15115675
 ] 

Aleksandr Kovalenko commented on AMBARI-14792:
--

23092 tests complete (20 seconds)
  164 tests pending


> Install Wizard: remove persist request after step7
> --
>
> Key: AMBARI-14792
> URL: https://issues.apache.org/jira/browse/AMBARI-14792
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14792.patch
>
>
> For example a use case, that may cause unexpected behavior:
> 1. Go to Install Wizard.
> 2. Proceed to step7. Change some configs and click next.
> 3. Relogin.
> 4. Proceed to step7 (again, as relogin resets all the progress).
> 5. Go to Manage Ambari.
> 6. Click on Ambari logo on the top left.
> You will be redirected back to step7, but all configs will be changed, like 
> you changed them, when you come to step7 first time (because they were 
> persisted). Also all other settings (hosts, service/components selections and 
> assignments) will be loaded from your first visit of the wizard. It even may 
> be not obvious, that something has changed and user may proceed next and 
> after deploy see, that cluster was deployed with wrong settings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14792) Install Wizard: remove persist request after step7

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14792:
-
Attachment: AMBARI-14792.patch

> Install Wizard: remove persist request after step7
> --
>
> Key: AMBARI-14792
> URL: https://issues.apache.org/jira/browse/AMBARI-14792
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14792.patch
>
>
> For example a use case, that may cause unexpected behavior:
> 1. Go to Install Wizard.
> 2. Proceed to step7. Change some configs and click next.
> 3. Relogin.
> 4. Proceed to step7 (again, as relogin resets all the progress).
> 5. Go to Manage Ambari.
> 6. Click on Ambari logo on the top left.
> You will be redirected back to step7, but all configs will be changed, like 
> you changed them, when you come to step7 first time (because they were 
> persisted). Also all other settings (hosts, service/components selections and 
> assignments) will be loaded from your first visit of the wizard. It even may 
> be not obvious, that something has changed and user may proceed next and 
> after deploy see, that cluster was deployed with wrong settings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-14792) Install Wizard: remove persist request after step7

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-14792:


 Summary: Install Wizard: remove persist request after step7
 Key: AMBARI-14792
 URL: https://issues.apache.org/jira/browse/AMBARI-14792
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 2.4.0


For example a use case, that may cause unexpected behavior:

1. Go to Install Wizard.
2. Proceed to step7. Change some configs and click next.
3. Relogin.
4. Proceed to step7 (again, as relogin resets all the progress).
5. Go to Manage Ambari.
6. Click on Ambari logo on the top left.

You will be redirected back to step7, but all configs will be changed, like you 
changed them, when you come to step7 first time (because they were persisted). 
Also all other settings (hosts, service/components selections and assignments) 
will be loaded from your first visit of the wizard. It even may be not obvious, 
that something has changed and user may proceed next and after deploy see, that 
cluster was deployed with wrong settings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14788) Alerts: Ability to customize timeout for WEB alerts in Ambari Web

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115431#comment-15115431
 ] 

Aleksandr Kovalenko commented on AMBARI-14788:
--

+1 for the patch

> Alerts: Ability to customize timeout for WEB alerts in Ambari Web
> -
>
> Key: AMBARI-14788
> URL: https://issues.apache.org/jira/browse/AMBARI-14788
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14788.patch
>
>
> WEB alerts, such as the Web UI alerts, need to have their timeout values 
> configurable from the Ambari Web UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14761) User loses all privileges after page refresh on Install Wizard

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112433#comment-15112433
 ] 

Aleksandr Kovalenko commented on AMBARI-14761:
--

This case cannot be covered by unit tests, it should be covered by system tests.

> User loses all privileges after page refresh on Install Wizard
> --
>
> Key: AMBARI-14761
> URL: https://issues.apache.org/jira/browse/AMBARI-14761
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14761.patch, AMBARI-14761_branch-rbac-sso.patch
>
>
> After step 7 in Install wizard and relogin user is unable to make page 
> refresh. After every page refresh admin user is redirected to Views page with 
> no privileges to do any action, only logout is possible. After relogin and 
> page refresh we have the same behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14761) User loses all privileges after page refresh on Install Wizard

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112436#comment-15112436
 ] 

Aleksandr Kovalenko commented on AMBARI-14761:
--

committed to trunk and branch-rbac-sso

> User loses all privileges after page refresh on Install Wizard
> --
>
> Key: AMBARI-14761
> URL: https://issues.apache.org/jira/browse/AMBARI-14761
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14761.patch, AMBARI-14761_branch-rbac-sso.patch
>
>
> After step 7 in Install wizard and relogin user is unable to make page 
> refresh. After every page refresh admin user is redirected to Views page with 
> no privileges to do any action, only logout is possible. After relogin and 
> page refresh we have the same behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14761) User loses all privileges after page refresh on Install Wizard

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14761:
-
Attachment: AMBARI-14761_branch-rbac-sso.patch

> User loses all privileges after page refresh on Install Wizard
> --
>
> Key: AMBARI-14761
> URL: https://issues.apache.org/jira/browse/AMBARI-14761
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14761.patch, AMBARI-14761_branch-rbac-sso.patch
>
>
> After step 7 in Install wizard and relogin user is unable to make page 
> refresh. After every page refresh admin user is redirected to Views page with 
> no privileges to do any action, only logout is possible. After relogin and 
> page refresh we have the same behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14748) Unable to proceed Assign Slaves step

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112373#comment-15112373
 ] 

Aleksandr Kovalenko commented on AMBARI-14748:
--

Tested on local cluster.

23074 tests complete (22 seconds)
  164 tests pending


> Unable to proceed Assign Slaves step
> 
>
> Key: AMBARI-14748
> URL: https://issues.apache.org/jira/browse/AMBARI-14748
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14748.patch
>
>
> Go to Install Wizard, go to Assign Slaves and Clients step and immediately 
> (in first second) click on Next. JS error will appear and Next button will 
> not work until page refresh. If user comes a step back, Next button on Assign 
> Masters step will not work too.
> {noformat}
> Uncaught TypeError: Cannot read property 'length' of undefined
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14761) User loses all privileges after page refresh on Install Wizard

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14761:
-
Attachment: AMBARI-14761.patch

> User loses all privileges after page refresh on Install Wizard
> --
>
> Key: AMBARI-14761
> URL: https://issues.apache.org/jira/browse/AMBARI-14761
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-14761.patch
>
>
> After step 7 in Install wizard and relogin user is unable to make page 
> refresh. After every page refresh admin user is redirected to Views page with 
> no privileges to do any action, only logout is possible. After relogin and 
> page refresh we have the same behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-14761) User loses all privileges after page refresh on Install Wizard

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-14761:


 Summary: User loses all privileges after page refresh on Install 
Wizard
 Key: AMBARI-14761
 URL: https://issues.apache.org/jira/browse/AMBARI-14761
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
 Fix For: 2.4.0


After step 7 in Install wizard and relogin user is unable to make page refresh. 
After every page refresh admin user is redirected to Views page with no 
privileges to do any action, only logout is possible. After relogin and page 
refresh we have the same behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14574) multiple clicks on "Next" button causes skipping of steps while installing a cluster

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110789#comment-15110789
 ] 

Aleksandr Kovalenko commented on AMBARI-14574:
--

+1 for the patch

> multiple clicks on "Next" button causes skipping of steps while installing a 
> cluster
> 
>
> Key: AMBARI-14574
> URL: https://issues.apache.org/jira/browse/AMBARI-14574
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.1
>Reporter: Keta Patel
>Assignee: Keta Patel
> Attachments: AMBARI-14574.patch, 
> AMBARI-14574_Jan19_only_nextBtnClickInProgress.patch, 
> AMBARI-14574_Jan19_with_transitionInProgress.patch, 
> AMBARI-14574_Jan20_manual_testing.patch, AMBARI-14574_Jan20_with_fix.patch, 
> attempt_1_controller.tiff, attempt_1_installer.tiff, 
> attempt_2_controller.tiff, attempt_2_installer.tiff, 
> attempt_3_adding_check_for_step1.tiff, 
> attempt_3_removing_check_from_step3.tiff
>
>
> On installation wizard, multiple clicks on the "Next" button can cause 
> skipping of steps. The timing of the 2nd click decides if that click will be 
> processed again or not. The following JIRAs had the same issue:
> AMBARI-7195
> AMBARI-7315
> The fix for the above issues helps to resolve most part of the problem. But 
> if the user happened to click again at the point when the last callback 
> function has just completed (and thus, has made the "Next" button clickable 
> again) but the next step has not yet completed its rendering, then the 2nd 
> click gets processed again. The "current step" was already updated in the 
> code to point to the next step, from the 1st click. So when this 2nd click 
> calls the "next" function in the router, the subsequent step of the "current 
> step" gets set as the current step. As a result we skip steps.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14748) Unable to proceed Assign Slaves step

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14748:
-
Attachment: AMBARI-14748.patch

> Unable to proceed Assign Slaves step
> 
>
> Key: AMBARI-14748
> URL: https://issues.apache.org/jira/browse/AMBARI-14748
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14748.patch
>
>
> Go to Install Wizard, go to Assign Slaves and Clients step and immediately 
> (in first second) click on Next. JS error will appear and Next button will 
> not work until page refresh. If user comes a step back, Next button on Assign 
> Masters step will not work too.
> {noformat}
> Uncaught TypeError: Cannot read property 'length' of undefined
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-14748) Unable to proceed Assign Slaves step

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-14748:


 Summary: Unable to proceed Assign Slaves step
 Key: AMBARI-14748
 URL: https://issues.apache.org/jira/browse/AMBARI-14748
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 2.4.0


Go to Install Wizard, go to Assign Slaves and Clients step and immediately (in 
first second) click on Next. JS error will appear and Next button will not work 
until page refresh. If user comes a step back, Next button on Assign Masters 
step will not work too.

{noformat}
Uncaught TypeError: Cannot read property 'length' of undefined
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14724) Provide option to +Add Oozie Server in Service Actions menu

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108922#comment-15108922
 ] 

Aleksandr Kovalenko commented on AMBARI-14724:
--

It is floating unit test failure, it will be fixed in separate commit soon.
I have run unit tests locally a lot of times and every time got success.

  23115 tests complete (16 seconds)
  165 tests pending


> Provide option to +Add Oozie Server in Service Actions menu
> ---
>
> Key: AMBARI-14724
> URL: https://issues.apache.org/jira/browse/AMBARI-14724
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14724.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14742) Custom time range has broken situations

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108840#comment-15108840
 ] 

Aleksandr Kovalenko commented on AMBARI-14742:
--

+1 for patches

> Custom time range has broken situations
> ---
>
> Key: AMBARI-14742
> URL: https://issues.apache.org/jira/browse/AMBARI-14742
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.2.1
>
> Attachments: AMBARI-14742.patch, AMBARI-14742_22.patch, 
> time-broken.pptx
>
>
> See attached for two bugs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-14724) Provide option to +Add Oozie Server in Service Actions menu

[Aleksandr Kovalenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-14724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksandr Kovalenko updated AMBARI-14724:
-
Attachment: AMBARI-14724.patch

> Provide option to +Add Oozie Server in Service Actions menu
> ---
>
> Key: AMBARI-14724
> URL: https://issues.apache.org/jira/browse/AMBARI-14724
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>    Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14724.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-14724) Provide option to +Add Oozie Server in Service Actions menu

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-14724:


 Summary: Provide option to +Add Oozie Server in Service Actions 
menu
 Key: AMBARI-14724
 URL: https://issues.apache.org/jira/browse/AMBARI-14724
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
 Fix For: 2.4.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-14719) After enabling NN HA AMS shows critical alert

[Aleksandr Kovalenko (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMBARI-14719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106745#comment-15106745
 ] 

Aleksandr Kovalenko commented on AMBARI-14719:
--

+1 for patches

> After enabling NN HA AMS shows critical alert
> -
>
> Key: AMBARI-14719
> URL: https://issues.apache.org/jira/browse/AMBARI-14719
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.1
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Fix For: 2.2.1
>
> Attachments: AMBARI-14719.patch, AMBARI-14719_branch_2.2.patch
>
>
> 1. deploy cluster with few services
> 2. Enable NN HA
> 3. stop ambari metrics
> 4. Update configs:
> "Metrics Service operation mode" :"distributed"
> "hbase.cluster.distributed": "true"
> "hbase.rootdir": "hdfs://nameservice/amshbase"
> 5. restart ambari metrcis
> Expected: ambari metrics is up and running and no alerts should be present
> Actual: 1 critical alert present on metrics
> NOTE: test might have also enabled security after teh above mentioneds teps 
> but teh metrics alert starts showing up after NN HA.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)