[jira] [Resolved] (AMBARI-25396) cross-site scripting vulnerability on Ambari hosts
[ https://issues.apache.org/jira/browse/AMBARI-25396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-25396. -- Resolution: Fixed > cross-site scripting vulnerability on Ambari hosts > -- > > Key: AMBARI-25396 > URL: https://issues.apache.org/jira/browse/AMBARI-25396 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Fix xss vulnerability in ssh-key name and value in wizards. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25396) cross-site scripting vulnerability on Ambari hosts
Aleksandr Kovalenko created AMBARI-25396: Summary: cross-site scripting vulnerability on Ambari hosts Key: AMBARI-25396 URL: https://issues.apache.org/jira/browse/AMBARI-25396 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.4 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.5 Fix xss vulnerability in ssh-key name and value in wizards. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25105) Cover views of the JournalNode wizard with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-25105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-25105. -- Resolution: Fixed > Cover views of the JournalNode wizard with unit tests > - > > Key: AMBARI-25105 > URL: https://issues.apache.org/jira/browse/AMBARI-25105 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Following files to cover: > * app/views/main/admin/highAvailability/journalNode/progress_view.js > * app/views/main/admin/highAvailability/journalNode/step3_view.js > * app/views/main/admin/highAvailability/journalNode/step5_view.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25145) Cover controllers of High Availability wizard with unit tests
Aleksandr Kovalenko created AMBARI-25145: Summary: Cover controllers of High Availability wizard with unit tests Key: AMBARI-25145 URL: https://issues.apache.org/jira/browse/AMBARI-25145 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.8.0 Following files to cover: * app/controllers/main/admin/highAvailability/hawq/removeStandby/step3_controller.js * app/controllers/main/admin/highAvailability/hawq/removeStandby/wizard_controller.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25144) Cover config history controller with unit tests
Aleksandr Kovalenko created AMBARI-25144: Summary: Cover config history controller with unit tests Key: AMBARI-25144 URL: https://issues.apache.org/jira/browse/AMBARI-25144 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.8.0 Following files to cover: * app/controllers/main/dashboard/config_history_controller.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25135) Cover service mixin with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-25135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-25135. -- Resolution: Fixed > Cover service mixin with unit tests > --- > > Key: AMBARI-25135 > URL: https://issues.apache.org/jira/browse/AMBARI-25135 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Following files to cover: > * app/mixins/main/service/groups_mapping.js > * app/mixins/main/service/themes_mapping.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-25134) Cover controller of widget edit with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-25134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-25134. -- Resolution: Fixed > Cover controller of widget edit with unit tests > --- > > Key: AMBARI-25134 > URL: https://issues.apache.org/jira/browse/AMBARI-25134 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Following files to cover: > * app/controllers/main/service/widgets/edit_controller.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25135) Cover service mixin with unit tests
Aleksandr Kovalenko created AMBARI-25135: Summary: Cover service mixin with unit tests Key: AMBARI-25135 URL: https://issues.apache.org/jira/browse/AMBARI-25135 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.8.0 Following files to cover: * app/mixins/main/service/groups_mapping.js * app/mixins/main/service/themes_mapping.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25134) Cover controller of widget edit with unit tests
Aleksandr Kovalenko created AMBARI-25134: Summary: Cover controller of widget edit with unit tests Key: AMBARI-25134 URL: https://issues.apache.org/jira/browse/AMBARI-25134 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.8.0 Following files to cover: * app/controllers/main/service/widgets/edit_controller.js -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24704) Problems with accounts page when sysprep_skip_create_users_and_groups is absent
[ https://issues.apache.org/jira/browse/AMBARI-24704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24704: - Resolution: Fixed Status: Resolved (was: Patch Available) > Problems with accounts page when sysprep_skip_create_users_and_groups is > absent > --- > > Key: AMBARI-24704 > URL: https://issues.apache.org/jira/browse/AMBARI-24704 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.8.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When sysprep_skip_create_users_and_groups property is absent accounts page > can not load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24824) Make cluster name inputs validation in Ambari UI consistent
[ https://issues.apache.org/jira/browse/AMBARI-24824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24824. -- Resolution: Fixed > Make cluster name inputs validation in Ambari UI consistent > --- > > Key: AMBARI-24824 > URL: https://issues.apache.org/jira/browse/AMBARI-24824 > Project: Ambari > Issue Type: Bug > Components: ambari-admin, ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.8.0 > > Time Spent: 40m > Remaining Estimate: 0h > > # User has ability to rename cluster on 'Cluster Information' page of Ambari > Admin. Cluster name input isn't being validated there. E.g., it's possible to > set the new name containing special characters like slash which would break > API. > # It's possible to proceed by clicking 'Save' button in rename cluster > scenario even if it's disabled. > # Cluster name validation is inconsistent in different possible scenarios of > its setting. In scope of this task validation on step0 of Ambari installer > should be changed. > Validation rules on Ui should be consistent with BE rules. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24824) Make cluster name inputs validation in Ambari UI consistent
Aleksandr Kovalenko created AMBARI-24824: Summary: Make cluster name inputs validation in Ambari UI consistent Key: AMBARI-24824 URL: https://issues.apache.org/jira/browse/AMBARI-24824 Project: Ambari Issue Type: Bug Components: ambari-admin, ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.8.0 # User has ability to rename cluster on 'Cluster Information' page of Ambari Admin. Cluster name input isn't being validated there. E.g., it's possible to set the new name containing special characters like slash which would break API. # It's possible to proceed by clicking 'Save' button in rename cluster scenario even if it's disabled. # Cluster name validation is inconsistent in different possible scenarios of its setting. In scope of this task validation on step0 of Ambari installer should be changed. Validation rules on Ui should be consistent with BE rules. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24787) Cover with unit tests wizard step7 views
[ https://issues.apache.org/jira/browse/AMBARI-24787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24787. -- Resolution: Fixed > Cover with unit tests wizard step7 views > > > Key: AMBARI-24787 > URL: https://issues.apache.org/jira/browse/AMBARI-24787 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24787) Cover with unit tests wizard step7 views
Aleksandr Kovalenko created AMBARI-24787: Summary: Cover with unit tests wizard step7 views Key: AMBARI-24787 URL: https://issues.apache.org/jira/browse/AMBARI-24787 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24704) Problems with accounts page when sysprep_skip_create_users_and_groups is absent
[ https://issues.apache.org/jira/browse/AMBARI-24704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24704: - Status: Patch Available (was: Open) > Problems with accounts page when sysprep_skip_create_users_and_groups is > absent > --- > > Key: AMBARI-24704 > URL: https://issues.apache.org/jira/browse/AMBARI-24704 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.8.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Fix For: 2.8.0 > > > When sysprep_skip_create_users_and_groups property is absent accounts page > can not load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24704) Problems with accounts page when sysprep_skip_create_users_and_groups is absent
Aleksandr Kovalenko created AMBARI-24704: Summary: Problems with accounts page when sysprep_skip_create_users_and_groups is absent Key: AMBARI-24704 URL: https://issues.apache.org/jira/browse/AMBARI-24704 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.8.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.8.0 When sysprep_skip_create_users_and_groups property is absent accounts page can not load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24676) Issues w.r.t Manage Journal Nodes (Particularly deletion) in HA enabled cluster.
[
https://issues.apache.org/jira/browse/AMBARI-24676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko resolved AMBARI-24676.
--
Resolution: Fixed
> Issues w.r.t Manage Journal Nodes (Particularly deletion) in HA enabled
> cluster.
>
>
> Key: AMBARI-24676
> URL: https://issues.apache.org/jira/browse/AMBARI-24676
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> # we have a cluster of 6 hosts (postfixes are 5, 6, 8, 9, 10 and 14)
> # this is a federated cluster with two namespaces: ns1 and ns2
> # Namenode HA is enabled; JNs are located on 5, 6, and 14
> # Added a new JN using the "Manage Journalnodes" wizard on host 8
> # Removed an existing JN using the "Manage Journalnodes" wizard from host 6
> # Relevant configurations after these steps:
> {noformat}
> dfs.namenode.shared.edits.dir=qjournal://ctr-e138-1518143905142-472105-01-14.host.site:8485;ctr-e138-1518143905142-472105-01-08.host.site:8485;ctr-e138-1518143905142-472105-01-05.host.site:8485/ns1,ns2
> dfs.namenode.shared.edits.dir.ns1=qjournal://ctr-e138-1518143905142-472105-01-05.host.site:8485;ctr-e138-1518143905142-472105-01-06.host.site:8485;ctr-e138-1518143905142-472105-01-14.host.site:8485/ns1
> dfs.namenode.shared.edits.dir.ns2=qjournal://ctr-e138-1518143905142-472105-01-05.host.site:8485;ctr-e138-1518143905142-472105-01-06.host.site:8485;ctr-e138-1518143905142-472105-01-14.host.site:8485/ns2
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24676) Issues w.r.t Manage Journal Nodes (Particularly deletion) in HA enabled cluster.
Aleksandr Kovalenko created AMBARI-24676:
Summary: Issues w.r.t Manage Journal Nodes (Particularly deletion)
in HA enabled cluster.
Key: AMBARI-24676
URL: https://issues.apache.org/jira/browse/AMBARI-24676
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.1
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Fix For: 2.8.0
# we have a cluster of 6 hosts (postfixes are 5, 6, 8, 9, 10 and 14)
# this is a federated cluster with two namespaces: ns1 and ns2
# Namenode HA is enabled; JNs are located on 5, 6, and 14
# Added a new JN using the "Manage Journalnodes" wizard on host 8
# Removed an existing JN using the "Manage Journalnodes" wizard from host 6
# Relevant configurations after these steps:
{noformat}
dfs.namenode.shared.edits.dir=qjournal://ctr-e138-1518143905142-472105-01-14.host.site:8485;ctr-e138-1518143905142-472105-01-08.host.site:8485;ctr-e138-1518143905142-472105-01-05.host.site:8485/ns1,ns2
dfs.namenode.shared.edits.dir.ns1=qjournal://ctr-e138-1518143905142-472105-01-05.host.site:8485;ctr-e138-1518143905142-472105-01-06.host.site:8485;ctr-e138-1518143905142-472105-01-14.host.site:8485/ns1
dfs.namenode.shared.edits.dir.ns2=qjournal://ctr-e138-1518143905142-472105-01-05.host.site:8485;ctr-e138-1518143905142-472105-01-06.host.site:8485;ctr-e138-1518143905142-472105-01-14.host.site:8485/ns2
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24554) UX issues with yarn containers widget
[ https://issues.apache.org/jira/browse/AMBARI-24554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24554. -- Resolution: Fixed > UX issues with yarn containers widget > -- > > Key: AMBARI-24554 > URL: https://issues.apache.org/jira/browse/AMBARI-24554 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > # The n/a content in yarn container widget seems to be bold as compared to > other widgets where it is faded out. > # no padding among three n/a makes it look a little unintuitive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24598) Broken markup for alert on Installer Step7
[ https://issues.apache.org/jira/browse/AMBARI-24598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24598. -- Resolution: Fixed > Broken markup for alert on Installer Step7 > -- > > Key: AMBARI-24598 > URL: https://issues.apache.org/jira/browse/AMBARI-24598 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Install Wizard -> Step 7 shows alert popup on the top of the page when user > creates config group and switches to it. Looks like it has broken markup or > styles. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24575) User get stuck between steps if API returns empty version_definitions array
[ https://issues.apache.org/jira/browse/AMBARI-24575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24575. -- Resolution: Fixed > User get stuck between steps if API returns empty version_definitions array > --- > > Key: AMBARI-24575 > URL: https://issues.apache.org/jira/browse/AMBARI-24575 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 40m > Remaining Estimate: 0h > > In Install Wizard when user goes to step1 API request to load version > definitions is sent. Sometimes this request returns empty array and UI is not > showing any error and just shows empty page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24597) Popup shown when Ambari started on a different port other than 8080
[
https://issues.apache.org/jira/browse/AMBARI-24597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko resolved AMBARI-24597.
--
Resolution: Fixed
> Popup shown when Ambari started on a different port other than 8080
> ---
>
> Key: AMBARI-24597
> URL: https://issues.apache.org/jira/browse/AMBARI-24597
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Change the Ambari server port by setting the following
> {code:title=ambari.properties}
> client.api.port=8000
> {code}
> Ab error popup is observed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24621) Badge with count of empty or invalid properties are missed ar the services panel during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-24621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24621. -- Resolution: Fixed > Badge with count of empty or invalid properties are missed ar the services > panel during cluster installation > > > Key: AMBARI-24621 > URL: https://issues.apache.org/jira/browse/AMBARI-24621 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > STR: > 1)Initiate cluster installation > 2)Navigate to customize all services page > 3)Navigate to service tab > 4)Clear some service required property > Expected > Count of errors near service name > Actual > Count of errors near service name is absent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24635) Web Client Chooses Wrong Version When Reverting Configs
Aleksandr Kovalenko created AMBARI-24635:
Summary: Web Client Chooses Wrong Version When Reverting Configs
Key: AMBARI-24635
URL: https://issues.apache.org/jira/browse/AMBARI-24635
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.2
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Fix For: 2.7.2
STR:
- Setup a simple cluster with ZK, HDFS, YARN, Hive, Pig
- Create at least 5 different configuration versions for Pig
- Load the Pig configuration page and select v4
- Now select V3 and then choose "Make Current"
At this point, the web client will populate a dialog that says {{Created from
service config version V4}} and indeed it restores v4, not v3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24336) Badge with count of empty or invalid properties are missed ar the services panel during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-24336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24336. -- Resolution: Fixed > Badge with count of empty or invalid properties are missed ar the services > panel during cluster installation > > > Key: AMBARI-24336 > URL: https://issues.apache.org/jira/browse/AMBARI-24336 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: Screen Shot 2018-07-03 at 11.21.08 AM.png, > photo_2018-07-03_18-52-37.jpg > > > STR: > 1)Initiate cluster installation > 2)Navigate to customize all services page > 3)Navigate to service tab > 4)Clear some service required property > Expected > Count of errors near service name > Actual > Count of errors near service name is absent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24628) Fix possible "Phishing by Navigating Browser Tabs" vulnerability
[
https://issues.apache.org/jira/browse/AMBARI-24628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko resolved AMBARI-24628.
--
Resolution: Fixed
> Fix possible "Phishing by Navigating Browser Tabs" vulnerability
>
>
> Key: AMBARI-24628
> URL: https://issues.apache.org/jira/browse/AMBARI-24628
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.6.2
>Reporter: amarnath reddy pappu
>Assignee: Aleksandr Kovalenko
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.2
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> According to details found at
> https://www.netsparker.com/web-vulnerability-scanner/vulnerabilities/phishing-by-navigating-browser-tabs/,
> it is possible to change the "window.opener.location" value in browser
> windows opened using normal anchor tags where the "target" attribute is
> specified as "_blank".
> This gives an attacker the ability to change the parent location and thus
> potentially allow for a phishing attack to invoked.
> To help this situation, it is suggested that the following attribute be set
> along with the "target" attribute:
> {noformat}
> rel="noopener noreferrer"
> {noformat}
> For example:
> {noformat}
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-24628) Fix possible "Phishing by Navigating Browser Tabs" vulnerability
[
https://issues.apache.org/jira/browse/AMBARI-24628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-24628:
-
Fix Version/s: 2.7.2
> Fix possible "Phishing by Navigating Browser Tabs" vulnerability
>
>
> Key: AMBARI-24628
> URL: https://issues.apache.org/jira/browse/AMBARI-24628
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.6.2
>Reporter: amarnath reddy pappu
>Assignee: Aleksandr Kovalenko
>Priority: Major
> Fix For: 2.7.2
>
>
> According to details found at
> https://www.netsparker.com/web-vulnerability-scanner/vulnerabilities/phishing-by-navigating-browser-tabs/,
> it is possible to change the "window.opener.location" value in browser
> windows opened using normal anchor tags where the "target" attribute is
> specified as "_blank".
> This gives an attacker the ability to change the parent location and thus
> potentially allow for a phishing attack to invoked.
> To help this situation, it is suggested that the following attribute be set
> along with the "target" attribute:
> {noformat}
> rel="noopener noreferrer"
> {noformat}
> For example:
> {noformat}
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-24628) Fix possible "Phishing by Navigating Browser Tabs" vulnerability
[
https://issues.apache.org/jira/browse/AMBARI-24628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko reassigned AMBARI-24628:
Assignee: Aleksandr Kovalenko
> Fix possible "Phishing by Navigating Browser Tabs" vulnerability
>
>
> Key: AMBARI-24628
> URL: https://issues.apache.org/jira/browse/AMBARI-24628
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk, 2.6.2
>Reporter: amarnath reddy pappu
>Assignee: Aleksandr Kovalenko
>Priority: Major
>
> According to details found at
> https://www.netsparker.com/web-vulnerability-scanner/vulnerabilities/phishing-by-navigating-browser-tabs/,
> it is possible to change the "window.opener.location" value in browser
> windows opened using normal anchor tags where the "target" attribute is
> specified as "_blank".
> This gives an attacker the ability to change the parent location and thus
> potentially allow for a phishing attack to invoked.
> To help this situation, it is suggested that the following attribute be set
> along with the "target" attribute:
> {noformat}
> rel="noopener noreferrer"
> {noformat}
> For example:
> {noformat}
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24621) Badge with count of empty or invalid properties are missed ar the services panel during cluster installation
Aleksandr Kovalenko created AMBARI-24621: Summary: Badge with count of empty or invalid properties are missed ar the services panel during cluster installation Key: AMBARI-24621 URL: https://issues.apache.org/jira/browse/AMBARI-24621 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 STR: 1)Initiate cluster installation 2)Navigate to customize all services page 3)Navigate to service tab 4)Clear some service required property Expected Count of errors near service name Actual Count of errors near service name is absent -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24586) User get stuck between steps if API returns empty version_definitions array
[ https://issues.apache.org/jira/browse/AMBARI-24586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24586. -- Resolution: Duplicate > User get stuck between steps if API returns empty version_definitions array > --- > > Key: AMBARI-24586 > URL: https://issues.apache.org/jira/browse/AMBARI-24586 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In Install Wizard when user goes to step1 API request to load version > definitions is sent. Sometimes this request returns empty array and UI is not > showing any error and just shows empty page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24598) Broken markup for alert on Installer Step7
Aleksandr Kovalenko created AMBARI-24598: Summary: Broken markup for alert on Installer Step7 Key: AMBARI-24598 URL: https://issues.apache.org/jira/browse/AMBARI-24598 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 Install Wizard -> Step 7 shows alert popup on the top of the page when user creates config group and switches to it. Looks like it has broken markup or styles. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24597) Popup shown when Ambari started on a different port other than 8080
Aleksandr Kovalenko created AMBARI-24597:
Summary: Popup shown when Ambari started on a different port other
than 8080
Key: AMBARI-24597
URL: https://issues.apache.org/jira/browse/AMBARI-24597
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.1
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Fix For: 2.7.2
Change the Ambari server port by setting the following
{code:title=ambari.properties}
client.api.port=8000
{code}
Ab error popup is observed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24586) User get stuck between steps if API returns empty version_definitions array
Aleksandr Kovalenko created AMBARI-24586: Summary: User get stuck between steps if API returns empty version_definitions array Key: AMBARI-24586 URL: https://issues.apache.org/jira/browse/AMBARI-24586 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 In Install Wizard when user goes to step1 API request to load version definitions is sent. Sometimes this request returns empty array and UI is not showing any error and just shows empty page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24575) User get stuck between steps if API returns empty version_definitions array
Aleksandr Kovalenko created AMBARI-24575: Summary: User get stuck between steps if API returns empty version_definitions array Key: AMBARI-24575 URL: https://issues.apache.org/jira/browse/AMBARI-24575 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 In Install Wizard when user goes to step1 API request to load version definitions is sent. Sometimes this request returns empty array and UI is not showing any error and just shows empty page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24554) UX issues with yarn containers widget
Aleksandr Kovalenko created AMBARI-24554: Summary: UX issues with yarn containers widget Key: AMBARI-24554 URL: https://issues.apache.org/jira/browse/AMBARI-24554 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 # The n/a content in yarn container widget seems to be bold as compared to other widgets where it is faded out. # no padding among three n/a makes it look a little unintuitive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24529) Add unit tests for centralized configs logic
[ https://issues.apache.org/jira/browse/AMBARI-24529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24529. -- Resolution: Fixed > Add unit tests for centralized configs logic > > > Key: AMBARI-24529 > URL: https://issues.apache.org/jira/browse/AMBARI-24529 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24529) Add unit tests for centralized configs logic
Aleksandr Kovalenko created AMBARI-24529: Summary: Add unit tests for centralized configs logic Key: AMBARI-24529 URL: https://issues.apache.org/jira/browse/AMBARI-24529 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24474) Data in Install Wizard is restored even after logout
[ https://issues.apache.org/jira/browse/AMBARI-24474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24474. -- Resolution: Fixed > Data in Install Wizard is restored even after logout > > > Key: AMBARI-24474 > URL: https://issues.apache.org/jira/browse/AMBARI-24474 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > If user in Install Wizard goes up to Review step then all his changes are > persisted to the server. So after every page refresh old data will be loaded > even if later user goes back and makes another changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24474) Data in Install Wizard is restored even after logout
Aleksandr Kovalenko created AMBARI-24474: Summary: Data in Install Wizard is restored even after logout Key: AMBARI-24474 URL: https://issues.apache.org/jira/browse/AMBARI-24474 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 If user in Install Wizard goes up to Review step then all his changes are persisted to the server. So after every page refresh old data will be loaded even if later user goes back and makes another changes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24442) HIVESERVER2 JDBC URL doesn't fit inside block
[ https://issues.apache.org/jira/browse/AMBARI-24442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24442. -- Resolution: Fixed > HIVESERVER2 JDBC URL doesn't fit inside block > -- > > Key: AMBARI-24442 > URL: https://issues.apache.org/jira/browse/AMBARI-24442 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > On Hive Service Summary page text doesn't fit inside the appropriate block if > HIVESERVER2 JDBC URL has much hosts in its value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24443) Slider type widget displays erroneously before first touch
[ https://issues.apache.org/jira/browse/AMBARI-24443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24443. -- Resolution: Fixed > Slider type widget displays erroneously before first touch > -- > > Key: AMBARI-24443 > URL: https://issues.apache.org/jira/browse/AMBARI-24443 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Under some circumstances slider type widget minimum and maximum values are > shown both on the left side one on the other, and the actual value pointer is > a bit off the point when the slider is. > STR: > 1. Go to the Hive/Configs > 2. Enable Interactive Query > 3. Click on Select on a the pop-up window > 4. Roll down to "Memory per Daemon" > 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24443) Slider type widget displays erroneously before first touch
[ https://issues.apache.org/jira/browse/AMBARI-24443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24443: - Description: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point when the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately was: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point whet the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately > Slider type widget displays erroneously before first touch > -- > > Key: AMBARI-24443 > URL: https://issues.apache.org/jira/browse/AMBARI-24443 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > > Under some circumstances slider type widget minimum and maximum values are > shown both on the left side one on the other, and the actual value pointer is > a bit off the point when the slider is. See attached video. > STR as seen on the attached video: > 1. Go to the Hive/Configs > 2. Enable Interactive Query > 3. Click on Select on a the pop-up window > 4. Roll down to "Memory per Daemon" > 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24443) Slider type widget displays erroneously before first touch
[ https://issues.apache.org/jira/browse/AMBARI-24443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24443: - Description: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point when the slider is. STR: 1. Go to the Hive/Configs 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately was: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point when the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately > Slider type widget displays erroneously before first touch > -- > > Key: AMBARI-24443 > URL: https://issues.apache.org/jira/browse/AMBARI-24443 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > > Under some circumstances slider type widget minimum and maximum values are > shown both on the left side one on the other, and the actual value pointer is > a bit off the point when the slider is. > STR: > 1. Go to the Hive/Configs > 2. Enable Interactive Query > 3. Click on Select on a the pop-up window > 4. Roll down to "Memory per Daemon" > 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24443) Slider type widget displays erroneously before first touch
[ https://issues.apache.org/jira/browse/AMBARI-24443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24443: - Description: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point whet the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately was: Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point whet the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs in the cluster http://104.196.74.255:8080/ 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately > Slider type widget displays erroneously before first touch > -- > > Key: AMBARI-24443 > URL: https://issues.apache.org/jira/browse/AMBARI-24443 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > > Under some circumstances slider type widget minimum and maximum values are > shown both on the left side one on the other, and the actual value pointer is > a bit off the point whet the slider is. See attached video. > STR as seen on the attached video: > 1. Go to the Hive/Configs > 2. Enable Interactive Query > 3. Click on Select on a the pop-up window > 4. Roll down to "Memory per Daemon" > 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24443) Slider type widget displays erroneously before first touch
Aleksandr Kovalenko created AMBARI-24443: Summary: Slider type widget displays erroneously before first touch Key: AMBARI-24443 URL: https://issues.apache.org/jira/browse/AMBARI-24443 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 Under some circumstances slider type widget minimum and maximum values are shown both on the left side one on the other, and the actual value pointer is a bit off the point whet the slider is. See attached video. STR as seen on the attached video: 1. Go to the Hive/Configs in the cluster http://104.196.74.255:8080/ 2. Enable Interactive Query 3. Click on Select on a the pop-up window 4. Roll down to "Memory per Daemon" 5. Touch the widget, it gets fixed immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24442) HIVESERVER2 JDBC URL doesn't fit inside block
Aleksandr Kovalenko created AMBARI-24442: Summary: HIVESERVER2 JDBC URL doesn't fit inside block Key: AMBARI-24442 URL: https://issues.apache.org/jira/browse/AMBARI-24442 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 On Hive Service Summary page text doesn't fit inside the appropriate block if HIVESERVER2 JDBC URL has much hosts in its value. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24405) Components in hosts page should be sorted by display name
[ https://issues.apache.org/jira/browse/AMBARI-24405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24405. -- Resolution: Fixed > Components in hosts page should be sorted by display name > - > > Key: AMBARI-24405 > URL: https://issues.apache.org/jira/browse/AMBARI-24405 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Components in hosts page seem to be sorted by component type (master, slave, > client etc) and within them they are not sorted by "display names", > "Timeline" comes before "History" > More importantly people when looking for a component don't look by their type > but instead look by their name. So all the components should be > alphabetically sorted by their display name irrespective of their type. Else > it becomes painful to look for a component of interest. (and finally have to > rely on browser's search capability) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24404) Button label appears incorrect during service deletion
[ https://issues.apache.org/jira/browse/AMBARI-24404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24404. -- Resolution: Fixed > Button label appears incorrect during service deletion > -- > > Key: AMBARI-24404 > URL: https://issues.apache.org/jira/browse/AMBARI-24404 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Try to delete Ranger service from a cluster, upon deletion stack advisor > recommends changes to configs. > This is fine, however the button at the bottom of the dialog says 'DELETE' > It should instead say something like 'Proceed' and once user clicks Proceed, > the delete pop-up should appear. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24405) Components in hosts page should be sorted by display name
Aleksandr Kovalenko created AMBARI-24405: Summary: Components in hosts page should be sorted by display name Key: AMBARI-24405 URL: https://issues.apache.org/jira/browse/AMBARI-24405 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 Components in hosts page seem to be sorted by component type (master, slave, client etc) and within them they are not sorted by "display names", "Timeline" comes before "History" More importantly people when looking for a component don't look by their type but instead look by their name. So all the components should be alphabetically sorted by their display name irrespective of their type. Else it becomes painful to look for a component of interest. (and finally have to rely on browser's search capability) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24404) Button label appears incorrect during service deletion
Aleksandr Kovalenko created AMBARI-24404: Summary: Button label appears incorrect during service deletion Key: AMBARI-24404 URL: https://issues.apache.org/jira/browse/AMBARI-24404 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 Try to delete Ranger service from a cluster, upon deletion stack advisor recommends changes to configs. This is fine, however the button at the bottom of the dialog says 'DELETE' It should instead say something like 'Proceed' and once user clicks Proceed, the delete pop-up should appear. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24391) Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS even if they dont qualify
[ https://issues.apache.org/jira/browse/AMBARI-24391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24391. -- Resolution: Fixed > Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS > even if they dont qualify > > > Key: AMBARI-24391 > URL: https://issues.apache.org/jira/browse/AMBARI-24391 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > - At customize services page - Directories tab - use properties filter to > show 'Property issues' and 'Final properties'. In both cases LOGDIR and > PIDDIR shows up as show in screenshot. There is no property in that panel but > they do show up -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24392) Align the entries in drop downs of Ambari UI left hand side pane
[ https://issues.apache.org/jira/browse/AMBARI-24392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24392. -- Resolution: Fixed > Align the entries in drop downs of Ambari UI left hand side pane > > > Key: AMBARI-24392 > URL: https://issues.apache.org/jira/browse/AMBARI-24392 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: Cluster-Admin.png, Services.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > See !Cluster-Admin.png! - it would be good to right align the entries in > the drop down > The Service pane looks better !Services.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24392) Align the entries in drop downs of Ambari UI left hand side pane
[ https://issues.apache.org/jira/browse/AMBARI-24392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24392: - Description: See !Cluster-Admin.png! - it would be good to right align the entries in the drop down The Service pane looks better !Services.png! was: See !Cluster-Admin.png! - it would be good to right align the entries in the drop down The Service pane looks better !Services.png! cc - [~paul] > Align the entries in drop downs of Ambari UI left hand side pane > > > Key: AMBARI-24392 > URL: https://issues.apache.org/jira/browse/AMBARI-24392 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Fix For: 3.0.0 > > Attachments: Cluster-Admin.png, Services.png > > > See !Cluster-Admin.png! - it would be good to right align the entries in > the drop down > The Service pane looks better !Services.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24392) Align the entries in drop downs of Ambari UI left hand side pane
[ https://issues.apache.org/jira/browse/AMBARI-24392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24392: - Description: See !Cluster-Admin.png! - it would be good to right align the entries in the drop down The Service pane looks better !Services.png! cc - [~paul] was: See !Cluster-Admin.png|thumbnail! - it would be good to right align the entries in the drop down The Service pane looks better !Services.png|thumbnail! cc - [~paul] > Align the entries in drop downs of Ambari UI left hand side pane > > > Key: AMBARI-24392 > URL: https://issues.apache.org/jira/browse/AMBARI-24392 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Major > Fix For: 3.0.0 > > Attachments: Cluster-Admin.png, Services.png > > > See !Cluster-Admin.png! - it would be good to right align the entries in > the drop down > The Service pane looks better !Services.png! > cc - [~paul] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24392) Align the entries in drop downs of Ambari UI left hand side pane
Aleksandr Kovalenko created AMBARI-24392: Summary: Align the entries in drop downs of Ambari UI left hand side pane Key: AMBARI-24392 URL: https://issues.apache.org/jira/browse/AMBARI-24392 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 Attachments: Cluster-Admin.png, Services.png See !Cluster-Admin.png|thumbnail! - it would be good to right align the entries in the drop down The Service pane looks better !Services.png|thumbnail! cc - [~paul] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24391) Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS even if they dont qualify
Aleksandr Kovalenko created AMBARI-24391: Summary: Properties filter in Customize Services Page brings up LOGDIRS and PIDDIRS even if they dont qualify Key: AMBARI-24391 URL: https://issues.apache.org/jira/browse/AMBARI-24391 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 3.0.0 - At customize services page - Directories tab - use properties filter to show 'Property issues' and 'Final properties'. In both cases LOGDIR and PIDDIR shows up as show in screenshot. There is no property in that panel but they do show up -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24315) Clicking on password warnings doesn't update the service tab navigation
[ https://issues.apache.org/jira/browse/AMBARI-24315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24315. -- Resolution: Fixed > Clicking on password warnings doesn't update the service tab navigation > --- > > Key: AMBARI-24315 > URL: https://issues.apache.org/jira/browse/AMBARI-24315 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.1 > > Time Spent: 1.5h > Remaining Estimate: 0h > > When choosing an insufficient password like 'admin' for services, we're > seeing the critical warning for password strength which is what we want, but > when you click on the property to navigate to it, the service tab navigation > is not getting updated so it "looks" like you're always in the HDFS service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24317) Lowercase g characters in the left-hand nav are getting slightly clipped bottom-up making them look like lowercase q's
Aleksandr Kovalenko created AMBARI-24317: Summary: Lowercase g characters in the left-hand nav are getting slightly clipped bottom-up making them look like lowercase q's Key: AMBARI-24317 URL: https://issues.apache.org/jira/browse/AMBARI-24317 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.1 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.1 We need to make sure the service names have enough vertical padding or ensure that they don't get clipped. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24315) Clicking on password warnings doesn't update the service tab navigation
Aleksandr Kovalenko created AMBARI-24315: Summary: Clicking on password warnings doesn't update the service tab navigation Key: AMBARI-24315 URL: https://issues.apache.org/jira/browse/AMBARI-24315 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.1 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.1 When choosing an insufficient password like 'admin' for services, we're seeing the critical warning for password strength which is what we want, but when you click on the property to navigate to it, the service tab navigation is not getting updated so it "looks" like you're always in the HDFS service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24213) Enabling RM HA should not be allowed if YARN is stopped
[ https://issues.apache.org/jira/browse/AMBARI-24213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24213. -- Resolution: Fixed > Enabling RM HA should not be allowed if YARN is stopped > --- > > Key: AMBARI-24213 > URL: https://issues.apache.org/jira/browse/AMBARI-24213 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Enabling RM HA should not be allowed if YARN is stopped. There should be a > popup message saying RM should be up before enabling HA, similar to NN HA > wizard warning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-24213) Enabling RM HA should not be allowed if YARN is stopped
[ https://issues.apache.org/jira/browse/AMBARI-24213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko reassigned AMBARI-24213: Assignee: Aleksandr Kovalenko > Enabling RM HA should not be allowed if YARN is stopped > --- > > Key: AMBARI-24213 > URL: https://issues.apache.org/jira/browse/AMBARI-24213 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Aleksandr Kovalenko >Priority: Major > Fix For: 2.7.0 > > > Enabling RM HA should not be allowed if YARN is stopped. There should be a > popup message saying RM should be up before enabling HA, similar to NN HA > wizard warning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24213) Enabling RM HA should not be allowed if YARN is stopped
[ https://issues.apache.org/jira/browse/AMBARI-24213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-24213: - Priority: Blocker (was: Major) > Enabling RM HA should not be allowed if YARN is stopped > --- > > Key: AMBARI-24213 > URL: https://issues.apache.org/jira/browse/AMBARI-24213 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Aleksandr Kovalenko >Priority: Blocker > Fix For: 2.7.0 > > > Enabling RM HA should not be allowed if YARN is stopped. There should be a > popup message saying RM should be up before enabling HA, similar to NN HA > wizard warning -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24191) Typo in div class name at CustomizeServicespage - Accounts tab
[ https://issues.apache.org/jira/browse/AMBARI-24191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24191. -- Resolution: Fixed > Typo in div class name at CustomizeServicespage - Accounts tab > -- > > Key: AMBARI-24191 > URL: https://issues.apache.org/jira/browse/AMBARI-24191 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Fix class name _use-ambari-chekboxes_ to be _use-ambari-checkboxes_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24191) Typo in div class name at CustomizeServicespage - Accounts tab
Aleksandr Kovalenko created AMBARI-24191: Summary: Typo in div class name at CustomizeServicespage - Accounts tab Key: AMBARI-24191 URL: https://issues.apache.org/jira/browse/AMBARI-24191 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Fix class name _use-ambari-chekboxes_ to be _use-ambari-checkboxes_ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24145) Ambari Master selection page breaks when you have large number of hosts
[ https://issues.apache.org/jira/browse/AMBARI-24145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24145. -- Resolution: Fixed > Ambari Master selection page breaks when you have large number of hosts > --- > > Key: AMBARI-24145 > URL: https://issues.apache.org/jira/browse/AMBARI-24145 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > I'm trying to create a a cluster via Ambari UI with 16 nodes. In the Master > selection page, if i select the the service on the bottom page and open up > the dropdown for host, the page breasks as the dropdown is larger than the > bottom div. My host maping image on the right dissapers and my navigation > buttons dissaper. I have to refresh the page to get around it.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24145) Ambari Master selection page breaks when you have large number of hosts
Aleksandr Kovalenko created AMBARI-24145: Summary: Ambari Master selection page breaks when you have large number of hosts Key: AMBARI-24145 URL: https://issues.apache.org/jira/browse/AMBARI-24145 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 I'm trying to create a a cluster via Ambari UI with 16 nodes. In the Master selection page, if i select the the service on the bottom page and open up the dropdown for host, the page breasks as the dropdown is larger than the bottom div. My host maping image on the right dissapers and my navigation buttons dissaper. I have to refresh the page to get around it.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24133) Deleting and adding the same host fails in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-24133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24133. -- Resolution: Fixed > Deleting and adding the same host fails in Ambari > - > > Key: AMBARI-24133 > URL: https://issues.apache.org/jira/browse/AMBARI-24133 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > # Delete an existing host > # Add the same host back via the Add Host wizard > # Navigate to the Review step and click Deploy button > The same step works when the page is refreshed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24133) Deleting and adding the same host fails in Ambari
Aleksandr Kovalenko created AMBARI-24133: Summary: Deleting and adding the same host fails in Ambari Key: AMBARI-24133 URL: https://issues.apache.org/jira/browse/AMBARI-24133 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 # Delete an existing host # Add the same host back via the Add Host wizard # Navigate to the Review step and click Deploy button The same step works when the page is refreshed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24127) Username case changes from Cluster info page to install wizard
[ https://issues.apache.org/jira/browse/AMBARI-24127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24127. -- Resolution: Fixed > Username case changes from Cluster info page to install wizard > -- > > Key: AMBARI-24127 > URL: https://issues.apache.org/jira/browse/AMBARI-24127 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Cluster info page shows user name as 'admin' where as in rest of the pages > its switched to uppercase and even after deployment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24127) Username case changes from Cluster info page to install wizard
Aleksandr Kovalenko created AMBARI-24127: Summary: Username case changes from Cluster info page to install wizard Key: AMBARI-24127 URL: https://issues.apache.org/jira/browse/AMBARI-24127 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Cluster info page shows user name as 'admin' where as in rest of the pages its switched to uppercase and even after deployment. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24117) Ambari "assign masters" should display available hosts in sorted order
[ https://issues.apache.org/jira/browse/AMBARI-24117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24117. -- Resolution: Fixed > Ambari "assign masters" should display available hosts in sorted order > --- > > Key: AMBARI-24117 > URL: https://issues.apache.org/jira/browse/AMBARI-24117 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The service layout often needs manual customization. We can make this process > a little easier for users by listing the available hosts in some sort of > sorted order (preferably alphabetized). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24117) Ambari "assign masters" should display available hosts in sorted order
Aleksandr Kovalenko created AMBARI-24117: Summary: Ambari "assign masters" should display available hosts in sorted order Key: AMBARI-24117 URL: https://issues.apache.org/jira/browse/AMBARI-24117 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 The service layout often needs manual customization. We can make this process a little easier for users by listing the available hosts in some sort of sorted order (preferably alphabetized). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24098) Filter have incorrect name on host page
[ https://issues.apache.org/jira/browse/AMBARI-24098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24098. -- Resolution: Fixed > Filter have incorrect name on host page > --- > > Key: AMBARI-24098 > URL: https://issues.apache.org/jira/browse/AMBARI-24098 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Actual result: some filter for components has an incorrect name "Install > Pending" but should be "Install Pending..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24098) Filter have incorrect name on host page
Aleksandr Kovalenko created AMBARI-24098: Summary: Filter have incorrect name on host page Key: AMBARI-24098 URL: https://issues.apache.org/jira/browse/AMBARI-24098 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Actual result: some filter for components has an incorrect name "Install Pending" but should be "Install Pending..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24080) [UI] Ambari label do not navigate to Dashboard page
[ https://issues.apache.org/jira/browse/AMBARI-24080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24080. -- Resolution: Fixed > [UI] Ambari label do not navigate to Dashboard page > --- > > Key: AMBARI-24080 > URL: https://issues.apache.org/jira/browse/AMBARI-24080 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Ambari label(not img) do not navigate to Dashboard page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24080) [UI] Ambari label do not navigate to Dashboard page
Aleksandr Kovalenko created AMBARI-24080: Summary: [UI] Ambari label do not navigate to Dashboard page Key: AMBARI-24080 URL: https://issues.apache.org/jira/browse/AMBARI-24080 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Ambari label(not img) do not navigate to Dashboard page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24057) Deploy button doesn't show in Review Page of Move Master Wizard
[
https://issues.apache.org/jira/browse/AMBARI-24057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko resolved AMBARI-24057.
--
Resolution: Fixed
> Deploy button doesn't show in Review Page of Move Master Wizard
> ---
>
> Key: AMBARI-24057
> URL: https://issues.apache.org/jira/browse/AMBARI-24057
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Priority: Blocker
> Fix For: 2.7.0
>
> Attachments: Screen Shot 2018-06-08 at 2.42.37 PM.png
>
>
> With ambari-2.7.0.0-657, noticed in the Review Page of Move Master Wizard for
> Hive Metastore is stuck and doesn't enable the Deploy button to proceed
> further.
> Steps:
> # Add Hive Metastore to a host
> # Select Move action in the Host Details page for Hive Metastore
> # Navigate the wizard till the Review Page
> Screenshot: !Screen Shot 2018-06-08 at 2.42.37 PM.png!
> Javascript errors:
> {code}
> app.js:31203 Uncaught TypeError: Cannot read property 'tag' of undefined
> at app.js:31203
> at Array.forEach ()
> at Class.getConfigUrlParams (app.js:31202)
> at Class.onLoadConfigsTags (app.js:31187)
> at Class.opt.success (app.js:183168)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24075) Deploy button doesn't show in Review Page of Move Master Wizard
[
https://issues.apache.org/jira/browse/AMBARI-24075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko resolved AMBARI-24075.
--
Resolution: Fixed
> Deploy button doesn't show in Review Page of Move Master Wizard
> ---
>
> Key: AMBARI-24075
> URL: https://issues.apache.org/jira/browse/AMBARI-24075
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Noticed in the Review Page of Move Master Wizard for Hive Metastore is stuck
> and doesn't enable the Deploy button to proceed further.
> Steps:
> # Add Hive Metastore to a host
> # Select Move action in the Host Details page for Hive Metastore
> # Navigate the wizard till the Review Page
> Javascript errors:
> {code}
> app.js:31203 Uncaught TypeError: Cannot read property 'tag' of undefined
> at app.js:31203
> at Array.forEach ()
> at Class.getConfigUrlParams (app.js:31202)
> at Class.onLoadConfigsTags (app.js:31187)
> at Class.opt.success (app.js:183168)
> at fire (vendor.js:1141)
> at Object.fireWith [as resolveWith] (vendor.js:1252)
> at done (vendor.js:8178)
> at XMLHttpRequest.callback (vendor.js:8702)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-24075) Deploy button doesn't show in Review Page of Move Master Wizard
Aleksandr Kovalenko created AMBARI-24075:
Summary: Deploy button doesn't show in Review Page of Move Master
Wizard
Key: AMBARI-24075
URL: https://issues.apache.org/jira/browse/AMBARI-24075
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Fix For: 2.7.0
Noticed in the Review Page of Move Master Wizard for Hive Metastore is stuck
and doesn't enable the Deploy button to proceed further.
Steps:
# Add Hive Metastore to a host
# Select Move action in the Host Details page for Hive Metastore
# Navigate the wizard till the Review Page
Javascript errors:
{code}
app.js:31203 Uncaught TypeError: Cannot read property 'tag' of undefined
at app.js:31203
at Array.forEach ()
at Class.getConfigUrlParams (app.js:31202)
at Class.onLoadConfigsTags (app.js:31187)
at Class.opt.success (app.js:183168)
at fire (vendor.js:1141)
at Object.fireWith [as resolveWith] (vendor.js:1252)
at done (vendor.js:8178)
at XMLHttpRequest.callback (vendor.js:8702)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-24061) Clicking on 'Details' button in Upgrade wizard shows no data
[ https://issues.apache.org/jira/browse/AMBARI-24061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24061. -- Resolution: Fixed > Clicking on 'Details' button in Upgrade wizard shows no data > > > Key: AMBARI-24061 > URL: https://issues.apache.org/jira/browse/AMBARI-24061 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > When clicked on 'show details' button while Upgrade is in progress, it shows > a spinning icon and no data underneath. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24061) Clicking on 'Details' button in Upgrade wizard shows no data
Aleksandr Kovalenko created AMBARI-24061: Summary: Clicking on 'Details' button in Upgrade wizard shows no data Key: AMBARI-24061 URL: https://issues.apache.org/jira/browse/AMBARI-24061 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 When clicked on 'show details' button while Upgrade is in progress, it shows a spinning icon and no data underneath. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24044) Widget Browser add/hide functionality is not working correctly
[ https://issues.apache.org/jira/browse/AMBARI-24044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24044. -- Resolution: Fixed > Widget Browser add/hide functionality is not working correctly > -- > > Key: AMBARI-24044 > URL: https://issues.apache.org/jira/browse/AMBARI-24044 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Widget browser add/hide widget functionality is not working correctly if > widget is included in several widget_layouts as in case of several NameNode > Namespaces. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24044) Widget Browser add/hide functionality is not working correctly
Aleksandr Kovalenko created AMBARI-24044: Summary: Widget Browser add/hide functionality is not working correctly Key: AMBARI-24044 URL: https://issues.apache.org/jira/browse/AMBARI-24044 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Widget browser add/hide widget functionality is not working correctly if widget is included in several widget_layouts as in case of several NameNode Namespaces. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24036) Config Group Names are converted to uppercase once selected on UI
[ https://issues.apache.org/jira/browse/AMBARI-24036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24036. -- Resolution: Fixed > Config Group Names are converted to uppercase once selected on UI > - > > Key: AMBARI-24036 > URL: https://issues.apache.org/jira/browse/AMBARI-24036 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Once selected config group names are converted to uppercase on UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24036) Config Group Names are converted to uppercase once selected on UI
Aleksandr Kovalenko created AMBARI-24036: Summary: Config Group Names are converted to uppercase once selected on UI Key: AMBARI-24036 URL: https://issues.apache.org/jira/browse/AMBARI-24036 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Once selected config group names are converted to uppercase on UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-24001) Recommission action doesn't appear for decommissioned component
[ https://issues.apache.org/jira/browse/AMBARI-24001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-24001. -- Resolution: Fixed > Recommission action doesn't appear for decommissioned component > --- > > Key: AMBARI-24001 > URL: https://issues.apache.org/jira/browse/AMBARI-24001 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Recomission action doesn't appear for decommissioned component > STR: > 1)Go to the host details page with Datanode > 2)Decommission Datanode > 3)Open component action > Expected: > Decommission is absent > Recommission is present > Actual: > Recommission is absent > Decommission is present -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-24001) Recommission action doesn't appear for decommissioned component
Aleksandr Kovalenko created AMBARI-24001: Summary: Recommission action doesn't appear for decommissioned component Key: AMBARI-24001 URL: https://issues.apache.org/jira/browse/AMBARI-24001 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Recomission action doesn't appear for decommissioned component STR: 1)Go to the host details page with Datanode 2)Decommission Datanode 3)Open component action Expected: Decommission is absent Recommission is present Actual: Recommission is absent Decommission is present -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23981) HDFS Summary widgets disappear after changing widgets order
[ https://issues.apache.org/jira/browse/AMBARI-23981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23981. -- Resolution: Fixed > HDFS Summary widgets disappear after changing widgets order > --- > > Key: AMBARI-23981 > URL: https://issues.apache.org/jira/browse/AMBARI-23981 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > STR: > 1. Add Namespace. > 2. Open HDFS service metrics page and change order of NS-specific widgets. > 3. Refresh the page and check general widgets. > It should not be empty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23731) Restart required services results in restart NN twice
[ https://issues.apache.org/jira/browse/AMBARI-23731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23731. -- Resolution: Fixed > Restart required services results in restart NN twice > - > > Key: AMBARI-23731 > URL: https://issues.apache.org/jira/browse/AMBARI-23731 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > On large clusters restart NN can take 40 mins , if we start nn1 and nn2 in > Start Namenodes step they should not be Restarted again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23559) Journalnode restart step is required when edits dir is changed
[
https://issues.apache.org/jira/browse/AMBARI-23559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko resolved AMBARI-23559.
--
Resolution: Fixed
> Journalnode restart step is required when edits dir is changed
> --
>
> Key: AMBARI-23559
> URL: https://issues.apache.org/jira/browse/AMBARI-23559
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Journal node does not create the edits directory in the right place because
> it is not restarted and hence does not load the new configurations resulting
> in the following error:
> {code}
> 2018-04-11 23:19:39,835 FATAL namenode.FSEditLog
> (JournalSet.java:mapJournalsAndReportErrors(390)) - Error:
> recoverUnfinalizedSegments failed for required journal (JournalAndSt
> ream(mgr=QJM to [10.240.0.23:8485, 10.240.0.32:8485, 10.240.0.95:8485],
> stream=null))
> org.apache.hadoop.hdfs.qjournal.client.QuorumException: Got too many
> exceptions to achieve quorum size 2/3. 3 exceptions thrown:
> 10.240.0.23:8485: Journal Storage Directory root= /hadoop2/hdfs/journal/ns2;
> location= null not formatted
> at
> org.apache.hadoop.hdfs.qjournal.server.Journal.checkFormatted(Journal.java:500)
> at
> org.apache.hadoop.hdfs.qjournal.server.Journal.getLastPromisedEpoch(Journal.java:262)
> {code}
> Need to add Restart All Journal nodes step right *before* the Format Namenode
> step in the wizard.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23707) NN Federation Wizard: move out of wizard create widgets operaions
[ https://issues.apache.org/jira/browse/AMBARI-23707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23707. -- Resolution: Fixed > NN Federation Wizard: move out of wizard create widgets operaions > - > > Key: AMBARI-23707 > URL: https://issues.apache.org/jira/browse/AMBARI-23707 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > As we should handle installing Ambari with federation from blueprint, we > should move create widgets logic out of wizard and run it on first dashboard > page visit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23792) Need Ranger Tagsync component to be started at end during restart all services task for Federation wizard
[ https://issues.apache.org/jira/browse/AMBARI-23792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23792. -- Resolution: Fixed > Need Ranger Tagsync component to be started at end during restart all > services task for Federation wizard > - > > Key: AMBARI-23792 > URL: https://issues.apache.org/jira/browse/AMBARI-23792 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Current implementation on Federation wizard start Ranger Tagsync before > Namenode start during start task of Ranger Service. Need Ranger Tagsync > component to be stopped when we are updating service name in restart of > namenode. > So following sequence of starting services needs to be considered. > # Stop Tagsync (as part of stop all services) > # Start Ranger Admin and Ranger Usersync > # Start Namenode > # Start Ranger Tagsync -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23981) HDFS Summary widgets disappear after changing widgets order
Aleksandr Kovalenko created AMBARI-23981: Summary: HDFS Summary widgets disappear after changing widgets order Key: AMBARI-23981 URL: https://issues.apache.org/jira/browse/AMBARI-23981 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 STR: 1. Add Namespace. 2. Open HDFS service metrics page and change order of NS-specific widgets. 3. Refresh the page and check general widgets. It should not be empty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23967) Dashboard,component information for few componets is not able to load after Ambari Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-23967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23967. -- Resolution: Fixed > Dashboard,component information for few componets is not able to load after > Ambari Upgrade > -- > > Key: AMBARI-23967 > URL: https://issues.apache.org/jira/browse/AMBARI-23967 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > 1) Upgrade Ambari from 2.6.1.5 to 2.7.0.0 > 2) Upgrade Ambari Infra and Logsearch > Post this, Ambari Dashboard is unable to load. Also for many components , the > component information is missing. Actions Menu keeps loading on clicking. > Quick links also do not load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23967) Dashboard,component information for few componets is not able to load after Ambari Upgrade
Aleksandr Kovalenko created AMBARI-23967: Summary: Dashboard,component information for few componets is not able to load after Ambari Upgrade Key: AMBARI-23967 URL: https://issues.apache.org/jira/browse/AMBARI-23967 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 1) Upgrade Ambari from 2.6.1.5 to 2.7.0.0 2) Upgrade Ambari Infra and Logsearch Post this, Ambari Dashboard is unable to load. Also for many components , the component information is missing. Actions Menu keeps loading on clicking. Quick links also do not load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23754) UI Issues for HDFS Metrics when having multiple namespaces
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko resolved AMBARI-23754. -- Resolution: Fixed > UI Issues for HDFS Metrics when having multiple namespaces > -- > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Aleksandr Kovalenko >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png, image-2018-05-07-11-08-12-178.png, > image-2018-05-07-11-08-25-003.png, image-2018-05-07-11-08-25-040.png, > image-2018-05-07-11-08-35-838.png, image-2018-05-07-11-08-35-880.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > !image-2018-05-07-11-08-12-178.png! > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > !image-2018-05-07-11-08-25-040.png!!image-2018-05-07-11-08-25-003.png! > > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > !image-2018-05-07-11-08-35-880.png!!image-2018-05-07-11-08-35-838.png! > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-23754) UI Issues for HDFS Metrics when having multiple namespaces
[ https://issues.apache.org/jira/browse/AMBARI-23754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko reassigned AMBARI-23754: Assignee: Aleksandr Kovalenko > UI Issues for HDFS Metrics when having multiple namespaces > -- > > Key: AMBARI-23754 > URL: https://issues.apache.org/jira/browse/AMBARI-23754 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Vivek Rathod >Assignee: Aleksandr Kovalenko >Priority: Major > Fix For: 2.7.0 > > Attachments: Issue #1.png, Issue #2 Create custom widget for > Namespace.png, Issue #2.png, Issue #3 -1.png, Issue #3 -2.png, Screen Shot > 2018-05-02 at 4.10.46 PM.png, Screen Shot 2018-05-02 at 4.20.20 PM.png, > Screen Shot 2018-05-02 at 4.21.31 PM.png, image-2018-05-07-11-08-12-178.png, > image-2018-05-07-11-08-25-003.png, image-2018-05-07-11-08-25-040.png, > image-2018-05-07-11-08-35-838.png, image-2018-05-07-11-08-35-880.png > > > Issue #1) > On Hdfs metrics page, add a widget. That is displayed in the top panel for > the default namespace and then at the bottom for the namespace selected > (ns1,ns2 or All) > Should the widget on the top show the aggregate metrics instead of metrics > for just default namespace? > OR > Should they not appear in the top section and be displayed only for the > namespace selected at the bottom? > !image-2018-05-07-11-08-12-178.png! > Issue #2) > Create custom widget for a namespace > No Namespace name next to the custom widget > !image-2018-05-07-11-08-25-040.png!!image-2018-05-07-11-08-25-003.png! > > Issue #3) > Duplicate widgets in the Browse Widgets window where there are multiple > namespaces > !image-2018-05-07-11-08-35-880.png!!image-2018-05-07-11-08-35-838.png! > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23792) Need Ranger Tagsync component to be started at end during restart all services task for Federation wizard
Aleksandr Kovalenko created AMBARI-23792: Summary: Need Ranger Tagsync component to be started at end during restart all services task for Federation wizard Key: AMBARI-23792 URL: https://issues.apache.org/jira/browse/AMBARI-23792 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.7.0 Current implementation on Federation wizard start Ranger Tagsync before Namenode start during start task of Ranger Service. Need Ranger Tagsync component to be stopped when we are updating service name in restart of namenode. So following sequence of starting services needs to be considered. # Stop Tagsync (as part of stop all services) # Start Ranger Admin and Ranger Usersync # Start Namenode # Start Ranger Tagsync -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23703) While adding HDFS Namespace from UI, Timeline service fails to start
[
https://issues.apache.org/jira/browse/AMBARI-23703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko resolved AMBARI-23703.
--
Resolution: Fixed
> While adding HDFS Namespace from UI, Timeline service fails to start
>
>
> Key: AMBARI-23703
> URL: https://issues.apache.org/jira/browse/AMBARI-23703
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Endre Major
>Assignee: Endre Major
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> While adding HDFS Namespace from UI, Timeline service fails to start in the
> last step ("Restart All Services") because the active Namenode(from older
> namespace) is in Safe Mode
> In Restart all services, Timeline Service starts right after Old Active NN
> starts
> This might be intermittent timing issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (AMBARI-23703) While adding HDFS Namespace from UI, Timeline service fails to start
[
https://issues.apache.org/jira/browse/AMBARI-23703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko reopened AMBARI-23703:
--
> While adding HDFS Namespace from UI, Timeline service fails to start
>
>
> Key: AMBARI-23703
> URL: https://issues.apache.org/jira/browse/AMBARI-23703
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Endre Major
>Assignee: Endre Major
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> While adding HDFS Namespace from UI, Timeline service fails to start in the
> last step ("Restart All Services") because the active Namenode(from older
> namespace) is in Safe Mode
> In Restart all services, Timeline Service starts right after Old Active NN
> starts
> This might be intermittent timing issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
