[jira] [Created] (AMBARI-25494) Ambari - Unsafe third-party link (target="_blank")
Antonenko Alexander created AMBARI-25494: Summary: Ambari - Unsafe third-party link (target="_blank") Key: AMBARI-25494 URL: https://issues.apache.org/jira/browse/AMBARI-25494 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.3 Reporter: Antonenko Alexander Fix For: 2.7.6 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25494) Ambari - Unsafe third-party link (target="_blank")
[ https://issues.apache.org/jira/browse/AMBARI-25494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25494: Assignee: Antonenko Alexander > Ambari - Unsafe third-party link (target="_blank") > -- > > Key: AMBARI-25494 > URL: https://issues.apache.org/jira/browse/AMBARI-25494 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.6 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25493) Ambari - Application Test Script Detected
Antonenko Alexander created AMBARI-25493: Summary: Ambari - Application Test Script Detected Key: AMBARI-25493 URL: https://issues.apache.org/jira/browse/AMBARI-25493 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.3 Reporter: Antonenko Alexander Fix For: 2.7.6 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25493) Ambari - Application Test Script Detected
[ https://issues.apache.org/jira/browse/AMBARI-25493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25493: Assignee: Antonenko Alexander > Ambari - Application Test Script Detected > - > > Key: AMBARI-25493 > URL: https://issues.apache.org/jira/browse/AMBARI-25493 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.6 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25489) On adding new VDF the Base URLs are not auto populated
Antonenko Alexander created AMBARI-25489: Summary: On adding new VDF the Base URLs are not auto populated Key: AMBARI-25489 URL: https://issues.apache.org/jira/browse/AMBARI-25489 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.6 Reporter: Antonenko Alexander Fix For: 2.7.6 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25489) On adding new VDF the Base URLs are not auto populated
[ https://issues.apache.org/jira/browse/AMBARI-25489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25489: Assignee: Antonenko Alexander > On adding new VDF the Base URLs are not auto populated > -- > > Key: AMBARI-25489 > URL: https://issues.apache.org/jira/browse/AMBARI-25489 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.6 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.6 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25487) Change authentication method from get to post
[ https://issues.apache.org/jira/browse/AMBARI-25487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25487: - Status: Patch Available (was: Open) > Change authentication method from get to post > - > > Key: AMBARI-25487 > URL: https://issues.apache.org/jira/browse/AMBARI-25487 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25487) Change authentication method from get to post
Antonenko Alexander created AMBARI-25487: Summary: Change authentication method from get to post Key: AMBARI-25487 URL: https://issues.apache.org/jira/browse/AMBARI-25487 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.7.6 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25486) Configs page not loading after Ambari upgrade
Antonenko Alexander created AMBARI-25486: Summary: Configs page not loading after Ambari upgrade Key: AMBARI-25486 URL: https://issues.apache.org/jira/browse/AMBARI-25486 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Fix For: 2.7.6 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25477) Add autocomplete off to all forms
[ https://issues.apache.org/jira/browse/AMBARI-25477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25477: - Status: Patch Available (was: Open) > Add autocomplete off to all forms > - > > Key: AMBARI-25477 > URL: https://issues.apache.org/jira/browse/AMBARI-25477 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-24517) Cover add standby step 4 controller
[ https://issues.apache.org/jira/browse/AMBARI-24517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-24517. -- Resolution: Fixed > Cover add standby step 4 controller > --- > > Key: AMBARI-24517 > URL: https://issues.apache.org/jira/browse/AMBARI-24517 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-24944) Cover cluster metric cpu view
[ https://issues.apache.org/jira/browse/AMBARI-24944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-24944: - Resolution: Fixed Status: Resolved (was: Patch Available) > Cover cluster metric cpu view > - > > Key: AMBARI-24944 > URL: https://issues.apache.org/jira/browse/AMBARI-24944 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25109) Cover onefs view
[ https://issues.apache.org/jira/browse/AMBARI-25109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25109: - Resolution: Fixed Status: Resolved (was: Patch Available) > Cover onefs view > > > Key: AMBARI-25109 > URL: https://issues.apache.org/jira/browse/AMBARI-25109 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25060) Install wizard fails on step 8
[ https://issues.apache.org/jira/browse/AMBARI-25060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-25060. -- Resolution: Fixed > Install wizard fails on step 8 > -- > > Key: AMBARI-25060 > URL: https://issues.apache.org/jira/browse/AMBARI-25060 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25120) Cover Assign Master Components Views
[ https://issues.apache.org/jira/browse/AMBARI-25120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-25120. -- Resolution: Fixed > Cover Assign Master Components Views > > > Key: AMBARI-25120 > URL: https://issues.apache.org/jira/browse/AMBARI-25120 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25121) Cover editable list view
[ https://issues.apache.org/jira/browse/AMBARI-25121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25121: - Resolution: Fixed Status: Resolved (was: Patch Available) > Cover editable list view > > > Key: AMBARI-25121 > URL: https://issues.apache.org/jira/browse/AMBARI-25121 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25132) Cover metric view
[ https://issues.apache.org/jira/browse/AMBARI-25132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-25132. -- Resolution: Won't Fix > Cover metric view > - > > Key: AMBARI-25132 > URL: https://issues.apache.org/jira/browse/AMBARI-25132 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25157) Cover Overridden Row View
[ https://issues.apache.org/jira/browse/AMBARI-25157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-25157. -- Resolution: Won't Fix > Cover Overridden Row View > - > > Key: AMBARI-25157 > URL: https://issues.apache.org/jira/browse/AMBARI-25157 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > app/views/common/configs/overriddenPropertyRow_view.js -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25367) backport of Heatmap Data Issues
[ https://issues.apache.org/jira/browse/AMBARI-25367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-25367. -- Resolution: Fixed > backport of Heatmap Data Issues > --- > > Key: AMBARI-25367 > URL: https://issues.apache.org/jira/browse/AMBARI-25367 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.6.0 > > Time Spent: 1h > Remaining Estimate: 0h > > "Data Not Available" in Dashboard / Heatmap for: > * Host Disk Space Used % > * Host Memory Used % > "Invalid Data" in Dashboard / Heatmap for: > * DataNode Process Disk I/O Utilization > * DataNode Process Network I/O Utilization > These should all be reporting data. > STR: > - Install ZooKeeper, HDFS, AMS, SmartSense > - Wait a 10 minutes to ensure data is coming into AMS > - Click on Dashboard / Heatmap and view these metrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25395) Update help text in Hive install provide a clearly formatted example
[ https://issues.apache.org/jira/browse/AMBARI-25395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25395: - Resolution: Fixed Status: Resolved (was: Patch Available) > Update help text in Hive install provide a clearly formatted example > > > Key: AMBARI-25395 > URL: https://issues.apache.org/jira/browse/AMBARI-25395 > Project: Ambari > Issue Type: Task >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > Update the help text displayed in Ambari during the Hive service install so > that there is a clearly labeled/formatted example of the download and/or an > accurate JAR filename example. The text as displayed presents > com.mysql.jdbc.driver as if it was a JAR file name, which may confuse some > users. (screenshot attached) > Provide a monospaced example ambari-server-setup command, such as in the > documentation here: > ambari-server setup --jdbc-db=mysql > --jdbc-driver=/path/to/mysql/mysql-connector-java.jar -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25410) Add autocomplete for all repos url for login and password
[ https://issues.apache.org/jira/browse/AMBARI-25410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-25410. -- Resolution: Fixed > Add autocomplete for all repos url for login and password > - > > Key: AMBARI-25410 > URL: https://issues.apache.org/jira/browse/AMBARI-25410 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > When user put his credentials for first or any links we need automatically to > add them in every link field. > If he will edit these credentials in any of existing fields - it should be > updated everywhere > We need to do this in ambari wizard and ambari-admin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25481) Customize Widget Threshold validation issue
[ https://issues.apache.org/jira/browse/AMBARI-25481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-25481. -- Resolution: Fixed > Customize Widget Threshold validation issue > --- > > Key: AMBARI-25481 > URL: https://issues.apache.org/jira/browse/AMBARI-25481 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.6 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.6 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25481) Customize Widget Threshold validation issue
Antonenko Alexander created AMBARI-25481: Summary: Customize Widget Threshold validation issue Key: AMBARI-25481 URL: https://issues.apache.org/jira/browse/AMBARI-25481 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.6 Reporter: Antonenko Alexander Fix For: 2.7.6 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25481) Customize Widget Threshold validation issue
[ https://issues.apache.org/jira/browse/AMBARI-25481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25481: Assignee: Antonenko Alexander > Customize Widget Threshold validation issue > --- > > Key: AMBARI-25481 > URL: https://issues.apache.org/jira/browse/AMBARI-25481 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.6 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.6 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25477) Add autocomplete off to all forms
Antonenko Alexander created AMBARI-25477: Summary: Add autocomplete off to all forms Key: AMBARI-25477 URL: https://issues.apache.org/jira/browse/AMBARI-25477 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25477) Add autocomplete off to all forms
[ https://issues.apache.org/jira/browse/AMBARI-25477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25477: Assignee: Antonenko Alexander > Add autocomplete off to all forms > - > > Key: AMBARI-25477 > URL: https://issues.apache.org/jira/browse/AMBARI-25477 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25472) Disable autocomplete on login screen
[ https://issues.apache.org/jira/browse/AMBARI-25472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25472: - Status: Patch Available (was: Open) > Disable autocomplete on login screen > > > Key: AMBARI-25472 > URL: https://issues.apache.org/jira/browse/AMBARI-25472 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25472) Disable autocomplete on login screen
[ https://issues.apache.org/jira/browse/AMBARI-25472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25472: Assignee: Antonenko Alexander > Disable autocomplete on login screen > > > Key: AMBARI-25472 > URL: https://issues.apache.org/jira/browse/AMBARI-25472 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.5 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25472) Disable autocomplete on login screen
Antonenko Alexander created AMBARI-25472: Summary: Disable autocomplete on login screen Key: AMBARI-25472 URL: https://issues.apache.org/jira/browse/AMBARI-25472 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander Fix For: 2.7.5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-25461) Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir
[ https://issues.apache.org/jira/browse/AMBARI-25461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023047#comment-17023047 ] Antonenko Alexander commented on AMBARI-25461: -- Committed to branch-2.6 > Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir > - > > Key: AMBARI-25461 > URL: https://issues.apache.org/jira/browse/AMBARI-25461 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25461) Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir
[ https://issues.apache.org/jira/browse/AMBARI-25461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25461: - Resolution: Fixed Status: Resolved (was: Patch Available) > Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir > - > > Key: AMBARI-25461 > URL: https://issues.apache.org/jira/browse/AMBARI-25461 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25461) Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir
[ https://issues.apache.org/jira/browse/AMBARI-25461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25461: - Status: Patch Available (was: Open) > Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir > - > > Key: AMBARI-25461 > URL: https://issues.apache.org/jira/browse/AMBARI-25461 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25461) Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir
[ https://issues.apache.org/jira/browse/AMBARI-25461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25461: Assignee: Antonenko Alexander > Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir > - > > Key: AMBARI-25461 > URL: https://issues.apache.org/jira/browse/AMBARI-25461 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25461) Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir
Antonenko Alexander created AMBARI-25461: Summary: Move JournalNode wizard generates wrong dfs.namenode.shared.edits.dir Key: AMBARI-25461 URL: https://issues.apache.org/jira/browse/AMBARI-25461 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.6.2 Reporter: Antonenko Alexander Fix For: 2.6.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-25453) If hive.server2.webui.use.ssl was setted to true it will always use https, does not matter if now it is false
[ https://issues.apache.org/jira/browse/AMBARI-25453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004109#comment-17004109 ] Antonenko Alexander commented on AMBARI-25453: -- Committed to branch-2.7 > If hive.server2.webui.use.ssl was setted to true it will always use https, > does not matter if now it is false > - > > Key: AMBARI-25453 > URL: https://issues.apache.org/jira/browse/AMBARI-25453 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25453) If hive.server2.webui.use.ssl was setted to true it will always use https, does not matter if now it is false
[ https://issues.apache.org/jira/browse/AMBARI-25453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25453: - Resolution: Fixed Status: Resolved (was: Patch Available) > If hive.server2.webui.use.ssl was setted to true it will always use https, > does not matter if now it is false > - > > Key: AMBARI-25453 > URL: https://issues.apache.org/jira/browse/AMBARI-25453 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25453) If hive.server2.webui.use.ssl was setted to true it will always use https, does not matter if now it is false
[ https://issues.apache.org/jira/browse/AMBARI-25453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25453: - Status: Patch Available (was: Open) > If hive.server2.webui.use.ssl was setted to true it will always use https, > does not matter if now it is false > - > > Key: AMBARI-25453 > URL: https://issues.apache.org/jira/browse/AMBARI-25453 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25453) If hive.server2.webui.use.ssl was setted to true it will always use https, does not matter if now it is false
Antonenko Alexander created AMBARI-25453: Summary: If hive.server2.webui.use.ssl was setted to true it will always use https, does not matter if now it is false Key: AMBARI-25453 URL: https://issues.apache.org/jira/browse/AMBARI-25453 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25453) If hive.server2.webui.use.ssl was setted to true it will always use https, does not matter if now it is false
[ https://issues.apache.org/jira/browse/AMBARI-25453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25453: Assignee: Antonenko Alexander > If hive.server2.webui.use.ssl was setted to true it will always use https, > does not matter if now it is false > - > > Key: AMBARI-25453 > URL: https://issues.apache.org/jira/browse/AMBARI-25453 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25448) Mask credentials during install step
[ https://issues.apache.org/jira/browse/AMBARI-25448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25448: - Resolution: Fixed Status: Resolved (was: Patch Available) > Mask credentials during install step > > > Key: AMBARI-25448 > URL: https://issues.apache.org/jira/browse/AMBARI-25448 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 20m > Remaining Estimate: 0h > > This ticket is about masking out credentials (*:*) in the deploy phase -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-25448) Mask credentials during install step
[ https://issues.apache.org/jira/browse/AMBARI-25448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995270#comment-16995270 ] Antonenko Alexander commented on AMBARI-25448: -- Committed to branch-2.7 > Mask credentials during install step > > > Key: AMBARI-25448 > URL: https://issues.apache.org/jira/browse/AMBARI-25448 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 20m > Remaining Estimate: 0h > > This ticket is about masking out credentials (*:*) in the deploy phase -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25448) Mask credentials during install step
[ https://issues.apache.org/jira/browse/AMBARI-25448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25448: - Status: Patch Available (was: Open) > Mask credentials during install step > > > Key: AMBARI-25448 > URL: https://issues.apache.org/jira/browse/AMBARI-25448 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > This ticket is about masking out credentials (*:*) in the deploy phase -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25448) Mask credentials during install step
[ https://issues.apache.org/jira/browse/AMBARI-25448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25448: Assignee: Antonenko Alexander > Mask credentials during install step > > > Key: AMBARI-25448 > URL: https://issues.apache.org/jira/browse/AMBARI-25448 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.7.5 > > > This ticket is about masking out credentials (*:*) in the deploy phase -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25448) Mask credentials during install step
Antonenko Alexander created AMBARI-25448: Summary: Mask credentials during install step Key: AMBARI-25448 URL: https://issues.apache.org/jira/browse/AMBARI-25448 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander Fix For: 2.7.5 This ticket is about masking out credentials (*:*) in the deploy phase -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25441) HDP-GPL field is not available in version registration page but present in edit page
[ https://issues.apache.org/jira/browse/AMBARI-25441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25441: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.7 > HDP-GPL field is not available in version registration page but present in > edit page > > > Key: AMBARI-25441 > URL: https://issues.apache.org/jira/browse/AMBARI-25441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 0.5h > Remaining Estimate: 0h > > New version registration page does not have HDP-GPL field. But this field is > present when we are editing the version urls after registering. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25441) HDP-GPL field is not available in version registration page but present in edit page
[ https://issues.apache.org/jira/browse/AMBARI-25441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25441: - Status: Patch Available (was: Open) > HDP-GPL field is not available in version registration page but present in > edit page > > > Key: AMBARI-25441 > URL: https://issues.apache.org/jira/browse/AMBARI-25441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > New version registration page does not have HDP-GPL field. But this field is > present when we are editing the version urls after registering. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25441) HDP-GPL field is not available in version registration page but present in edit page
Antonenko Alexander created AMBARI-25441: Summary: HDP-GPL field is not available in version registration page but present in edit page Key: AMBARI-25441 URL: https://issues.apache.org/jira/browse/AMBARI-25441 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander Fix For: 2.7.5 New version registration page does not have HDP-GPL field. But this field is present when we are editing the version urls after registering. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25441) HDP-GPL field is not available in version registration page but present in edit page
[ https://issues.apache.org/jira/browse/AMBARI-25441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25441: Assignee: Antonenko Alexander > HDP-GPL field is not available in version registration page but present in > edit page > > > Key: AMBARI-25441 > URL: https://issues.apache.org/jira/browse/AMBARI-25441 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.7.5 > > > New version registration page does not have HDP-GPL field. But this field is > present when we are editing the version urls after registering. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25439) XSS vulnerability for repo check hint
[ https://issues.apache.org/jira/browse/AMBARI-25439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25439: - Status: Patch Available (was: Open) > XSS vulnerability for repo check hint > - > > Key: AMBARI-25439 > URL: https://issues.apache.org/jira/browse/AMBARI-25439 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > For now UI parses repo error hint as html. It is potential XSS vulnerability. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25439) XSS vulnerability for repo check hint
Antonenko Alexander created AMBARI-25439: Summary: XSS vulnerability for repo check hint Key: AMBARI-25439 URL: https://issues.apache.org/jira/browse/AMBARI-25439 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander Fix For: 2.7.5 For now UI parses repo error hint as html. It is potential XSS vulnerability. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25439) XSS vulnerability for repo check hint
[ https://issues.apache.org/jira/browse/AMBARI-25439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25439: Assignee: Antonenko Alexander > XSS vulnerability for repo check hint > - > > Key: AMBARI-25439 > URL: https://issues.apache.org/jira/browse/AMBARI-25439 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.7.5 > > > For now UI parses repo error hint as html. It is potential XSS vulnerability. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25436) Unable to uncheck 'hidden' checkbox in ambari stackVersions page
[ https://issues.apache.org/jira/browse/AMBARI-25436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25436: - Status: Patch Available (was: Open) > Unable to uncheck 'hidden' checkbox in ambari stackVersions page > > > Key: AMBARI-25436 > URL: https://issues.apache.org/jira/browse/AMBARI-25436 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > If version is hidden - we need always allow to make it visible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25436) Unable to uncheck 'hidden' checkbox in ambari stackVersions page
Antonenko Alexander created AMBARI-25436: Summary: Unable to uncheck 'hidden' checkbox in ambari stackVersions page Key: AMBARI-25436 URL: https://issues.apache.org/jira/browse/AMBARI-25436 Project: Ambari Issue Type: Task Components: ambari-admin Affects Versions: 2.7.5 Reporter: Antonenko Alexander Fix For: 2.7.5 If version is hidden - we need always allow to make it visible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25436) Unable to uncheck 'hidden' checkbox in ambari stackVersions page
[ https://issues.apache.org/jira/browse/AMBARI-25436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25436: Assignee: Antonenko Alexander > Unable to uncheck 'hidden' checkbox in ambari stackVersions page > > > Key: AMBARI-25436 > URL: https://issues.apache.org/jira/browse/AMBARI-25436 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.7.5 > > > If version is hidden - we need always allow to make it visible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25425) Recommendations API error during cluster creation wizard
[ https://issues.apache.org/jira/browse/AMBARI-25425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25425: - Resolution: Fixed Status: Resolved (was: Patch Available) > Recommendations API error during cluster creation wizard > > > Key: AMBARI-25425 > URL: https://issues.apache.org/jira/browse/AMBARI-25425 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 40m > Remaining Estimate: 0h > > Ambari Cluster wizard step #7 shows an error. The recommendations API returns > with [400] BadRequest as no clusterId is provided in the http request body. > UI is sending wrong request. > Same issue exists on kerberos wizard -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-25425) Recommendations API error during cluster creation wizard
[ https://issues.apache.org/jira/browse/AMBARI-25425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16982942#comment-16982942 ] Antonenko Alexander commented on AMBARI-25425: -- Committed to branch-2.7 > Recommendations API error during cluster creation wizard > > > Key: AMBARI-25425 > URL: https://issues.apache.org/jira/browse/AMBARI-25425 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 40m > Remaining Estimate: 0h > > Ambari Cluster wizard step #7 shows an error. The recommendations API returns > with [400] BadRequest as no clusterId is provided in the http request body. > UI is sending wrong request. > Same issue exists on kerberos wizard -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25425) Recommendations API error during cluster creation wizard
[ https://issues.apache.org/jira/browse/AMBARI-25425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25425: - Status: Patch Available (was: Open) > Recommendations API error during cluster creation wizard > > > Key: AMBARI-25425 > URL: https://issues.apache.org/jira/browse/AMBARI-25425 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > Ambari Cluster wizard step #7 shows an error. The recommendations API returns > with [400] BadRequest as no clusterId is provided in the http request body. > UI is sending wrong request. > Same issue exists on kerberos wizard -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25425) Recommendations API error during cluster creation wizard
[ https://issues.apache.org/jira/browse/AMBARI-25425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25425: Assignee: Antonenko Alexander > Recommendations API error during cluster creation wizard > > > Key: AMBARI-25425 > URL: https://issues.apache.org/jira/browse/AMBARI-25425 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.7.5 > > > Ambari Cluster wizard step #7 shows an error. The recommendations API returns > with [400] BadRequest as no clusterId is provided in the http request body. > UI is sending wrong request. > Same issue exists on kerberos wizard -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25425) Recommendations API error during cluster creation wizard
Antonenko Alexander created AMBARI-25425: Summary: Recommendations API error during cluster creation wizard Key: AMBARI-25425 URL: https://issues.apache.org/jira/browse/AMBARI-25425 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander Fix For: 2.7.5 Ambari Cluster wizard step #7 shows an error. The recommendations API returns with [400] BadRequest as no clusterId is provided in the http request body. UI is sending wrong request. Same issue exists on kerberos wizard -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25421) HSI Start failing when enabled from Hive>Configs tab
[ https://issues.apache.org/jira/browse/AMBARI-25421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25421: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.7 > HSI Start failing when enabled from Hive>Configs tab > > > Key: AMBARI-25421 > URL: https://issues.apache.org/jira/browse/AMBARI-25421 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25421) HSI Start failing when enabled from Hive>Configs tab
[ https://issues.apache.org/jira/browse/AMBARI-25421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25421: - Assignee: Antonenko Alexander Status: Patch Available (was: Open) > HSI Start failing when enabled from Hive>Configs tab > > > Key: AMBARI-25421 > URL: https://issues.apache.org/jira/browse/AMBARI-25421 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25421) HSI Start failing when enabled from Hive>Configs tab
Antonenko Alexander created AMBARI-25421: Summary: HSI Start failing when enabled from Hive>Configs tab Key: AMBARI-25421 URL: https://issues.apache.org/jira/browse/AMBARI-25421 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander Fix For: 2.7.5 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-25153) Ambari 2.7.3 web hangs at first step installation wizard
[ https://issues.apache.org/jira/browse/AMBARI-25153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978399#comment-16978399 ] Antonenko Alexander commented on AMBARI-25153: -- Committed to branch-2.7 > Ambari 2.7.3 web hangs at first step installation wizard > > > Key: AMBARI-25153 > URL: https://issues.apache.org/jira/browse/AMBARI-25153 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Anh >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Attachments: 92571-ambari-error1.png, RDw4k.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > > I installed 2.7.3 following the instructions from: > [https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.3] > After a long process I managed to complete the installation and start both > services successfully: "ambari-server" and "ambari-agent" > Now I am stuck on the install wizard in the fisrt step without getting any > error or any progress. That is, after hitting "Next" it never gets to step 2. > (see picture) [screenshot showing the > issue|https://i.stack.imgur.com/RDw4k.png] Things done so far to try to work > this around: > * restarting services (several times) > * ambari-server upgrade (once more) > * trying with chrome and IE > * looking at the log files of ambari-server and ambari-agent > ...but without success. Has anybody come across the same issue? Any clues? > Here's a picture of the console in Firefox (I get the same in chrome) > Thanks for your help! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25153) Ambari 2.7.3 web hangs at first step installation wizard
[ https://issues.apache.org/jira/browse/AMBARI-25153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25153: - Resolution: Fixed Status: Resolved (was: Patch Available) > Ambari 2.7.3 web hangs at first step installation wizard > > > Key: AMBARI-25153 > URL: https://issues.apache.org/jira/browse/AMBARI-25153 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Anh >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Attachments: 92571-ambari-error1.png, RDw4k.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > > I installed 2.7.3 following the instructions from: > [https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.3] > After a long process I managed to complete the installation and start both > services successfully: "ambari-server" and "ambari-agent" > Now I am stuck on the install wizard in the fisrt step without getting any > error or any progress. That is, after hitting "Next" it never gets to step 2. > (see picture) [screenshot showing the > issue|https://i.stack.imgur.com/RDw4k.png] Things done so far to try to work > this around: > * restarting services (several times) > * ambari-server upgrade (once more) > * trying with chrome and IE > * looking at the log files of ambari-server and ambari-agent > ...but without success. Has anybody come across the same issue? Any clues? > Here's a picture of the console in Firefox (I get the same in chrome) > Thanks for your help! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AMBARI-25419) Add option to disable URL credential auto-update behaviour
[ https://issues.apache.org/jira/browse/AMBARI-25419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978397#comment-16978397 ] Antonenko Alexander commented on AMBARI-25419: -- Committed to branch-2.7 > Add option to disable URL credential auto-update behaviour > -- > > Key: AMBARI-25419 > URL: https://issues.apache.org/jira/browse/AMBARI-25419 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > This is to enable customers using different auth credentials for different > repos (mixed OS). The use-case currently unlikely, it is only to prevent > later patches around this behaviour. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (AMBARI-25419) Add option to disable URL credential auto-update behaviour
[ https://issues.apache.org/jira/browse/AMBARI-25419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander resolved AMBARI-25419. -- Resolution: Fixed > Add option to disable URL credential auto-update behaviour > -- > > Key: AMBARI-25419 > URL: https://issues.apache.org/jira/browse/AMBARI-25419 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > This is to enable customers using different auth credentials for different > repos (mixed OS). The use-case currently unlikely, it is only to prevent > later patches around this behaviour. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25419) Add option to disable URL credential auto-update behaviour
[ https://issues.apache.org/jira/browse/AMBARI-25419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25419: - Summary: Add option to disable URL credential auto-update behaviour (was: Add option to disable URL credential auto-update behaviou) > Add option to disable URL credential auto-update behaviour > -- > > Key: AMBARI-25419 > URL: https://issues.apache.org/jira/browse/AMBARI-25419 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > > This is to enable customers using different auth credentials for different > repos (mixed OS). The use-case currently unlikely, it is only to prevent > later patches around this behaviour. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25419) Add option to disable URL credential auto-update behaviou
[ https://issues.apache.org/jira/browse/AMBARI-25419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25419: Assignee: Antonenko Alexander > Add option to disable URL credential auto-update behaviou > - > > Key: AMBARI-25419 > URL: https://issues.apache.org/jira/browse/AMBARI-25419 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > > This is to enable customers using different auth credentials for different > repos (mixed OS). The use-case currently unlikely, it is only to prevent > later patches around this behaviour. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25419) Add option to disable URL credential auto-update behaviou
Antonenko Alexander created AMBARI-25419: Summary: Add option to disable URL credential auto-update behaviou Key: AMBARI-25419 URL: https://issues.apache.org/jira/browse/AMBARI-25419 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander This is to enable customers using different auth credentials for different repos (mixed OS). The use-case currently unlikely, it is only to prevent later patches around this behaviour. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25153) Ambari 2.7.3 web hangs at first step installation wizard
[ https://issues.apache.org/jira/browse/AMBARI-25153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25153: - Status: Patch Available (was: Open) > Ambari 2.7.3 web hangs at first step installation wizard > > > Key: AMBARI-25153 > URL: https://issues.apache.org/jira/browse/AMBARI-25153 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Anh >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Attachments: 92571-ambari-error1.png, RDw4k.png > > Time Spent: 10m > Remaining Estimate: 0h > > I installed 2.7.3 following the instructions from: > [https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.3] > After a long process I managed to complete the installation and start both > services successfully: "ambari-server" and "ambari-agent" > Now I am stuck on the install wizard in the fisrt step without getting any > error or any progress. That is, after hitting "Next" it never gets to step 2. > (see picture) [screenshot showing the > issue|https://i.stack.imgur.com/RDw4k.png] Things done so far to try to work > this around: > * restarting services (several times) > * ambari-server upgrade (once more) > * trying with chrome and IE > * looking at the log files of ambari-server and ambari-agent > ...but without success. Has anybody come across the same issue? Any clues? > Here's a picture of the console in Firefox (I get the same in chrome) > Thanks for your help! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25412) Remove all tags from logger service methods in ambari-contrib
[ https://issues.apache.org/jira/browse/AMBARI-25412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25412: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.7 > Remove all tags from logger service methods in ambari-contrib > - > > Key: AMBARI-25412 > URL: https://issues.apache.org/jira/browse/AMBARI-25412 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Supporting tags inject was removed in AMBARI-25384 due to XSS. We need to > stop to using tags inside logger service -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25412) Remove all tags from logger service methods in ambari-contrib
[ https://issues.apache.org/jira/browse/AMBARI-25412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25412: - Status: Patch Available (was: Open) > Remove all tags from logger service methods in ambari-contrib > - > > Key: AMBARI-25412 > URL: https://issues.apache.org/jira/browse/AMBARI-25412 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > Supporting tags inject was removed in AMBARI-25384 due to XSS. We need to > stop to using tags inside logger service -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25412) Remove all tags from logger service methods in ambari-contrib
[ https://issues.apache.org/jira/browse/AMBARI-25412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25412: Assignee: Antonenko Alexander > Remove all tags from logger service methods in ambari-contrib > - > > Key: AMBARI-25412 > URL: https://issues.apache.org/jira/browse/AMBARI-25412 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.5 > > Time Spent: 10m > Remaining Estimate: 0h > > Supporting tags inject was removed in AMBARI-25384 due to XSS. We need to > stop to using tags inside logger service -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25412) Remove all tags from logger service methods in ambari-contrib
Antonenko Alexander created AMBARI-25412: Summary: Remove all tags from logger service methods in ambari-contrib Key: AMBARI-25412 URL: https://issues.apache.org/jira/browse/AMBARI-25412 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander Fix For: 2.7.5 Supporting tags inject was removed in AMBARI-25384 due to XSS. We need to stop to using tags inside logger service -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25153) Ambari 2.7.3 web hangs at first step installation wizard
[ https://issues.apache.org/jira/browse/AMBARI-25153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25153: Assignee: Antonenko Alexander (was: Éberhardt Péter) > Ambari 2.7.3 web hangs at first step installation wizard > > > Key: AMBARI-25153 > URL: https://issues.apache.org/jira/browse/AMBARI-25153 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.3 >Reporter: Anh >Assignee: Antonenko Alexander >Priority: Blocker > Attachments: 92571-ambari-error1.png, RDw4k.png > > > I installed 2.7.3 following the instructions from: > [https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.3] > After a long process I managed to complete the installation and start both > services successfully: "ambari-server" and "ambari-agent" > Now I am stuck on the install wizard in the fisrt step without getting any > error or any progress. That is, after hitting "Next" it never gets to step 2. > (see picture) [screenshot showing the > issue|https://i.stack.imgur.com/RDw4k.png] Things done so far to try to work > this around: > * restarting services (several times) > * ambari-server upgrade (once more) > * trying with chrome and IE > * looking at the log files of ambari-server and ambari-agent > ...but without success. Has anybody come across the same issue? Any clues? > Here's a picture of the console in Firefox (I get the same in chrome) > Thanks for your help! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25410) Add autocomplete for all repos url for login and password
[ https://issues.apache.org/jira/browse/AMBARI-25410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25410: - Description: When user put his credentials for first or any links we need automatically to add them in every link field. If he will edit these credentials in any of existing fields - it should be updated everywhere We need to do this in ambari wizard and ambari-admin was: For paywall we need to add autocomplete logic: When user put his credentials for first or any links we need automatically to add them in every link field. If he will edit these credentials in any of existing fields - it should be updated everywhere We need to do this in ambari wizard and ambari-admin > Add autocomplete for all repos url for login and password > - > > Key: AMBARI-25410 > URL: https://issues.apache.org/jira/browse/AMBARI-25410 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > > When user put his credentials for first or any links we need automatically to > add them in every link field. > If he will edit these credentials in any of existing fields - it should be > updated everywhere > We need to do this in ambari wizard and ambari-admin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25410) Add autocomplete for all repos url for login and password
[ https://issues.apache.org/jira/browse/AMBARI-25410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25410: Assignee: Antonenko Alexander > Add autocomplete for all repos url for login and password > - > > Key: AMBARI-25410 > URL: https://issues.apache.org/jira/browse/AMBARI-25410 > Project: Ambari > Issue Type: Task > Components: ambari-admin, ambari-web >Affects Versions: 2.7.5 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > > For paywall we need to add autocomplete logic: > When user put his credentials for first or any links we need automatically to > add them in every link field. > If he will edit these credentials in any of existing fields - it should be > updated everywhere > We need to do this in ambari wizard and ambari-admin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25410) Add autocomplete for all repos url for login and password
Antonenko Alexander created AMBARI-25410: Summary: Add autocomplete for all repos url for login and password Key: AMBARI-25410 URL: https://issues.apache.org/jira/browse/AMBARI-25410 Project: Ambari Issue Type: Task Components: ambari-admin, ambari-web Affects Versions: 2.7.5 Reporter: Antonenko Alexander For paywall we need to add autocomplete logic: When user put his credentials for first or any links we need automatically to add them in every link field. If he will edit these credentials in any of existing fields - it should be updated everywhere We need to do this in ambari wizard and ambari-admin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25395) Update help text in Hive install provide a clearly formatted example
[ https://issues.apache.org/jira/browse/AMBARI-25395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25395: - Status: Patch Available (was: Open) > Update help text in Hive install provide a clearly formatted example > > > Key: AMBARI-25395 > URL: https://issues.apache.org/jira/browse/AMBARI-25395 > Project: Ambari > Issue Type: Task >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Update the help text displayed in Ambari during the Hive service install so > that there is a clearly labeled/formatted example of the download and/or an > accurate JAR filename example. The text as displayed presents > com.mysql.jdbc.driver as if it was a JAR file name, which may confuse some > users. (screenshot attached) > Provide a monospaced example ambari-server-setup command, such as in the > documentation here: > ambari-server setup --jdbc-db=mysql > --jdbc-driver=/path/to/mysql/mysql-connector-java.jar -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (AMBARI-25395) Update help text in Hive install provide a clearly formatted example
[ https://issues.apache.org/jira/browse/AMBARI-25395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25395: Assignee: Antonenko Alexander > Update help text in Hive install provide a clearly formatted example > > > Key: AMBARI-25395 > URL: https://issues.apache.org/jira/browse/AMBARI-25395 > Project: Ambari > Issue Type: Task >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > > Update the help text displayed in Ambari during the Hive service install so > that there is a clearly labeled/formatted example of the download and/or an > accurate JAR filename example. The text as displayed presents > com.mysql.jdbc.driver as if it was a JAR file name, which may confuse some > users. (screenshot attached) > Provide a monospaced example ambari-server-setup command, such as in the > documentation here: > ambari-server setup --jdbc-db=mysql > --jdbc-driver=/path/to/mysql/mysql-connector-java.jar -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (AMBARI-25395) Update help text in Hive install provide a clearly formatted example
Antonenko Alexander created AMBARI-25395: Summary: Update help text in Hive install provide a clearly formatted example Key: AMBARI-25395 URL: https://issues.apache.org/jira/browse/AMBARI-25395 Project: Ambari Issue Type: Task Reporter: Antonenko Alexander Update the help text displayed in Ambari during the Hive service install so that there is a clearly labeled/formatted example of the download and/or an accurate JAR filename example. The text as displayed presents com.mysql.jdbc.driver as if it was a JAR file name, which may confuse some users. (screenshot attached) Provide a monospaced example ambari-server-setup command, such as in the documentation here: ambari-server setup --jdbc-db=mysql --jdbc-driver=/path/to/mysql/mysql-connector-java.jar -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (AMBARI-25214) Moving resource manager does not update yarn.resourcemanager.address property
[
https://issues.apache.org/jira/browse/AMBARI-25214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-25214:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Moving resource manager does not update yarn.resourcemanager.address property
> -
>
> Key: AMBARI-25214
> URL: https://issues.apache.org/jira/browse/AMBARI-25214
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.3
>Reporter: Balázs Bence Sári
>Assignee: Antonenko Alexander
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.4
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When Resource Manager is move in a Yarn HA cluster (maybe without HA too),
> the *yarn.resourcemanager.address.* property is not updated unlike
> others (e.g. *yarn.resourcemanager.hostname.* or
> *yarn.resourcemanager.webapp.address.*).
> As a result, the moved resource manager stops after a while with an execption
> in the log:
> {code}
> org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Invalid
> configuration! Can not find valid RM_HA_ID. None of
> yarn.resourcemanager.address.rm1 yarn.resourcemanager.address.rm2 are
> matching the local address OR yarn.resourcemanager.ha.id is not specified in
> HA Configuration
> at
> org.apache.hadoop.yarn.conf.HAUtil.throwBadConfigurationException(HAUtil.java:45)
> at
> org.apache.hadoop.yarn.conf.HAUtil.verifyAndSetCurrentRMHAId(HAUtil.java:151)
> at
> org.apache.hadoop.yarn.conf.HAUtil.verifyAndSetConfiguration(HAUtil.java:106)
> at
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.serviceInit(ResourceManager.java:276)
> at
> org.apache.hadoop.service.AbstractService.init(AbstractService.java:164)
> at
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.main(ResourceManager.java:1512)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (AMBARI-25374) Use host names instead ip addresses while checking hive interactive service status if new hive.server2.leadertest.use.ip is false
[ https://issues.apache.org/jira/browse/AMBARI-25374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25374: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch 2.7 > Use host names instead ip addresses while checking hive interactive service > status if new hive.server2.leadertest.use.ip is false > -- > > Key: AMBARI-25374 > URL: https://issues.apache.org/jira/browse/AMBARI-25374 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > Add logic: > * if hive.server2.webui.use.ssl is true we should use https > * add new property hive.server2.leadertest.use.ip and set it to true by > default > * if hive.server2.leadertest.use.ip is false we sould use host names is url -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (AMBARI-25374) Use host names instead ip addresses while checking hive interactive service status if new hive.server2.leadertest.use.ip is false
[ https://issues.apache.org/jira/browse/AMBARI-25374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25374: - Description: Add logic: * if hive.server2.webui.use.ssl is true we should use https * add new property hive.server2.leadertest.use.ip and set it to true by default * if hive.server2.leadertest.use.ip is false we sould use host names is url > Use host names instead ip addresses while checking hive interactive service > status if new hive.server2.leadertest.use.ip is false > -- > > Key: AMBARI-25374 > URL: https://issues.apache.org/jira/browse/AMBARI-25374 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Add logic: > * if hive.server2.webui.use.ssl is true we should use https > * add new property hive.server2.leadertest.use.ip and set it to true by > default > * if hive.server2.leadertest.use.ip is false we sould use host names is url -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (AMBARI-25374) Use host names instead ip addresses while checking hive interactive service status if new hive.server2.leadertest.use.ip is false
[ https://issues.apache.org/jira/browse/AMBARI-25374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25374: - Summary: Use host names instead ip addresses while checking hive interactive service status if new hive.server2.leadertest.use.ip is false (was: Use host names instead ip addresses while checking hive interactive service status) > Use host names instead ip addresses while checking hive interactive service > status if new hive.server2.leadertest.use.ip is false > -- > > Key: AMBARI-25374 > URL: https://issues.apache.org/jira/browse/AMBARI-25374 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (AMBARI-25374) Use host names instead ip addresses while checking hive interactive service status
[ https://issues.apache.org/jira/browse/AMBARI-25374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25374: - Status: Patch Available (was: Open) > Use host names instead ip addresses while checking hive interactive service > status > --- > > Key: AMBARI-25374 > URL: https://issues.apache.org/jira/browse/AMBARI-25374 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (AMBARI-25374) Use host names instead ip addresses while checking hive interactive service status
[ https://issues.apache.org/jira/browse/AMBARI-25374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25374: - Summary: Use host names instead ip addresses while checking hive interactive service status (was: Cloudbreak gives fatal error when create cluster is configured for mysql external datasource) > Use host names instead ip addresses while checking hive interactive service > status > --- > > Key: AMBARI-25374 > URL: https://issues.apache.org/jira/browse/AMBARI-25374 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (AMBARI-25374) Cloudbreak gives fatal error when create cluster is configured for mysql external datasource
[ https://issues.apache.org/jira/browse/AMBARI-25374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25374: Assignee: Antonenko Alexander > Cloudbreak gives fatal error when create cluster is configured for mysql > external datasource > > > Key: AMBARI-25374 > URL: https://issues.apache.org/jira/browse/AMBARI-25374 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.3 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (AMBARI-25374) Cloudbreak gives fatal error when create cluster is configured for mysql external datasource
Antonenko Alexander created AMBARI-25374: Summary: Cloudbreak gives fatal error when create cluster is configured for mysql external datasource Key: AMBARI-25374 URL: https://issues.apache.org/jira/browse/AMBARI-25374 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.3 Reporter: Antonenko Alexander -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (AMBARI-25367) backport of Heatmap Data Issues
[ https://issues.apache.org/jira/browse/AMBARI-25367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25367: Assignee: Antonenko Alexander > backport of Heatmap Data Issues > --- > > Key: AMBARI-25367 > URL: https://issues.apache.org/jira/browse/AMBARI-25367 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.6.0 > > > "Data Not Available" in Dashboard / Heatmap for: > * Host Disk Space Used % > * Host Memory Used % > "Invalid Data" in Dashboard / Heatmap for: > * DataNode Process Disk I/O Utilization > * DataNode Process Network I/O Utilization > These should all be reporting data. > STR: > - Install ZooKeeper, HDFS, AMS, SmartSense > - Wait a 10 minutes to ensure data is coming into AMS > - Click on Dashboard / Heatmap and view these metrics -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (AMBARI-25367) backport of Heatmap Data Issues
Antonenko Alexander created AMBARI-25367: Summary: backport of Heatmap Data Issues Key: AMBARI-25367 URL: https://issues.apache.org/jira/browse/AMBARI-25367 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.6.0 Reporter: Antonenko Alexander Fix For: 2.6.0 "Data Not Available" in Dashboard / Heatmap for: * Host Disk Space Used % * Host Memory Used % "Invalid Data" in Dashboard / Heatmap for: * DataNode Process Disk I/O Utilization * DataNode Process Network I/O Utilization These should all be reporting data. STR: - Install ZooKeeper, HDFS, AMS, SmartSense - Wait a 10 minutes to ensure data is coming into AMS - Click on Dashboard / Heatmap and view these metrics -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (AMBARI-25329) Ambari breadcrumbs xss vulnerability
[
https://issues.apache.org/jira/browse/AMBARI-25329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-25329:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari breadcrumbs xss vulnerability
>
>
> Key: AMBARI-25329
> URL: https://issues.apache.org/jira/browse/AMBARI-25329
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.7.4
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.4
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Special characters should be encoded when displayed in Ambari Views.
> If special characters are not encoded, then scripts
> ({{alert("xss!")}}) may be executed due to user input. For
> example, issues may occur by placing special character in the Display Name
> field of an Ambari View.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-25329) Ambari breadcrumbs xss vulnerability
[
https://issues.apache.org/jira/browse/AMBARI-25329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-25329:
-
Status: Patch Available (was: Open)
> Ambari breadcrumbs xss vulnerability
>
>
> Key: AMBARI-25329
> URL: https://issues.apache.org/jira/browse/AMBARI-25329
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.7.4
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.4
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Special characters should be encoded when displayed in Ambari Views.
> If special characters are not encoded, then scripts
> ({{alert("xss!")}}) may be executed due to user input. For
> example, issues may occur by placing special character in the Display Name
> field of an Ambari View.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-25329) Ambari breadcrumbs xss vulnerability
[
https://issues.apache.org/jira/browse/AMBARI-25329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander reassigned AMBARI-25329:
Assignee: Antonenko Alexander
> Ambari breadcrumbs xss vulnerability
>
>
> Key: AMBARI-25329
> URL: https://issues.apache.org/jira/browse/AMBARI-25329
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.7.4
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Blocker
> Fix For: 2.7.4
>
>
> Special characters should be encoded when displayed in Ambari Views.
> If special characters are not encoded, then scripts
> ({{alert("xss!")}}) may be executed due to user input. For
> example, issues may occur by placing special character in the Display Name
> field of an Ambari View.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-25329) Ambari breadcrumbs xss vulnerability
Antonenko Alexander created AMBARI-25329:
Summary: Ambari breadcrumbs xss vulnerability
Key: AMBARI-25329
URL: https://issues.apache.org/jira/browse/AMBARI-25329
Project: Ambari
Issue Type: Task
Components: ambari-web
Affects Versions: 2.7.4
Reporter: Antonenko Alexander
Fix For: 2.7.4
Special characters should be encoded when displayed in Ambari Views.
If special characters are not encoded, then scripts
({{alert("xss!")}}) may be executed due to user input. For
example, issues may occur by placing special character in the Display Name
field of an Ambari View.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-25318) Regenerate Key tabs action is missing from Service Action list
[ https://issues.apache.org/jira/browse/AMBARI-25318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869544#comment-16869544 ] Antonenko Alexander commented on AMBARI-25318: -- Committed to branch-2.7 > Regenerate Key tabs action is missing from Service Action list > -- > > Key: AMBARI-25318 > URL: https://issues.apache.org/jira/browse/AMBARI-25318 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.4 > > Time Spent: 50m > Remaining Estimate: 0h > > Action is missing even if not manual kerberos is enabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25318) Regenerate Key tabs action is missing from Service Action list
[ https://issues.apache.org/jira/browse/AMBARI-25318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25318: - Resolution: Fixed Status: Resolved (was: Patch Available) > Regenerate Key tabs action is missing from Service Action list > -- > > Key: AMBARI-25318 > URL: https://issues.apache.org/jira/browse/AMBARI-25318 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.4 > > Time Spent: 50m > Remaining Estimate: 0h > > Action is missing even if not manual kerberos is enabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-25318) Regenerate Key tabs action is missing from Service Action list
[ https://issues.apache.org/jira/browse/AMBARI-25318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-25318: - Status: Patch Available (was: Open) > Regenerate Key tabs action is missing from Service Action list > -- > > Key: AMBARI-25318 > URL: https://issues.apache.org/jira/browse/AMBARI-25318 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.4 > > Time Spent: 10m > Remaining Estimate: 0h > > Action is missing even if not manual kerberos is enabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-25318) Regenerate Key tabs action is missing from Service Action list
[ https://issues.apache.org/jira/browse/AMBARI-25318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-25318: Assignee: Antonenko Alexander > Regenerate Key tabs action is missing from Service Action list > -- > > Key: AMBARI-25318 > URL: https://issues.apache.org/jira/browse/AMBARI-25318 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.4 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.4 > > > Action is missing even if not manual kerberos is enabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-25318) Regenerate Key tabs action is missing from Service Action list
Antonenko Alexander created AMBARI-25318: Summary: Regenerate Key tabs action is missing from Service Action list Key: AMBARI-25318 URL: https://issues.apache.org/jira/browse/AMBARI-25318 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.4 Reporter: Antonenko Alexander Fix For: 2.7.4 Action is missing even if not manual kerberos is enabled -- This message was sent by Atlassian JIRA (v7.6.3#76005)
