[jira] [Created] (AMBARI-16775) Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and 'YARN Memory per Daemon' which is a 'Label'.
Andrii Tkach created AMBARI-16775: - Summary: Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and 'YARN Memory per Daemon' which is a 'Label'. Key: AMBARI-16775 URL: https://issues.apache.org/jira/browse/AMBARI-16775 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.4.0 Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and 'YARN Memory per Daemon' which is a 'Label'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16793) Popup size changes when clicking to highlight
[ https://issues.apache.org/jira/browse/AMBARI-16793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15293146#comment-15293146 ] Andrii Tkach commented on AMBARI-16793: --- +1 for the patch > Popup size changes when clicking to highlight > - > > Key: AMBARI-16793 > URL: https://issues.apache.org/jira/browse/AMBARI-16793 > 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-16793.patch > > > STR: > # On host registration page open operation progress > # Click to highlight > Result: Popup size changes when clicking to highlight > Look at the attached video. > Is it expected? For me looks like popup window should not change size. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16819) zookeeper-env template has incorrect name on UI
[ https://issues.apache.org/jira/browse/AMBARI-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16819: -- Resolution: Fixed Status: Resolved (was: Patch Available) > zookeeper-env template has incorrect name on UI > --- > > Key: AMBARI-16819 > URL: https://issues.apache.org/jira/browse/AMBARI-16819 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16819.patch, oozie.png > > > STR: > Go to Customize Services page -> Oozie tab -> Advanced oozie-env > Expected: *zookeeper-env template* > Actually: *content* > The same on the other services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16819) zookeeper-env template has incorrect name on UI
[ https://issues.apache.org/jira/browse/AMBARI-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296419#comment-15296419 ] Andrii Tkach commented on AMBARI-16819: --- committed to trunk and branch-2.4 > zookeeper-env template has incorrect name on UI > --- > > Key: AMBARI-16819 > URL: https://issues.apache.org/jira/browse/AMBARI-16819 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16819.patch, oozie.png > > > STR: > Go to Customize Services page -> Oozie tab -> Advanced oozie-env > Expected: *zookeeper-env template* > Actually: *content* > The same on the other services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16775) Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and 'YARN Memory per Daemon' which is a 'Label'.
[ https://issues.apache.org/jira/browse/AMBARI-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15291507#comment-15291507 ] Andrii Tkach commented on AMBARI-16775: --- 27827 tests complete (25 seconds) 154 tests pending > Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and > 'YARN Memory per Daemon' which is a 'Label'. > - > > Key: AMBARI-16775 > URL: https://issues.apache.org/jira/browse/AMBARI-16775 > 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-16775.patch > > > Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and > 'YARN Memory per Daemon' which is a 'Label'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16775) Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and 'YARN Memory per Daemon' which is a 'Label'.
[ https://issues.apache.org/jira/browse/AMBARI-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16775: -- Attachment: AMBARI-16775.patch > Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and > 'YARN Memory per Daemon' which is a 'Label'. > - > > Key: AMBARI-16775 > URL: https://issues.apache.org/jira/browse/AMBARI-16775 > 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-16775.patch > > > Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and > 'YARN Memory per Daemon' which is a 'Label'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16775) Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and 'YARN Memory per Daemon' which is a 'Label'.
[ https://issues.apache.org/jira/browse/AMBARI-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16775: -- Status: Patch Available (was: Open) > Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and > 'YARN Memory per Daemon' which is a 'Label'. > - > > Key: AMBARI-16775 > URL: https://issues.apache.org/jira/browse/AMBARI-16775 > 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-16775.patch > > > Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and > 'YARN Memory per Daemon' which is a 'Label'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16819) zookeeper-env template has incorrect name on UI
[ https://issues.apache.org/jira/browse/AMBARI-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16819: -- Attachment: AMBARI-16819.patch > zookeeper-env template has incorrect name on UI > --- > > Key: AMBARI-16819 > URL: https://issues.apache.org/jira/browse/AMBARI-16819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16819.patch, oozie.png > > > STR: > Go to Customize Services page -> Oozie tab -> Advanced oozie-env > Expected: *zookeeper-env template* > Actually: *content* > The same on the other services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16819) zookeeper-env template has incorrect name on UI
[ https://issues.apache.org/jira/browse/AMBARI-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15296360#comment-15296360 ] Andrii Tkach commented on AMBARI-16819: --- 27834 tests complete (28 seconds) 154 tests pending > zookeeper-env template has incorrect name on UI > --- > > Key: AMBARI-16819 > URL: https://issues.apache.org/jira/browse/AMBARI-16819 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16819.patch, oozie.png > > > STR: > Go to Customize Services page -> Oozie tab -> Advanced oozie-env > Expected: *zookeeper-env template* > Actually: *content* > The same on the other services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16819) zookeeper-env template has incorrect name on UI
[ https://issues.apache.org/jira/browse/AMBARI-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16819: -- Status: Patch Available (was: Open) > zookeeper-env template has incorrect name on UI > --- > > Key: AMBARI-16819 > URL: https://issues.apache.org/jira/browse/AMBARI-16819 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16819.patch, oozie.png > > > STR: > Go to Customize Services page -> Oozie tab -> Advanced oozie-env > Expected: *zookeeper-env template* > Actually: *content* > The same on the other services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16819) zookeeper-env template has incorrect name on UI
[ https://issues.apache.org/jira/browse/AMBARI-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16819: -- Component/s: ambari-server > zookeeper-env template has incorrect name on UI > --- > > Key: AMBARI-16819 > URL: https://issues.apache.org/jira/browse/AMBARI-16819 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16819.patch, oozie.png > > > STR: > Go to Customize Services page -> Oozie tab -> Advanced oozie-env > Expected: *zookeeper-env template* > Actually: *content* > The same on the other services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16819) zookeeper-env template has incorrect name on U
[ https://issues.apache.org/jira/browse/AMBARI-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16819: -- Attachment: oozie.png > zookeeper-env template has incorrect name on U > -- > > Key: AMBARI-16819 > URL: https://issues.apache.org/jira/browse/AMBARI-16819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: oozie.png > > > STR: > Go to Customize Services page -> Oozie tab -> Advanced oozie-env > Expected: *zookeeper-env template* > Actually: *content* > The same on the other services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16819) zookeeper-env template has incorrect name on U
Andrii Tkach created AMBARI-16819: - Summary: zookeeper-env template has incorrect name on U Key: AMBARI-16819 URL: https://issues.apache.org/jira/browse/AMBARI-16819 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.4.0 Attachments: oozie.png STR: Go to Customize Services page -> Oozie tab -> Advanced oozie-env Expected: *zookeeper-env template* Actually: *content* The same on the other services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16819) zookeeper-env template has incorrect name on UI
[ https://issues.apache.org/jira/browse/AMBARI-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16819: -- Summary: zookeeper-env template has incorrect name on UI (was: zookeeper-env template has incorrect name on U) > zookeeper-env template has incorrect name on UI > --- > > Key: AMBARI-16819 > URL: https://issues.apache.org/jira/browse/AMBARI-16819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: oozie.png > > > STR: > Go to Customize Services page -> Oozie tab -> Advanced oozie-env > Expected: *zookeeper-env template* > Actually: *content* > The same on the other services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16845) Can not open BG operations after RU
[ https://issues.apache.org/jira/browse/AMBARI-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16845: -- Attachment: recor12.mkv > Can not open BG operations after RU > --- > > Key: AMBARI-16845 > URL: https://issues.apache.org/jira/browse/AMBARI-16845 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.4.0 > > Attachments: recor12.mkv > > > STR: > # Deploy old HDP (e.g 2.2) > # Register couple of stack versions (e.g. 2.5.0.0, 2.4.3) > # Install one of them (e.g 2.4.3) > # Start RU to 2.4.3 > # During RU start version 2.5.0.0 installation > Result: after RU you can not open BG operations, installation will proceed, > but never finished. > After some time stack version installation has been finished, but BG > operation popup could not be opened. > Please look at the attached video. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16845) Can not open BG operations after RU
Andrii Tkach created AMBARI-16845: - Summary: Can not open BG operations after RU Key: AMBARI-16845 URL: https://issues.apache.org/jira/browse/AMBARI-16845 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Blocker Fix For: 2.4.0 STR: # Deploy old HDP (e.g 2.2) # Register couple of stack versions (e.g. 2.5.0.0, 2.4.3) # Install one of them (e.g 2.4.3) # Start RU to 2.4.3 # During RU start version 2.5.0.0 installation Result: after RU you can not open BG operations, installation will proceed, but never finished. After some time stack version installation has been finished, but BG operation popup could not be opened. Please look at the attached video. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16845) Can not open BG operations after RU
[ https://issues.apache.org/jira/browse/AMBARI-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16845: -- Attachment: AMBARI-16845.patch > Can not open BG operations after RU > --- > > Key: AMBARI-16845 > URL: https://issues.apache.org/jira/browse/AMBARI-16845 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16845.patch, recor12.mkv > > > STR: > # Deploy old HDP (e.g 2.2) > # Register couple of stack versions (e.g. 2.5.0.0, 2.4.3) > # Install one of them (e.g 2.4.3) > # Start RU to 2.4.3 > # During RU start version 2.5.0.0 installation > Result: after RU you can not open BG operations, installation will proceed, > but never finished. > After some time stack version installation has been finished, but BG > operation popup could not be opened. > Please look at the attached video. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16845) Can not open BG operations after RU
[ https://issues.apache.org/jira/browse/AMBARI-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15298248#comment-15298248 ] Andrii Tkach commented on AMBARI-16845: --- 27838 tests complete (27 seconds) 154 tests pending > Can not open BG operations after RU > --- > > Key: AMBARI-16845 > URL: https://issues.apache.org/jira/browse/AMBARI-16845 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16845.patch, recor12.mkv > > > STR: > # Deploy old HDP (e.g 2.2) > # Register couple of stack versions (e.g. 2.5.0.0, 2.4.3) > # Install one of them (e.g 2.4.3) > # Start RU to 2.4.3 > # During RU start version 2.5.0.0 installation > Result: after RU you can not open BG operations, installation will proceed, > but never finished. > After some time stack version installation has been finished, but BG > operation popup could not be opened. > Please look at the attached video. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16845) Can not open BG operations after RU
[ https://issues.apache.org/jira/browse/AMBARI-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16845: -- Status: Patch Available (was: Open) > Can not open BG operations after RU > --- > > Key: AMBARI-16845 > URL: https://issues.apache.org/jira/browse/AMBARI-16845 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16845.patch, recor12.mkv > > > STR: > # Deploy old HDP (e.g 2.2) > # Register couple of stack versions (e.g. 2.5.0.0, 2.4.3) > # Install one of them (e.g 2.4.3) > # Start RU to 2.4.3 > # During RU start version 2.5.0.0 installation > Result: after RU you can not open BG operations, installation will proceed, > but never finished. > After some time stack version installation has been finished, but BG > operation popup could not be opened. > Please look at the attached video. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16845) Can not open BG operations after RU
[ https://issues.apache.org/jira/browse/AMBARI-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16845: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Can not open BG operations after RU > --- > > Key: AMBARI-16845 > URL: https://issues.apache.org/jira/browse/AMBARI-16845 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16845.patch, recor12.mkv > > > STR: > # Deploy old HDP (e.g 2.2) > # Register couple of stack versions (e.g. 2.5.0.0, 2.4.3) > # Install one of them (e.g 2.4.3) > # Start RU to 2.4.3 > # During RU start version 2.5.0.0 installation > Result: after RU you can not open BG operations, installation will proceed, > but never finished. > After some time stack version installation has been finished, but BG > operation popup could not be opened. > Please look at the attached video. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16845) Can not open BG operations after RU
[ https://issues.apache.org/jira/browse/AMBARI-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15298363#comment-15298363 ] Andrii Tkach commented on AMBARI-16845: --- committed to trunk and branch-2.4 > Can not open BG operations after RU > --- > > Key: AMBARI-16845 > URL: https://issues.apache.org/jira/browse/AMBARI-16845 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.4.0 > > Attachments: AMBARI-16845.patch, recor12.mkv > > > STR: > # Deploy old HDP (e.g 2.2) > # Register couple of stack versions (e.g. 2.5.0.0, 2.4.3) > # Install one of them (e.g 2.4.3) > # Start RU to 2.4.3 > # During RU start version 2.5.0.0 installation > Result: after RU you can not open BG operations, installation will proceed, > but never finished. > After some time stack version installation has been finished, but BG > operation popup could not be opened. > Please look at the attached video. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16775) Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and 'YARN Memory per Daemon' which is a 'Label'.
[ https://issues.apache.org/jira/browse/AMBARI-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15291691#comment-15291691 ] Andrii Tkach commented on AMBARI-16775: --- committed to trunk and branch-2.4 > Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and > 'YARN Memory per Daemon' which is a 'Label'. > - > > Key: AMBARI-16775 > URL: https://issues.apache.org/jira/browse/AMBARI-16775 > 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-16775.patch > > > Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and > 'YARN Memory per Daemon' which is a 'Label'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16775) Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and 'YARN Memory per Daemon' which is a 'Label'.
[ https://issues.apache.org/jira/browse/AMBARI-16775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16775: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and > 'YARN Memory per Daemon' which is a 'Label'. > - > > Key: AMBARI-16775 > URL: https://issues.apache.org/jira/browse/AMBARI-16775 > 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-16775.patch > > > Add units (MB) to 'In-Memory Cache per Daemon' which is a 'Text Box' and > 'YARN Memory per Daemon' which is a 'Label'. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16287) BGOperations is taking very long time to finish
[ https://issues.apache.org/jira/browse/AMBARI-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15279921#comment-15279921 ] Andrii Tkach commented on AMBARI-16287: --- committed to trunk > BGOperations is taking very long time to finish > --- > > Key: AMBARI-16287 > URL: https://issues.apache.org/jira/browse/AMBARI-16287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16287.patch > > > Kerb split with add host, add services, add components split has tarted > taking long time to finish due to BGOperations taking very long time to > finish. > This is what this split does: > Deploy cluster with very few services > EnableKerberos > TestKerberosKeytabsAndPrincipal > Add remaining Services > AddHost > AddingComponents > Run SmokeTests on all -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16287) BGOperations is taking very long time to finish
[ https://issues.apache.org/jira/browse/AMBARI-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16287: -- Resolution: Fixed Status: Resolved (was: Patch Available) > BGOperations is taking very long time to finish > --- > > Key: AMBARI-16287 > URL: https://issues.apache.org/jira/browse/AMBARI-16287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16287.patch > > > Kerb split with add host, add services, add components split has tarted > taking long time to finish due to BGOperations taking very long time to > finish. > This is what this split does: > Deploy cluster with very few services > EnableKerberos > TestKerberosKeytabsAndPrincipal > Add remaining Services > AddHost > AddingComponents > Run SmokeTests on all -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16643) Ambari allows installing a component on more than one host even with cardinality as 0-1
Andrii Tkach created AMBARI-16643: - Summary: Ambari allows installing a component on more than one host even with cardinality as 0-1 Key: AMBARI-16643 URL: https://issues.apache.org/jira/browse/AMBARI-16643 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.2.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.4.0 ACTIVITY_ANALYZER is configured to have cardinality of 0-1, however from hosts page I would add service to two hosts. User should have been prevented from adding additional more than once instance of this slave as it violates the cardinality constraint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16643) Ambari allows installing a component on more than one host even with cardinality as 0-1
[ https://issues.apache.org/jira/browse/AMBARI-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16643: -- Status: Patch Available (was: Open) > Ambari allows installing a component on more than one host even with > cardinality as 0-1 > --- > > Key: AMBARI-16643 > URL: https://issues.apache.org/jira/browse/AMBARI-16643 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16643.patch, image-2016-05-03-11-40-49-268.png > > > ACTIVITY_ANALYZER is configured to have cardinality of 0-1, however from > hosts page I would add service to two hosts. > User should have been prevented from adding additional more than once > instance of this slave as it violates the cardinality constraint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16643) Ambari allows installing a component on more than one host even with cardinality as 0-1
[ https://issues.apache.org/jira/browse/AMBARI-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16643: -- Attachment: image-2016-05-03-11-40-49-268.png > Ambari allows installing a component on more than one host even with > cardinality as 0-1 > --- > > Key: AMBARI-16643 > URL: https://issues.apache.org/jira/browse/AMBARI-16643 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: image-2016-05-03-11-40-49-268.png > > > ACTIVITY_ANALYZER is configured to have cardinality of 0-1, however from > hosts page I would add service to two hosts. > User should have been prevented from adding additional more than once > instance of this slave as it violates the cardinality constraint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16643) Ambari allows installing a component on more than one host even with cardinality as 0-1
[ https://issues.apache.org/jira/browse/AMBARI-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16643: -- Attachment: AMBARI-16643.patch > Ambari allows installing a component on more than one host even with > cardinality as 0-1 > --- > > Key: AMBARI-16643 > URL: https://issues.apache.org/jira/browse/AMBARI-16643 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16643.patch, image-2016-05-03-11-40-49-268.png > > > ACTIVITY_ANALYZER is configured to have cardinality of 0-1, however from > hosts page I would add service to two hosts. > User should have been prevented from adding additional more than once > instance of this slave as it violates the cardinality constraint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16685: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16685.patch, kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15286262#comment-15286262 ] Andrii Tkach commented on AMBARI-16685: --- committed to trunk and branch-2.4 > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16685.patch, kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16682: -- Status: Patch Available (was: Open) > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16684) Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when installed HDP-2.2
[ https://issues.apache.org/jira/browse/AMBARI-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284809#comment-15284809 ] Andrii Tkach commented on AMBARI-16684: --- +1 for the patch > Ranger Tagsync component (added in HDP-2.5) is shown under Summary Tab when > installed HDP-2.2 > - > > Key: AMBARI-16684 > URL: https://issues.apache.org/jira/browse/AMBARI-16684 > 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-16684.patch > > > Hide Ranger Tagsync row from summary page if component is not included in > installed stack -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284812#comment-15284812 ] Andrii Tkach commented on AMBARI-16685: --- 27815 tests complete (25 seconds) 154 tests pending > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16685.patch, kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16685: -- Status: Patch Available (was: Open) > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16685.patch, kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16685: -- Attachment: AMBARI-16685.patch > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-16685.patch, kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16685) Kerberos page: Cancel clear config values
[ https://issues.apache.org/jira/browse/AMBARI-16685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16685: -- Attachment: kerberos_page.png > Kerberos page: Cancel clear config values > - > > Key: AMBARI-16685 > URL: https://issues.apache.org/jira/browse/AMBARI-16685 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: kerberos_page.png > > > *Steps to reproduce:* > # Enable Kerberos service > # Go to Admin -> Kerberos page > # Click "Edit" > # Hit Cancel button > *Actual result:* > All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16685) Kerberos page: Cancel clear config values
Andrii Tkach created AMBARI-16685: - Summary: Kerberos page: Cancel clear config values Key: AMBARI-16685 URL: https://issues.apache.org/jira/browse/AMBARI-16685 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.4.0 Attachments: kerberos_page.png *Steps to reproduce:* # Enable Kerberos service # Go to Admin -> Kerberos page # Click "Edit" # Hit Cancel button *Actual result:* All configs have empty values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
Andrii Tkach created AMBARI-16682: - Summary: After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled Key: AMBARI-16682 URL: https://issues.apache.org/jira/browse/AMBARI-16682 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.4.0 This was not observed as part of the system test While testing the new delete feature, I observed this 1) enable Kerberos 2) Delete Kerberos from UI 3) The kerberos tab still shows it enabled How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16682: -- Resolution: Fixed Status: Resolved (was: Patch Available) > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284737#comment-15284737 ] Andrii Tkach commented on AMBARI-16682: --- committed to trunk and branch-2.4 > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16682: -- Attachment: AMBARI-16682.patch > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16682: -- Attachment: Screen Shot 2016-05-10 at 2.41.02 PM.png > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: Screen Shot 2016-05-10 at 2.41.02 PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16682) After deleting Kerberos (while enabled), Kerberos tab still shows it as enabled
[ https://issues.apache.org/jira/browse/AMBARI-16682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15284721#comment-15284721 ] Andrii Tkach commented on AMBARI-16682: --- 27817 tests complete (26 seconds) 154 tests pending > After deleting Kerberos (while enabled), Kerberos tab still shows it as > enabled > --- > > Key: AMBARI-16682 > URL: https://issues.apache.org/jira/browse/AMBARI-16682 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16682.patch, Screen Shot 2016-05-10 at 2.41.02 > PM.png > > > This was not observed as part of the system test > While testing the new delete feature, I observed this > 1) enable Kerberos > 2) Delete Kerberos from UI > 3) The kerberos tab still shows it enabled > How should Kerberos deletion be handled? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16660) Kerberos Configs Page issues
Andrii Tkach created AMBARI-16660: - Summary: Kerberos Configs Page issues Key: AMBARI-16660 URL: https://issues.apache.org/jira/browse/AMBARI-16660 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.4.0 1st issue: Kerberos Configs page contains message: Attention: Some configurations need your attention before you can proceed. Show me properties with issues Clicking on "Show me properties with issues" shows: No properties to display. 2nd issue: Clicking in "Edit"-link doesn't do anything (inputs with configs don't become editable). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16660) Kerberos Configs Page issues
[ https://issues.apache.org/jira/browse/AMBARI-16660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16660: -- Attachment: AMBARI-16660.patch > Kerberos Configs Page issues > > > Key: AMBARI-16660 > URL: https://issues.apache.org/jira/browse/AMBARI-16660 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16660.patch > > > 1st issue: > Kerberos Configs page contains message: > Attention: Some configurations need your attention before you can proceed. > Show me properties with issues > Clicking on "Show me properties with issues" shows: > No properties to display. > 2nd issue: > Clicking in "Edit"-link doesn't do anything (inputs with configs don't become > editable). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16643) Ambari allows installing a component on more than one host even with cardinality as 0-1
[ https://issues.apache.org/jira/browse/AMBARI-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282714#comment-15282714 ] Andrii Tkach commented on AMBARI-16643: --- Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 approved: 1414 licence. > Ambari allows installing a component on more than one host even with > cardinality as 0-1 > --- > > Key: AMBARI-16643 > URL: https://issues.apache.org/jira/browse/AMBARI-16643 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16643.patch, image-2016-05-03-11-40-49-268.png > > > ACTIVITY_ANALYZER is configured to have cardinality of 0-1, however from > hosts page I would add service to two hosts. > User should have been prevented from adding additional more than once > instance of this slave as it violates the cardinality constraint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16643) Ambari allows installing a component on more than one host even with cardinality as 0-1
[ https://issues.apache.org/jira/browse/AMBARI-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16643: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari allows installing a component on more than one host even with > cardinality as 0-1 > --- > > Key: AMBARI-16643 > URL: https://issues.apache.org/jira/browse/AMBARI-16643 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16643.patch, image-2016-05-03-11-40-49-268.png > > > ACTIVITY_ANALYZER is configured to have cardinality of 0-1, however from > hosts page I would add service to two hosts. > User should have been prevented from adding additional more than once > instance of this slave as it violates the cardinality constraint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16660) Kerberos Configs Page issues
[ https://issues.apache.org/jira/browse/AMBARI-16660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282745#comment-15282745 ] Andrii Tkach commented on AMBARI-16660: --- 27802 tests complete (25 seconds) 154 tests pending > Kerberos Configs Page issues > > > Key: AMBARI-16660 > URL: https://issues.apache.org/jira/browse/AMBARI-16660 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16660.patch > > > 1st issue: > Kerberos Configs page contains message: > Attention: Some configurations need your attention before you can proceed. > Show me properties with issues > Clicking on "Show me properties with issues" shows: > No properties to display. > 2nd issue: > Clicking in "Edit"-link doesn't do anything (inputs with configs don't become > editable). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16660) Kerberos Configs Page issues
[ https://issues.apache.org/jira/browse/AMBARI-16660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16660: -- Status: Patch Available (was: Open) > Kerberos Configs Page issues > > > Key: AMBARI-16660 > URL: https://issues.apache.org/jira/browse/AMBARI-16660 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16660.patch > > > 1st issue: > Kerberos Configs page contains message: > Attention: Some configurations need your attention before you can proceed. > Show me properties with issues > Clicking on "Show me properties with issues" shows: > No properties to display. > 2nd issue: > Clicking in "Edit"-link doesn't do anything (inputs with configs don't become > editable). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16661) Provide Information Message About Suspended Alerts During Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-16661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282801#comment-15282801
]
Andrii Tkach commented on AMBARI-16661:
---
+1 for the patch
> Provide Information Message About Suspended Alerts During Upgrade
> -
>
> Key: AMBARI-16661
> URL: https://issues.apache.org/jira/browse/AMBARI-16661
> 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-16661.patch
>
>
> Ambari now suspends most outbound notifications during an HDP upgrade.
> Although the alerts will still show in the UI, the Ambari server will not
> dispatch alerts while:
> - An upgrade is in progress
> - An existing upgrade is suspended
> There are some alerts, however, which still remain active for triggering
> outbound notifications. These deal with mostly {{AMBARI/AMBARI_SERVER}} and
> {{AMBARI/AMBARI_AGENT}} alerts which are not associated with a cluster. For
> example:
> - Agent Disk Usage
> - Agent Heartbeats
> - Ambari Performance
> ... will all still produce notifications.
> The web client should provide an informational dialog that lets
> administrators know that outbound alerts, if configured, will be mostly
> suppressed during the upgrade. The web client can even see if there are any
> alert targets defined, and choose not to show the message if there are none
> configured.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16660) Kerberos Configs Page issues
[
https://issues.apache.org/jira/browse/AMBARI-16660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282809#comment-15282809
]
Andrii Tkach commented on AMBARI-16660:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12803870/AMBARI-16660.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
> Kerberos Configs Page issues
>
>
> Key: AMBARI-16660
> URL: https://issues.apache.org/jira/browse/AMBARI-16660
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16660.patch
>
>
> 1st issue:
> Kerberos Configs page contains message:
> Attention: Some configurations need your attention before you can proceed.
> Show me properties with issues
> Clicking on "Show me properties with issues" shows:
> No properties to display.
> 2nd issue:
> Clicking in "Edit"-link doesn't do anything (inputs with configs don't become
> editable).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16729) When selecting cluster capacity to 100% for llap queue, user is not shown warning
[ https://issues.apache.org/jira/browse/AMBARI-16729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15288858#comment-15288858 ] Andrii Tkach commented on AMBARI-16729: --- +1 for the patch > When selecting cluster capacity to 100% for llap queue, user is not shown > warning > - > > Key: AMBARI-16729 > URL: https://issues.apache.org/jira/browse/AMBARI-16729 > 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-16729.patch > > > Enable HS2 Interactive > Update % cluster capacity property to 100% (by default is 25%) > Expected: LLAP will consume this entire YARN queue. The admin needs to be > warned of this fact. > Actual: No warning is displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16633) 'Download CSV' button in Add Service Wizard is not performing any action
[ https://issues.apache.org/jira/browse/AMBARI-16633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15281396#comment-15281396 ] Andrii Tkach commented on AMBARI-16633: --- +1 for the patch > 'Download CSV' button in Add Service Wizard is not performing any action > > > Key: AMBARI-16633 > URL: https://issues.apache.org/jira/browse/AMBARI-16633 > 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-16633.patch, Screen Shot 2016-05-09 at 10.31.29 > PM.png > > > - On a cluster deployed via blueprint, navigate to Add Service Wizard > - Choose LogSearch > - Proceed till review Page > - Choose to 'Download CSV' > - This button present is not doing any action > - Tested in Chrome, Firefox and Safari -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16287) BGOperations is taking very long time to finish
[ https://issues.apache.org/jira/browse/AMBARI-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16287: -- Attachment: (was: AMBARI-16287.patch) > BGOperations is taking very long time to finish > --- > > Key: AMBARI-16287 > URL: https://issues.apache.org/jira/browse/AMBARI-16287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > > Kerb split with add host, add services, add components split has tarted > taking long time to finish due to BGOperations taking very long time to > finish. > This is what this split does: > Deploy cluster with very few services > EnableKerberos > TestKerberosKeytabsAndPrincipal > Add remaining Services > AddHost > AddingComponents > Run SmokeTests on all -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16287) BGOperations is taking very long time to finish
[ https://issues.apache.org/jira/browse/AMBARI-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16287: -- Status: Open (was: Patch Available) > BGOperations is taking very long time to finish > --- > > Key: AMBARI-16287 > URL: https://issues.apache.org/jira/browse/AMBARI-16287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16287.patch > > > Kerb split with add host, add services, add components split has tarted > taking long time to finish due to BGOperations taking very long time to > finish. > This is what this split does: > Deploy cluster with very few services > EnableKerberos > TestKerberosKeytabsAndPrincipal > Add remaining Services > AddHost > AddingComponents > Run SmokeTests on all -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16287) BGOperations is taking very long time to finish
[ https://issues.apache.org/jira/browse/AMBARI-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16287: -- Status: Patch Available (was: Open) > BGOperations is taking very long time to finish > --- > > Key: AMBARI-16287 > URL: https://issues.apache.org/jira/browse/AMBARI-16287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16287.patch > > > Kerb split with add host, add services, add components split has tarted > taking long time to finish due to BGOperations taking very long time to > finish. > This is what this split does: > Deploy cluster with very few services > EnableKerberos > TestKerberosKeytabsAndPrincipal > Add remaining Services > AddHost > AddingComponents > Run SmokeTests on all -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16257) Cover Kerberos wizard controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-16257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16257: -- Status: Patch Available (was: Open) > Cover Kerberos wizard controllers with unit tests > - > > Key: AMBARI-16257 > URL: https://issues.apache.org/jira/browse/AMBARI-16257 > 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-16257.patch > > > Cover following files with unit tests: > * ambari-web/app/controllers/main/admin/kerberos/step1_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step3_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step5_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step6_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step7_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step8_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step4_controller.js > * ambari-web/app/controllers/main/admin/kerberos/disable_controller.js > * ambari-web/app/controllers/main/admin/kerberos/wizard_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16257) Cover Kerberos wizard controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-16257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15271071#comment-15271071 ] Andrii Tkach commented on AMBARI-16257: --- 27719 tests complete (27 seconds) 154 tests pending > Cover Kerberos wizard controllers with unit tests > - > > Key: AMBARI-16257 > URL: https://issues.apache.org/jira/browse/AMBARI-16257 > 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-16257.patch > > > Cover following files with unit tests: > * ambari-web/app/controllers/main/admin/kerberos/step1_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step3_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step5_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step6_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step7_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step8_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step4_controller.js > * ambari-web/app/controllers/main/admin/kerberos/disable_controller.js > * ambari-web/app/controllers/main/admin/kerberos/wizard_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16257) Cover Kerberos wizard controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-16257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16257: -- Attachment: AMBARI-16257.patch > Cover Kerberos wizard controllers with unit tests > - > > Key: AMBARI-16257 > URL: https://issues.apache.org/jira/browse/AMBARI-16257 > 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-16257.patch > > > Cover following files with unit tests: > * ambari-web/app/controllers/main/admin/kerberos/step1_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step3_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step5_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step6_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step7_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step8_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step4_controller.js > * ambari-web/app/controllers/main/admin/kerberos/disable_controller.js > * ambari-web/app/controllers/main/admin/kerberos/wizard_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16257) Cover Kerberos wizard controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-16257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15272178#comment-15272178 ] Andrii Tkach commented on AMBARI-16257: --- committed to trunk > Cover Kerberos wizard controllers with unit tests > - > > Key: AMBARI-16257 > URL: https://issues.apache.org/jira/browse/AMBARI-16257 > 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-16257.patch > > > Cover following files with unit tests: > * ambari-web/app/controllers/main/admin/kerberos/step1_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step3_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step5_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step6_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step7_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step8_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step4_controller.js > * ambari-web/app/controllers/main/admin/kerberos/disable_controller.js > * ambari-web/app/controllers/main/admin/kerberos/wizard_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16257) Cover Kerberos wizard controllers with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-16257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16257: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Cover Kerberos wizard controllers with unit tests > - > > Key: AMBARI-16257 > URL: https://issues.apache.org/jira/browse/AMBARI-16257 > 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-16257.patch > > > Cover following files with unit tests: > * ambari-web/app/controllers/main/admin/kerberos/step1_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step3_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step5_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step6_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step7_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step8_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js > * ambari-web/app/controllers/main/admin/kerberos/step4_controller.js > * ambari-web/app/controllers/main/admin/kerberos/disable_controller.js > * ambari-web/app/controllers/main/admin/kerberos/wizard_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16287) BGOperations is taking very long time to finish
[ https://issues.apache.org/jira/browse/AMBARI-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16287: -- Attachment: AMBARI-16287.patch > BGOperations is taking very long time to finish > --- > > Key: AMBARI-16287 > URL: https://issues.apache.org/jira/browse/AMBARI-16287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16287.patch > > > Kerb split with add host, add services, add components split has tarted > taking long time to finish due to BGOperations taking very long time to > finish. > This is what this split does: > Deploy cluster with very few services > EnableKerberos > TestKerberosKeytabsAndPrincipal > Add remaining Services > AddHost > AddingComponents > Run SmokeTests on all -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16287) BGOperations is taking very long time to finish
[ https://issues.apache.org/jira/browse/AMBARI-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16287: -- Status: Patch Available (was: Open) > BGOperations is taking very long time to finish > --- > > Key: AMBARI-16287 > URL: https://issues.apache.org/jira/browse/AMBARI-16287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16287.patch > > > Kerb split with add host, add services, add components split has tarted > taking long time to finish due to BGOperations taking very long time to > finish. > This is what this split does: > Deploy cluster with very few services > EnableKerberos > TestKerberosKeytabsAndPrincipal > Add remaining Services > AddHost > AddingComponents > Run SmokeTests on all -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16287) BGOperations is taking very long time to finish
Andrii Tkach created AMBARI-16287: - Summary: BGOperations is taking very long time to finish Key: AMBARI-16287 URL: https://issues.apache.org/jira/browse/AMBARI-16287 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.2.2 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.4.0 Kerb split with add host, add services, add components split has tarted taking long time to finish due to BGOperations taking very long time to finish. This is what this split does: Deploy cluster with very few services EnableKerberos TestKerberosKeytabsAndPrincipal Add remaining Services AddHost AddingComponents Run SmokeTests on all -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16287) BGOperations is taking very long time to finish
[ https://issues.apache.org/jira/browse/AMBARI-16287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15273979#comment-15273979 ] Andrii Tkach commented on AMBARI-16287: --- 27727 tests complete (30 seconds) 154 tests pending > BGOperations is taking very long time to finish > --- > > Key: AMBARI-16287 > URL: https://issues.apache.org/jira/browse/AMBARI-16287 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16287.patch > > > Kerb split with add host, add services, add components split has tarted > taking long time to finish due to BGOperations taking very long time to > finish. > This is what this split does: > Deploy cluster with very few services > EnableKerberos > TestKerberosKeytabsAndPrincipal > Add remaining Services > AddHost > AddingComponents > Run SmokeTests on all -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16257) Cover Kerberos wizard controllers with unit tests
Andrii Tkach created AMBARI-16257: - Summary: Cover Kerberos wizard controllers with unit tests Key: AMBARI-16257 URL: https://issues.apache.org/jira/browse/AMBARI-16257 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.4.0 Cover following files with unit tests: * ambari-web/app/controllers/main/admin/kerberos/step1_controller.js * ambari-web/app/controllers/main/admin/kerberos/step3_controller.js * ambari-web/app/controllers/main/admin/kerberos/step5_controller.js * ambari-web/app/controllers/main/admin/kerberos/step6_controller.js * ambari-web/app/controllers/main/admin/kerberos/step7_controller.js * ambari-web/app/controllers/main/admin/kerberos/step8_controller.js * ambari-web/app/controllers/main/admin/kerberos/step2_controller.js * ambari-web/app/controllers/main/admin/kerberos/step4_controller.js * ambari-web/app/controllers/main/admin/kerberos/disable_controller.js * ambari-web/app/controllers/main/admin/kerberos/wizard_controller.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16421) JS error on ASW step4 after page refresh
[
https://issues.apache.org/jira/browse/AMBARI-16421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15277846#comment-15277846
]
Andrii Tkach commented on AMBARI-16421:
---
+1 for the patch
> JS error on ASW step4 after page refresh
>
>
> Key: AMBARI-16421
> URL: https://issues.apache.org/jira/browse/AMBARI-16421
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16421.patch
>
>
> * Open ASW
> * Proceed to the step4
> * Do page refresh
> JS error appears:
> {{Uncaught TypeError: Cannot read property 'filterProperty' of null}}
> Source:
> {code:javascript}
> var selectedServices =
> this.get('content.services').filterProperty('isSelected',
> true).filterProperty('isInstalled', false).mapProperty('serviceName');
> {code}
> File:
> {{ambari/ambari-web/app/controllers/main/service/add_controller.js}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15920) Save creds checkbox is enabled, even though ambari is not config'd to save
[ https://issues.apache.org/jira/browse/AMBARI-15920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15920: -- Attachment: AMBARI-15920.patch > Save creds checkbox is enabled, even though ambari is not config'd to save > -- > > Key: AMBARI-15920 > URL: https://issues.apache.org/jira/browse/AMBARI-15920 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15920.patch, checkbox-active.tiff > > > See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15920) Save creds checkbox is enabled, even though ambari is not config'd to save
[ https://issues.apache.org/jira/browse/AMBARI-15920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15920: -- Attachment: checkbox-active.tiff > Save creds checkbox is enabled, even though ambari is not config'd to save > -- > > Key: AMBARI-15920 > URL: https://issues.apache.org/jira/browse/AMBARI-15920 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: checkbox-active.tiff > > > See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15920) Save creds checkbox is enabled, even though ambari is not config'd to save
[ https://issues.apache.org/jira/browse/AMBARI-15920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15920: -- Status: Patch Available (was: Open) > Save creds checkbox is enabled, even though ambari is not config'd to save > -- > > Key: AMBARI-15920 > URL: https://issues.apache.org/jira/browse/AMBARI-15920 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15920.patch, checkbox-active.tiff > > > See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15920) Save creds checkbox is enabled, even though ambari is not config'd to save
[ https://issues.apache.org/jira/browse/AMBARI-15920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243114#comment-15243114 ] Andrii Tkach commented on AMBARI-15920: --- 25687 tests complete (24 seconds) 154 tests pending > Save creds checkbox is enabled, even though ambari is not config'd to save > -- > > Key: AMBARI-15920 > URL: https://issues.apache.org/jira/browse/AMBARI-15920 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15920.patch, checkbox-active.tiff > > > See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15946) Make Current button doesn't work when 2 versions are being compared on Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-15946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-15946:
--
Attachment: pics (1).docx
> Make Current button doesn't work when 2 versions are being compared on Ambari
> UI
>
>
> Key: AMBARI-15946
> URL: https://issues.apache.org/jira/browse/AMBARI-15946
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.1.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: pics (1).docx
>
>
> *PROBLEM:*
> From ambari UI, we can hover mouse over the previous versions of any configs
> and we can an option to make it current. This works fine.
> We also have an feature to compare the current and previous versions. When we
> do this we get a green button *"Make V6 Current"*
> (V6 is in my cluster. It can be any version).
> If we click on this we get *"Created from service config version {0}"* pop up
> and again a Make current button.
> Click on it and everything seems ok. But the problem is the previous version
> is NOT made current.
> This works fine on Safari and firefox but *it does NOT work on chrome*.
> *Attachments:*
>
> 1. [^pics (1).docx] - screenshots.
> *BUSINESS IMPACT:* This caused us lot of issue as we all thought previous
> configs had been reinstated but it wasn't and our debugging took a complete
> detour.
> *Go Live Date -* N/A
> *STEPS TO REPRODUCE:*
> 1. Hover mouse on any previous version and click "compare".
> 2. Click "Make Current V6" (Make current for previous version).
> 3. Make current confirmation pop-up shows version {0} instead of the actual
> version number.
> 4. Click "Make Current" and restart all services marked for "restart".
> *EXPECTED RESULT:* The version I choose to make current should be applied.
> *ACTUAL RESULT:* Previous version is not made current.
> *SUPPORT ANALYSIS:* Reproduced the issue in-house.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-15946) Make Current button doesn't work when 2 versions are being compared on Ambari UI
Andrii Tkach created AMBARI-15946:
-
Summary: Make Current button doesn't work when 2 versions are
being compared on Ambari UI
Key: AMBARI-15946
URL: https://issues.apache.org/jira/browse/AMBARI-15946
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.2.1.1
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Fix For: 2.4.0
*PROBLEM:*
>From ambari UI, we can hover mouse over the previous versions of any configs
>and we can an option to make it current. This works fine.
We also have an feature to compare the current and previous versions. When we
do this we get a green button *"Make V6 Current"*
(V6 is in my cluster. It can be any version).
If we click on this we get *"Created from service config version {0}"* pop up
and again a Make current button.
Click on it and everything seems ok. But the problem is the previous version is
NOT made current.
This works fine on Safari and firefox but *it does NOT work on chrome*.
*Attachments:*
1. [^pics (1).docx] - screenshots.
*BUSINESS IMPACT:* This caused us lot of issue as we all thought previous
configs had been reinstated but it wasn't and our debugging took a complete
detour.
*Go Live Date -* N/A
*STEPS TO REPRODUCE:*
1. Hover mouse on any previous version and click "compare".
2. Click "Make Current V6" (Make current for previous version).
3. Make current confirmation pop-up shows version {0} instead of the actual
version number.
4. Click "Make Current" and restart all services marked for "restart".
*EXPECTED RESULT:* The version I choose to make current should be applied.
*ACTUAL RESULT:* Previous version is not made current.
*SUPPORT ANALYSIS:* Reproduced the issue in-house.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15946) Make Current button doesn't work when 2 versions are being compared on Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-15946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-15946:
--
Status: Patch Available (was: Open)
> Make Current button doesn't work when 2 versions are being compared on Ambari
> UI
>
>
> Key: AMBARI-15946
> URL: https://issues.apache.org/jira/browse/AMBARI-15946
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.1.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15946.patch, pics (1).docx
>
>
> *PROBLEM:*
> From ambari UI, we can hover mouse over the previous versions of any configs
> and we can an option to make it current. This works fine.
> We also have an feature to compare the current and previous versions. When we
> do this we get a green button *"Make V6 Current"*
> (V6 is in my cluster. It can be any version).
> If we click on this we get *"Created from service config version {0}"* pop up
> and again a Make current button.
> Click on it and everything seems ok. But the problem is the previous version
> is NOT made current.
> This works fine on Safari and firefox but *it does NOT work on chrome*.
> *Attachments:*
>
> 1. [^pics (1).docx] - screenshots.
> *BUSINESS IMPACT:* This caused us lot of issue as we all thought previous
> configs had been reinstated but it wasn't and our debugging took a complete
> detour.
> *Go Live Date -* N/A
> *STEPS TO REPRODUCE:*
> 1. Hover mouse on any previous version and click "compare".
> 2. Click "Make Current V6" (Make current for previous version).
> 3. Make current confirmation pop-up shows version {0} instead of the actual
> version number.
> 4. Click "Make Current" and restart all services marked for "restart".
> *EXPECTED RESULT:* The version I choose to make current should be applied.
> *ACTUAL RESULT:* Previous version is not made current.
> *SUPPORT ANALYSIS:* Reproduced the issue in-house.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15946) Make Current button doesn't work when 2 versions are being compared on Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-15946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-15946:
--
Attachment: AMBARI-15946.patch
> Make Current button doesn't work when 2 versions are being compared on Ambari
> UI
>
>
> Key: AMBARI-15946
> URL: https://issues.apache.org/jira/browse/AMBARI-15946
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.1.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15946.patch, pics (1).docx
>
>
> *PROBLEM:*
> From ambari UI, we can hover mouse over the previous versions of any configs
> and we can an option to make it current. This works fine.
> We also have an feature to compare the current and previous versions. When we
> do this we get a green button *"Make V6 Current"*
> (V6 is in my cluster. It can be any version).
> If we click on this we get *"Created from service config version {0}"* pop up
> and again a Make current button.
> Click on it and everything seems ok. But the problem is the previous version
> is NOT made current.
> This works fine on Safari and firefox but *it does NOT work on chrome*.
> *Attachments:*
>
> 1. [^pics (1).docx] - screenshots.
> *BUSINESS IMPACT:* This caused us lot of issue as we all thought previous
> configs had been reinstated but it wasn't and our debugging took a complete
> detour.
> *Go Live Date -* N/A
> *STEPS TO REPRODUCE:*
> 1. Hover mouse on any previous version and click "compare".
> 2. Click "Make Current V6" (Make current for previous version).
> 3. Make current confirmation pop-up shows version {0} instead of the actual
> version number.
> 4. Click "Make Current" and restart all services marked for "restart".
> *EXPECTED RESULT:* The version I choose to make current should be applied.
> *ACTUAL RESULT:* Previous version is not made current.
> *SUPPORT ANALYSIS:* Reproduced the issue in-house.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15946) Make Current button doesn't work when 2 versions are being compared on Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-15946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246090#comment-15246090
]
Andrii Tkach commented on AMBARI-15946:
---
25681 tests complete (24 seconds)
154 tests pending
> Make Current button doesn't work when 2 versions are being compared on Ambari
> UI
>
>
> Key: AMBARI-15946
> URL: https://issues.apache.org/jira/browse/AMBARI-15946
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.1.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15946.patch, pics (1).docx
>
>
> *PROBLEM:*
> From ambari UI, we can hover mouse over the previous versions of any configs
> and we can an option to make it current. This works fine.
> We also have an feature to compare the current and previous versions. When we
> do this we get a green button *"Make V6 Current"*
> (V6 is in my cluster. It can be any version).
> If we click on this we get *"Created from service config version {0}"* pop up
> and again a Make current button.
> Click on it and everything seems ok. But the problem is the previous version
> is NOT made current.
> This works fine on Safari and firefox but *it does NOT work on chrome*.
> *Attachments:*
>
> 1. [^pics (1).docx] - screenshots.
> *BUSINESS IMPACT:* This caused us lot of issue as we all thought previous
> configs had been reinstated but it wasn't and our debugging took a complete
> detour.
> *Go Live Date -* N/A
> *STEPS TO REPRODUCE:*
> 1. Hover mouse on any previous version and click "compare".
> 2. Click "Make Current V6" (Make current for previous version).
> 3. Make current confirmation pop-up shows version {0} instead of the actual
> version number.
> 4. Click "Make Current" and restart all services marked for "restart".
> *EXPECTED RESULT:* The version I choose to make current should be applied.
> *ACTUAL RESULT:* Previous version is not made current.
> *SUPPORT ANALYSIS:* Reproduced the issue in-house.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15970) Ambari UI under replicated blocks do not match active NN reports
[ https://issues.apache.org/jira/browse/AMBARI-15970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15248144#comment-15248144 ] Andrii Tkach commented on AMBARI-15970: --- committed to trunk. > Ambari UI under replicated blocks do not match active NN reports > > > Key: AMBARI-15970 > URL: https://issues.apache.org/jira/browse/AMBARI-15970 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-15970.patch > > > PROBLEM: Ambari has a discrepancy when reporting under replicated blocks. It > sometimes pulls this number from the Standby Namenode. fsck report and Active > Namenode jmx report one number. Manual failover will correct this number. > ACTUAL RESULT: Ambari displays under replicated blocks from Standby Namenode > EXPECTED RESULT: Ambari should display under replicated blocks from Active > Namenode -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15970) Ambari UI under replicated blocks do not match active NN reports
[ https://issues.apache.org/jira/browse/AMBARI-15970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15970: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari UI under replicated blocks do not match active NN reports > > > Key: AMBARI-15970 > URL: https://issues.apache.org/jira/browse/AMBARI-15970 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-15970.patch > > > PROBLEM: Ambari has a discrepancy when reporting under replicated blocks. It > sometimes pulls this number from the Standby Namenode. fsck report and Active > Namenode jmx report one number. Manual failover will correct this number. > ACTUAL RESULT: Ambari displays under replicated blocks from Standby Namenode > EXPECTED RESULT: Ambari should display under replicated blocks from Active > Namenode -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15946) Make Current button doesn't work when 2 versions are being compared on Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-15946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247716#comment-15247716
]
Andrii Tkach commented on AMBARI-15946:
---
committed to trunk
> Make Current button doesn't work when 2 versions are being compared on Ambari
> UI
>
>
> Key: AMBARI-15946
> URL: https://issues.apache.org/jira/browse/AMBARI-15946
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.1.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15946.patch, pics (1).docx
>
>
> *PROBLEM:*
> From ambari UI, we can hover mouse over the previous versions of any configs
> and we can an option to make it current. This works fine.
> We also have an feature to compare the current and previous versions. When we
> do this we get a green button *"Make V6 Current"*
> (V6 is in my cluster. It can be any version).
> If we click on this we get *"Created from service config version {0}"* pop up
> and again a Make current button.
> Click on it and everything seems ok. But the problem is the previous version
> is NOT made current.
> This works fine on Safari and firefox but *it does NOT work on chrome*.
> *Attachments:*
>
> 1. [^pics (1).docx] - screenshots.
> *BUSINESS IMPACT:* This caused us lot of issue as we all thought previous
> configs had been reinstated but it wasn't and our debugging took a complete
> detour.
> *Go Live Date -* N/A
> *STEPS TO REPRODUCE:*
> 1. Hover mouse on any previous version and click "compare".
> 2. Click "Make Current V6" (Make current for previous version).
> 3. Make current confirmation pop-up shows version {0} instead of the actual
> version number.
> 4. Click "Make Current" and restart all services marked for "restart".
> *EXPECTED RESULT:* The version I choose to make current should be applied.
> *ACTUAL RESULT:* Previous version is not made current.
> *SUPPORT ANALYSIS:* Reproduced the issue in-house.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15946) Make Current button doesn't work when 2 versions are being compared on Ambari UI
[
https://issues.apache.org/jira/browse/AMBARI-15946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-15946:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Make Current button doesn't work when 2 versions are being compared on Ambari
> UI
>
>
> Key: AMBARI-15946
> URL: https://issues.apache.org/jira/browse/AMBARI-15946
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.2.1.1
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.4.0
>
> Attachments: AMBARI-15946.patch, pics (1).docx
>
>
> *PROBLEM:*
> From ambari UI, we can hover mouse over the previous versions of any configs
> and we can an option to make it current. This works fine.
> We also have an feature to compare the current and previous versions. When we
> do this we get a green button *"Make V6 Current"*
> (V6 is in my cluster. It can be any version).
> If we click on this we get *"Created from service config version {0}"* pop up
> and again a Make current button.
> Click on it and everything seems ok. But the problem is the previous version
> is NOT made current.
> This works fine on Safari and firefox but *it does NOT work on chrome*.
> *Attachments:*
>
> 1. [^pics (1).docx] - screenshots.
> *BUSINESS IMPACT:* This caused us lot of issue as we all thought previous
> configs had been reinstated but it wasn't and our debugging took a complete
> detour.
> *Go Live Date -* N/A
> *STEPS TO REPRODUCE:*
> 1. Hover mouse on any previous version and click "compare".
> 2. Click "Make Current V6" (Make current for previous version).
> 3. Make current confirmation pop-up shows version {0} instead of the actual
> version number.
> 4. Click "Make Current" and restart all services marked for "restart".
> *EXPECTED RESULT:* The version I choose to make current should be applied.
> *ACTUAL RESULT:* Previous version is not made current.
> *SUPPORT ANALYSIS:* Reproduced the issue in-house.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15920) Save creds checkbox is enabled, even though ambari is not config'd to save
[ https://issues.apache.org/jira/browse/AMBARI-15920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15245415#comment-15245415 ] Andrii Tkach commented on AMBARI-15920: --- committed to trunk > Save creds checkbox is enabled, even though ambari is not config'd to save > -- > > Key: AMBARI-15920 > URL: https://issues.apache.org/jira/browse/AMBARI-15920 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15920.patch, checkbox-active.tiff > > > See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15920) Save creds checkbox is enabled, even though ambari is not config'd to save
[ https://issues.apache.org/jira/browse/AMBARI-15920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15920: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Save creds checkbox is enabled, even though ambari is not config'd to save > -- > > Key: AMBARI-15920 > URL: https://issues.apache.org/jira/browse/AMBARI-15920 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15920.patch, checkbox-active.tiff > > > See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15910) Read-only user is getting extra perms
[ https://issues.apache.org/jira/browse/AMBARI-15910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15242732#comment-15242732 ] Andrii Tkach commented on AMBARI-15910: --- +1 for the patch > Read-only user is getting extra perms > - > > Key: AMBARI-15910 > URL: https://issues.apache.org/jira/browse/AMBARI-15910 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15910.patch, Screen Shot 2016-04-04 at 8.27.21 AM > (2).png, Screen Shot 2016-04-04 at 8.27.52 AM (2).png > > > 1) Created read-only user, and they have option to Make Current. > 2) Getting option to Set Rack > See attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15909) Alert help_url is not visible on the dash board
[
https://issues.apache.org/jira/browse/AMBARI-15909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15242731#comment-15242731
]
Andrii Tkach commented on AMBARI-15909:
---
+1 for the patch
> Alert help_url is not visible on the dash board
> ---
>
> Key: AMBARI-15909
> URL: https://issues.apache.org/jira/browse/AMBARI-15909
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15909.patch, Screen Shot 2016-04-14 at 5.34.19
> PM.png
>
>
> See the attached screen-shot !Screen Shot 2016-04-14 at 5.34.19
> PM.png|thumbnail!
> The help_url field is in the API.
> {code}
> {
> "href" :
> "http://c6401.ambari.apache.org:8080/api/v1/clusters/c1/alert_definitions/53;,
> "AlertDefinition" : {
> "cluster_name" : "c1",
> "component_name" : "AMBARI_SERVER",
> "description" : "This alert is triggered if the server has lost contact
> with an agent.",
> "enabled" : true,
> "help_url" :
> "https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Alerts#AmbariAlerts-ambari_agent_heartbeat;,
> "id" : 53,
> "ignore_host" : false,
> "interval" : 2,
> "label" : "Ambari Agent Heartbeat",
> "name" : "ambari_server_agent_heartbeat",
> "repeat_tolerance" : 1,
> "repeat_tolerance_enabled" : false,
> "scope" : "HOST",
> "service_name" : "AMBARI",
> "source" : {
> "class" : "org.apache.ambari.server.alerts.AgentHeartbeatAlertRunnable",
> "type" : "SERVER"
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-16012) JS error logged in dev console on signing in to ambari
[ https://issues.apache.org/jira/browse/AMBARI-16012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251948#comment-15251948 ] Andrii Tkach commented on AMBARI-16012: --- +1 for the patch > JS error logged in dev console on signing in to ambari > -- > > Key: AMBARI-16012 > URL: https://issues.apache.org/jira/browse/AMBARI-16012 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Oleg Nechiporenko >Assignee: Oleg Nechiporenko > Fix For: 2.4.0 > > Attachments: AMBARI-16012.patch, Screen Shot 2016-04-20 at 11.16.41 > AM.png, Screen Shot 2016-04-20 at 11.16.52 AM.png > > > *STR:* > # Deploy a cluster with HDFS and YARN > # Log off from ambari > # Refresh browser > # Log in to Ambari > JS error as shown in attachment is generated. > This issue happens intermittently with the stated STR as this seems to be > timing issue. It seems that multiple quick links widgets on dashboard page > are calling > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L223] > and this generates error at > [link|https://github.com/apache/ambari/blob/trunk/ambari-web/app/views/common/quick_view_link_view.js#L569] > I haven't verified but this issue might affect http/https formation in quick > link structure of dashboard widget. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15970) Ambari UI under replicated blocks do not match active NN reports
[ https://issues.apache.org/jira/browse/AMBARI-15970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15970: -- Description: PROBLEM: Ambari has a discrepancy when reporting under replicated blocks. It sometimes pulls this number from the Standby Namenode. fsck report and Active Namenode jmx report one number. Manual failover will correct this number. ACTUAL RESULT: Ambari displays under replicated blocks from Standby Namenode EXPECTED RESULT: Ambari should display under replicated blocks from Active Namenode was: PROBLEM: Ambari has a discrepancy when reporting under replicated blocks. It sometimes pulls this number from the Standby Namenode. fsck report and Active Namenode jmx report one number. Manual failover will correct this number. EXPECTED RESULT: Ambari displays under replicated blocks from Standby Namenode ACTUAL RESULT: Ambari should display under replicated blocks from Active Namenode > Ambari UI under replicated blocks do not match active NN reports > > > Key: AMBARI-15970 > URL: https://issues.apache.org/jira/browse/AMBARI-15970 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-15970.patch > > > PROBLEM: Ambari has a discrepancy when reporting under replicated blocks. It > sometimes pulls this number from the Standby Namenode. fsck report and Active > Namenode jmx report one number. Manual failover will correct this number. > ACTUAL RESULT: Ambari displays under replicated blocks from Standby Namenode > EXPECTED RESULT: Ambari should display under replicated blocks from Active > Namenode -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15970) Ambari UI under replicated blocks do not match active NN reports
Andrii Tkach created AMBARI-15970: - Summary: Ambari UI under replicated blocks do not match active NN reports Key: AMBARI-15970 URL: https://issues.apache.org/jira/browse/AMBARI-15970 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.2.1 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.4.0 PROBLEM: Ambari has a discrepancy when reporting under replicated blocks. It sometimes pulls this number from the Standby Namenode. fsck report and Active Namenode jmx report one number. Manual failover will correct this number. EXPECTED RESULT: Ambari displays under replicated blocks from Standby Namenode ACTUAL RESULT: Ambari should display under replicated blocks from Active Namenode -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15970) Ambari UI under replicated blocks do not match active NN reports
[ https://issues.apache.org/jira/browse/AMBARI-15970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247622#comment-15247622 ] Andrii Tkach commented on AMBARI-15970: --- 25679 tests complete (23 seconds) 154 tests pending > Ambari UI under replicated blocks do not match active NN reports > > > Key: AMBARI-15970 > URL: https://issues.apache.org/jira/browse/AMBARI-15970 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-15970.patch > > > PROBLEM: Ambari has a discrepancy when reporting under replicated blocks. It > sometimes pulls this number from the Standby Namenode. fsck report and Active > Namenode jmx report one number. Manual failover will correct this number. > EXPECTED RESULT: Ambari displays under replicated blocks from Standby Namenode > ACTUAL RESULT: Ambari should display under replicated blocks from Active > Namenode -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15970) Ambari UI under replicated blocks do not match active NN reports
[ https://issues.apache.org/jira/browse/AMBARI-15970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15970: -- Status: Patch Available (was: Open) > Ambari UI under replicated blocks do not match active NN reports > > > Key: AMBARI-15970 > URL: https://issues.apache.org/jira/browse/AMBARI-15970 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-15970.patch > > > PROBLEM: Ambari has a discrepancy when reporting under replicated blocks. It > sometimes pulls this number from the Standby Namenode. fsck report and Active > Namenode jmx report one number. Manual failover will correct this number. > EXPECTED RESULT: Ambari displays under replicated blocks from Standby Namenode > ACTUAL RESULT: Ambari should display under replicated blocks from Active > Namenode -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15958) Can not save roles assigned to users and groups on Manage Ambari -> Roles -> Block view
[ https://issues.apache.org/jira/browse/AMBARI-15958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15958: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Can not save roles assigned to users and groups on Manage Ambari -> Roles -> > Block view > --- > > Key: AMBARI-15958 > URL: https://issues.apache.org/jira/browse/AMBARI-15958 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Keta Patel >Assignee: Keta Patel > Fix For: 2.4.0 > > Attachments: AMBARI-15958.patch, img1.tiff, img2.tiff, img3.tiff, > img4.tiff > > > ISSUE: > Steps to reproduce: > 1. Go to Manage Ambari -> Roles (Block View) > 2. assign some role to some users or groups by typing their name in the > respective Roles' box. (img1.tiff, img2.tiff) > 3. Click on the Save button (Tick mark button) (img2.tiff) > 4. We can see the names of the users/groups in the Roles' box. (img3.tiff) > 5. Refresh the page, the names are no longer present in those boxes. > (img4.tiff) > The Save button must save the roles for the users/groups present in the > Roles' box. > CAUSE: > The controller handling the Block view is not able to call the > "$scope.save()" function whenever any Roles' box is edited. This is because > of an error in the name of the variable "isDataLoaded" used in condition of > the if-clause. > (The associated JIRA is AMBARI-15802) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15958) Can not save roles assigned to users and groups on Manage Ambari -> Roles -> Block view
[ https://issues.apache.org/jira/browse/AMBARI-15958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251609#comment-15251609 ] Andrii Tkach commented on AMBARI-15958: --- committed to trunk > Can not save roles assigned to users and groups on Manage Ambari -> Roles -> > Block view > --- > > Key: AMBARI-15958 > URL: https://issues.apache.org/jira/browse/AMBARI-15958 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Keta Patel >Assignee: Keta Patel > Fix For: 2.4.0 > > Attachments: AMBARI-15958.patch, img1.tiff, img2.tiff, img3.tiff, > img4.tiff > > > ISSUE: > Steps to reproduce: > 1. Go to Manage Ambari -> Roles (Block View) > 2. assign some role to some users or groups by typing their name in the > respective Roles' box. (img1.tiff, img2.tiff) > 3. Click on the Save button (Tick mark button) (img2.tiff) > 4. We can see the names of the users/groups in the Roles' box. (img3.tiff) > 5. Refresh the page, the names are no longer present in those boxes. > (img4.tiff) > The Save button must save the roles for the users/groups present in the > Roles' box. > CAUSE: > The controller handling the Block view is not able to call the > "$scope.save()" function whenever any Roles' box is edited. This is because > of an error in the name of the variable "isDataLoaded" used in condition of > the if-clause. > (The associated JIRA is AMBARI-15802) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15958) Can not save roles assigned to users and groups on Manage Ambari -> Roles -> Block view
[ https://issues.apache.org/jira/browse/AMBARI-15958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15958: -- Fix Version/s: (was: trunk) 2.4.0 > Can not save roles assigned to users and groups on Manage Ambari -> Roles -> > Block view > --- > > Key: AMBARI-15958 > URL: https://issues.apache.org/jira/browse/AMBARI-15958 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 2.4.0 >Reporter: Keta Patel >Assignee: Keta Patel > Fix For: 2.4.0 > > Attachments: AMBARI-15958.patch, img1.tiff, img2.tiff, img3.tiff, > img4.tiff > > > ISSUE: > Steps to reproduce: > 1. Go to Manage Ambari -> Roles (Block View) > 2. assign some role to some users or groups by typing their name in the > respective Roles' box. (img1.tiff, img2.tiff) > 3. Click on the Save button (Tick mark button) (img2.tiff) > 4. We can see the names of the users/groups in the Roles' box. (img3.tiff) > 5. Refresh the page, the names are no longer present in those boxes. > (img4.tiff) > The Save button must save the roles for the users/groups present in the > Roles' box. > CAUSE: > The controller handling the Block view is not able to call the > "$scope.save()" function whenever any Roles' box is edited. This is because > of an error in the name of the variable "isDataLoaded" used in condition of > the if-clause. > (The associated JIRA is AMBARI-15802) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15979) Provide UI validation for widget_name and description fields in Create/Edit Widget pop-up.
[ https://issues.apache.org/jira/browse/AMBARI-15979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-15979: -- Fix Version/s: 2.4.0 > Provide UI validation for widget_name and description fields in Create/Edit > Widget pop-up. > -- > > Key: AMBARI-15979 > URL: https://issues.apache.org/jira/browse/AMBARI-15979 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Keta Patel >Assignee: Keta Patel > Fix For: 2.4.0 > > Attachments: AMBARI-15979-April-20.patch, > AMBARI-15979-April-25.patch, AMBARI-15979-April-26-updated.patch, > AMBARI-15979-April-26.patch, AMBARI-15979-inlineError.patch, > AMBARI-15979-topError.patch, AMBARI-15979.patch, > create_widget_button_location.tiff, create_widget_step1.tiff, > create_widget_step2.tiff, create_widget_step3.tiff, > fixed_ErrorOnTop_character_validation_for_description.tiff, > fixed_ErrorOnTop_character_validation_for_name.tiff, > fixed_ErrorOnTop_length_validation_for_description.tiff, > fixed_ErrorOnTop_length_validation_for_name.tiff, > fixed_InlineError_character_validation_for_description.tiff, > fixed_InlineError_character_validation_for_name.tiff, > fixed_InlineError_length_validation_for_description.tiff, > fixed_InlineError_length_validation_for_name.tiff, > fixed_characters_allowed_for_description.tiff, > fixed_characters_allowed_for_name.tiff, > original_characters_allowed_for_name_and_description.tiff, > original_length_validation_for_description.tiff, > original_length_validation_for_name.tiff > > > The UI validation at present checks only the length of the user input for > widget_name and description fields. All characters are allowed to be stored > in the database through them. A more strict UI validation that limits the > type of characters entered for these fields will provide a good first line of > defense. > Steps to reproduce: > 1. Make sure you have Ambari Metrics service installed on your cluster. > 2. On the Dashboard, select any service that makes use of Ambari Metrics, say > HDFS. > 3. In the "Metrics" section, click the "Actions" button in the top-right > corner, and select "Create a new widget" option from the drop-down. > (attachment: create_widget_button_location.tiff) > 4. Create widget pop-up is displayed. > 5. On Step-1, select any type for the widget and click "Next". (attachment: > create_widget_step1.tiff) > 6. On Step-2, select any valid metrics parameter and click "Next". > (attachment: create_widget_step2.tiff) > 7. On Step-3, for widget_name and description fields, you can enter any > character. No validation is present to check the contents. The only > validation present checks the length of the input text. > (attachments: > create_widget_step3.tiff, > original_characters_allowed_for_name_and_description.tiff, > original_length_validation_for_name.tiff, > original_length_validation_for_description.tiff ) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15979) Provide UI validation for widget_name and description fields in Create/Edit Widget pop-up.
[ https://issues.apache.org/jira/browse/AMBARI-15979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15261788#comment-15261788 ] Andrii Tkach commented on AMBARI-15979: --- committed to trunk > Provide UI validation for widget_name and description fields in Create/Edit > Widget pop-up. > -- > > Key: AMBARI-15979 > URL: https://issues.apache.org/jira/browse/AMBARI-15979 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: trunk >Reporter: Keta Patel >Assignee: Keta Patel > Fix For: 2.4.0 > > Attachments: AMBARI-15979-April-20.patch, > AMBARI-15979-April-25.patch, AMBARI-15979-April-26-updated.patch, > AMBARI-15979-April-26.patch, AMBARI-15979-inlineError.patch, > AMBARI-15979-topError.patch, AMBARI-15979.patch, > create_widget_button_location.tiff, create_widget_step1.tiff, > create_widget_step2.tiff, create_widget_step3.tiff, > fixed_ErrorOnTop_character_validation_for_description.tiff, > fixed_ErrorOnTop_character_validation_for_name.tiff, > fixed_ErrorOnTop_length_validation_for_description.tiff, > fixed_ErrorOnTop_length_validation_for_name.tiff, > fixed_InlineError_character_validation_for_description.tiff, > fixed_InlineError_character_validation_for_name.tiff, > fixed_InlineError_length_validation_for_description.tiff, > fixed_InlineError_length_validation_for_name.tiff, > fixed_characters_allowed_for_description.tiff, > fixed_characters_allowed_for_name.tiff, > original_characters_allowed_for_name_and_description.tiff, > original_length_validation_for_description.tiff, > original_length_validation_for_name.tiff > > > The UI validation at present checks only the length of the user input for > widget_name and description fields. All characters are allowed to be stored > in the database through them. A more strict UI validation that limits the > type of characters entered for these fields will provide a good first line of > defense. > Steps to reproduce: > 1. Make sure you have Ambari Metrics service installed on your cluster. > 2. On the Dashboard, select any service that makes use of Ambari Metrics, say > HDFS. > 3. In the "Metrics" section, click the "Actions" button in the top-right > corner, and select "Create a new widget" option from the drop-down. > (attachment: create_widget_button_location.tiff) > 4. Create widget pop-up is displayed. > 5. On Step-1, select any type for the widget and click "Next". (attachment: > create_widget_step1.tiff) > 6. On Step-2, select any valid metrics parameter and click "Next". > (attachment: create_widget_step2.tiff) > 7. On Step-3, for widget_name and description fields, you can enter any > character. No validation is present to check the contents. The only > validation present checks the length of the input text. > (attachments: > create_widget_step3.tiff, > original_characters_allowed_for_name_and_description.tiff, > original_length_validation_for_name.tiff, > original_length_validation_for_description.tiff ) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16865) While deleting a service from UI, the confirmation popup does not appear sometimes
[ https://issues.apache.org/jira/browse/AMBARI-16865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16865: -- Attachment: test_video_part17-6.flv > While deleting a service from UI, the confirmation popup does not appear > sometimes > -- > > Key: AMBARI-16865 > URL: https://issues.apache.org/jira/browse/AMBARI-16865 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: test_video_part17-6.flv > > > This was observed in many tests when they were deleting a service from UI. > The final confirmation window that says service was deletes successfully does > not appear sometimes. The wait period is 20 seconds in tests but sometimes it > just doesn't appear. > But service is deleted successfully. > In the video attached, > the test enables ranger plugins, then restarts services with stale configs > (not an important to reproduce) > and then tries to delete ranger from UI(at 1:25). > Ranger is deleted successfully but the pop up did not appear, and hence the > page did not refresh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16865) While deleting a service from UI, the confirmation popup does not appear sometimes
Andrii Tkach created AMBARI-16865: - Summary: While deleting a service from UI, the confirmation popup does not appear sometimes Key: AMBARI-16865 URL: https://issues.apache.org/jira/browse/AMBARI-16865 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.4.0 This was observed in many tests when they were deleting a service from UI. The final confirmation window that says service was deletes successfully does not appear sometimes. The wait period is 20 seconds in tests but sometimes it just doesn't appear. But service is deleted successfully. In the video attached, the test enables ranger plugins, then restarts services with stale configs (not an important to reproduce) and then tries to delete ranger from UI(at 1:25). Ranger is deleted successfully but the pop up did not appear, and hence the page did not refresh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16865) While deleting a service from UI, the confirmation popup does not appear sometimes
[ https://issues.apache.org/jira/browse/AMBARI-16865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299764#comment-15299764 ] Andrii Tkach commented on AMBARI-16865: --- committed to trunk and branch-2.4 > While deleting a service from UI, the confirmation popup does not appear > sometimes > -- > > Key: AMBARI-16865 > URL: https://issues.apache.org/jira/browse/AMBARI-16865 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16865.patch, test_video_part17-6.flv > > > This was observed in many tests when they were deleting a service from UI. > The final confirmation window that says service was deletes successfully does > not appear sometimes. The wait period is 20 seconds in tests but sometimes it > just doesn't appear. > But service is deleted successfully. > In the video attached, > the test enables ranger plugins, then restarts services with stale configs > (not an important to reproduce) > and then tries to delete ranger from UI(at 1:25). > Ranger is deleted successfully but the pop up did not appear, and hence the > page did not refresh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16865) While deleting a service from UI, the confirmation popup does not appear sometimes
[ https://issues.apache.org/jira/browse/AMBARI-16865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-16865: -- Resolution: Fixed Status: Resolved (was: Patch Available) > While deleting a service from UI, the confirmation popup does not appear > sometimes > -- > > Key: AMBARI-16865 > URL: https://issues.apache.org/jira/browse/AMBARI-16865 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16865.patch, test_video_part17-6.flv > > > This was observed in many tests when they were deleting a service from UI. > The final confirmation window that says service was deletes successfully does > not appear sometimes. The wait period is 20 seconds in tests but sometimes it > just doesn't appear. > But service is deleted successfully. > In the video attached, > the test enables ranger plugins, then restarts services with stale configs > (not an important to reproduce) > and then tries to delete ranger from UI(at 1:25). > Ranger is deleted successfully but the pop up did not appear, and hence the > page did not refresh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16865) While deleting a service from UI, the confirmation popup does not appear sometimes
[ https://issues.apache.org/jira/browse/AMBARI-16865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15299724#comment-15299724 ] Andrii Tkach commented on AMBARI-16865: --- 27840 tests complete (27 seconds) 154 tests pending > While deleting a service from UI, the confirmation popup does not appear > sometimes > -- > > Key: AMBARI-16865 > URL: https://issues.apache.org/jira/browse/AMBARI-16865 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16865.patch, test_video_part17-6.flv > > > This was observed in many tests when they were deleting a service from UI. > The final confirmation window that says service was deletes successfully does > not appear sometimes. The wait period is 20 seconds in tests but sometimes it > just doesn't appear. > But service is deleted successfully. > In the video attached, > the test enables ranger plugins, then restarts services with stale configs > (not an important to reproduce) > and then tries to delete ranger from UI(at 1:25). > Ranger is deleted successfully but the pop up did not appear, and hence the > page did not refresh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
