[jira] [Commented] (AMBARI-15488) Text field is displayed instead of Hive default query queue dropdown
[ https://issues.apache.org/jira/browse/AMBARI-15488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204344#comment-15204344 ] Aleksandr Kovalenko commented on AMBARI-15488: -- +1 for the patch > Text field is displayed instead of Hive default query queue dropdown > > > Key: AMBARI-15488 > URL: https://issues.apache.org/jira/browse/AMBARI-15488 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.1.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15488.patch, CustomizeServices.png > > > The combo box with queue names does not show up the first time visiting > Configs section for installed cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15517) Improve config groups loading on wizard (part 1)
[ https://issues.apache.org/jira/browse/AMBARI-15517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206685#comment-15206685 ] Aleksandr Kovalenko commented on AMBARI-15517: -- +1 for the patch > Improve config groups loading on wizard (part 1) > > > Key: AMBARI-15517 > URL: https://issues.apache.org/jira/browse/AMBARI-15517 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-15517.patch > > > Simplify logic for adding saved overrides to configs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15532) ambari-web allows to delete a service that has running processes
[ https://issues.apache.org/jira/browse/AMBARI-15532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208448#comment-15208448 ] Aleksandr Kovalenko commented on AMBARI-15532: -- +1 for the patch > ambari-web allows to delete a service that has running processes > > > Key: AMBARI-15532 > URL: https://issues.apache.org/jira/browse/AMBARI-15532 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15532.patch > > > # Navigate to Hive Service summary page > # Stop Webhcat server > # Delete Hive Service > *Actual behavior:* As one master component of Hive is in installed state > which brings hive service in installed state, ambari-web considers this to be > a valid siatuation and executes delete API call on Hive service resource > *Expected behavior:* Instead of relying on service state, state of all master > and slave component of a service should be checked and if any of them is in > started state then user should be asked to stop the master component first. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15559) Cover services views with unit tests
[ https://issues.apache.org/jira/browse/AMBARI-15559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210418#comment-15210418 ] Aleksandr Kovalenko commented on AMBARI-15559: -- +1 for the patch > Cover services views with unit tests > > > Key: AMBARI-15559 > URL: https://issues.apache.org/jira/browse/AMBARI-15559 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-15559.patch > > > Cover following files with unit tests: > * ambari-web/app/views/main/service/services/hdfs > * ambari-web/app/views/main/service/services/yarn > * ambari-web/app/views/main/service/services/hive > * ambari-web/app/views/main/service/services/oozie > * ambari-web/app/views/main/service/services/hbase > * ambari-web/app/views/main/service/services/storm > * ambari-web/app/views/main/service/services/mapreduce2 > * ambari-web/app/views/main/service/services/flume -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15562) Result of service deletion action is not known until user does browser refresh
[ https://issues.apache.org/jira/browse/AMBARI-15562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210462#comment-15210462 ] Aleksandr Kovalenko commented on AMBARI-15562: -- +1 for the patch > Result of service deletion action is not known until user does browser refresh > -- > > Key: AMBARI-15562 > URL: https://issues.apache.org/jira/browse/AMBARI-15562 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15562.patch > > > We should display a positive/negative confirmation after the service deletion > is confirmed via the API. Once the user clicks OK, force a page refresh. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15584) Need warning pop-up for not installing SmartSense
[ https://issues.apache.org/jira/browse/AMBARI-15584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211735#comment-15211735 ] Aleksandr Kovalenko commented on AMBARI-15584: -- +1 for the patch > Need warning pop-up for not installing SmartSense > - > > Key: AMBARI-15584 > URL: https://issues.apache.org/jira/browse/AMBARI-15584 > Project: Ambari > Issue Type: Improvement > Components: ambari-web >Affects Versions: 2.2.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-15584.patch > > > Just like AMS, we'd like a pop-up to be displayed if the user does not choose > SmartSense from the list of services during installation. > *Limited Functionality Warning* > SmartSense securely collections diagnostic data from the cluster and provides > both recommendations as well as automated analysis for troubleshooting > support cases. If you do not install the SmartSense service, no > recommendations will be provided and data must be gathered manually for > troubleshooting support cases. Are you sure you want to proceed without > SmartSense? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15601: - Description: *STR:* # On Nn ha environment, nn1 is on host1 and nn2 is on host2 # Put host1 in maintenance mode # Start "Move namenode wizard" # Wizard will fail on last step "Delete disabled namenode+zkfc" because the namenode to be deleted which was in maintenace mode never stopped as part of wizard, and delete operation on a component in 'STARTED' state throws an exception # user ends up with 3 instances of namenode. It is reasonable to expect that the source host is in maintenance mode (the user is likely doing a move because the host is in bad state). was: *STR:* # On Nn ha environment, nn1 is on host1 and nn2 is on host2 # Put host1 in maintenance mode # Start "Move namenode wizard" # Wizard will fail on last step "Delete disabled namenode+zkfc" because the namenode to be deleted which was in maintenace mode never stopped as part of wizard, and delete operation on a component in 'STARTED' state throws an exception # user ends up with 3 instances of namenode. It is reasonable to expect that the source host is in maintenance mode (the user is likely doing a move because the host is in bad state). All move wizards should tolerate the source host being in maintenance mode and just work. > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
Aleksandr Kovalenko created AMBARI-15601: Summary: HA Namenode Move failed on Delete disabled NameNode+ZKFC stage Key: AMBARI-15601 URL: https://issues.apache.org/jira/browse/AMBARI-15601 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 2.2.2 *STR:* # On Nn ha environment, nn1 is on host1 and nn2 is on host2 # Put host1 in maintenance mode # Start "Move namenode wizard" # Wizard will fail on last step "Delete disabled namenode+zkfc" because the namenode to be deleted which was in maintenace mode never stopped as part of wizard, and delete operation on a component in 'STARTED' state throws an exception # user ends up with 3 instances of namenode. It is reasonable to expect that the source host is in maintenance mode (the user is likely doing a move because the host is in bad state). All move wizards should tolerate the source host being in maintenance mode and just work. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15601: - Status: Patch Available (was: Open) > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214448#comment-15214448 ] Aleksandr Kovalenko commented on AMBARI-15601: -- 10487 tests complete (14 seconds) 121 tests pending > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15601: - Attachment: AMBARI-15601.patch > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15601: - Attachment: (was: AMBARI-15601.patch) > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601_branch-2.2.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15601: - Attachment: AMBARI-15601_branch-2.2.patch > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601_branch-2.2.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15601: - Attachment: AMBARI-15601.patch > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601.patch, AMBARI-15601_branch-2.2.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15601: - Attachment: AMBARI-15601_branch-2.2.patch > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601_branch-2.2.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15601: - Attachment: (was: AMBARI-15601_branch-2.2.patch) > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601_branch-2.2.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214944#comment-15214944 ] Aleksandr Kovalenko commented on AMBARI-15601: -- committed to trunk and branch-2.2 > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601.patch, AMBARI-15601_branch-2.2.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15601: - Resolution: Fixed Status: Resolved (was: Patch Available) > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601.patch, AMBARI-15601_branch-2.2.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15615) Populate property dfs.internal.nameservices when enabling NN HA
[ https://issues.apache.org/jira/browse/AMBARI-15615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216170#comment-15216170 ] Aleksandr Kovalenko commented on AMBARI-15615: -- +1 for the patch > Populate property dfs.internal.nameservices when enabling NN HA > --- > > Key: AMBARI-15615 > URL: https://issues.apache.org/jira/browse/AMBARI-15615 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15615.patch > > > NN HA wizard should add a new property dfs.internal.nameservices to hdfs-site > as part of enabling NN HA. This value should be the same as what is set for > dfs.nameservices. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15618) Remove "isHadoop22Stack" and "isHadoop20Stack" flags
[ https://issues.apache.org/jira/browse/AMBARI-15618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216268#comment-15216268 ] Aleksandr Kovalenko commented on AMBARI-15618: -- +1 for the patch > Remove "isHadoop22Stack" and "isHadoop20Stack" flags > > > Key: AMBARI-15618 > URL: https://issues.apache.org/jira/browse/AMBARI-15618 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-15618.patch > > > For Ambari version 2.4.0 the lowest stack version is 2.2, so we do not need > "isHadoop22Stack" and "isHadoop20Stack" any more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15619) UI - calculate RU/EU is paused by using "suspended" property
[ https://issues.apache.org/jira/browse/AMBARI-15619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216387#comment-15216387 ] Aleksandr Kovalenko commented on AMBARI-15619: -- +1 for the patch > UI - calculate RU/EU is paused by using "suspended" property > > > Key: AMBARI-15619 > URL: https://issues.apache.org/jira/browse/AMBARI-15619 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-15619.patch > > > A property called "suspended" were introduced for the "upgrade" resource. > Right now, the UI assumes that a status of "ABORTED" implies the upgrade is > suspended, and this is not necessarily the case. Instead, the UI should use > the "suspended" property, which is new in Ambari 2.4.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15632) Move wizard failed on Delete component operation if component is in MM
Aleksandr Kovalenko created AMBARI-15632: Summary: Move wizard failed on Delete component operation if component is in MM Key: AMBARI-15632 URL: https://issues.apache.org/jira/browse/AMBARI-15632 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.2.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15632) Move wizard failed on Delete component operation if component is in MM
[ https://issues.apache.org/jira/browse/AMBARI-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15632: - Description: On Move wizard for every component we have generic action of deleting host component from source host. For success delete operation host component should be in INSTALLED (stopped) state. But if source host is in maintenance mode some host level or service level operations may be ignored for host component (depending on maintenance mode level: host, service or component), so Stop All Services or Stop Service operations may be ignored by host components in MM, so delete operations for them will fail. We should add additional request to stop components in MM, that we want to delete. This jira should cover changes in Move Wizard for all movable components. > Move wizard failed on Delete component operation if component is in MM > -- > > Key: AMBARI-15632 > URL: https://issues.apache.org/jira/browse/AMBARI-15632 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.2.2 > > > On Move wizard for every component we have generic action of deleting host > component from source host. For success delete operation host component > should be in INSTALLED (stopped) state. But if source host is in maintenance > mode some host level or service level operations may be ignored for host > component (depending on maintenance mode level: host, service or component), > so Stop All Services or Stop Service operations may be ignored by host > components in MM, so delete operations for them will fail. We should add > additional request to stop components in MM, that we want to delete. > This jira should cover changes in Move Wizard for all movable components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15632) Move wizard failed on Delete component operation if component is in MM
[ https://issues.apache.org/jira/browse/AMBARI-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15632: - Attachment: AMBARI-15632_branch-2.2.patch > Move wizard failed on Delete component operation if component is in MM > -- > > Key: AMBARI-15632 > URL: https://issues.apache.org/jira/browse/AMBARI-15632 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.2.2 > > Attachments: AMBARI-15632_branch-2.2.patch > > > On Move wizard for every component we have generic action of deleting host > component from source host. For success delete operation host component > should be in INSTALLED (stopped) state. But if source host is in maintenance > mode some host level or service level operations may be ignored for host > component (depending on maintenance mode level: host, service or component), > so Stop All Services or Stop Service operations may be ignored by host > components in MM, so delete operations for them will fail. We should add > additional request to stop components in MM, that we want to delete. > This jira should cover changes in Move Wizard for all movable components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15632) Move wizard failed on Delete component operation if component is in MM
[ https://issues.apache.org/jira/browse/AMBARI-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218346#comment-15218346 ] Aleksandr Kovalenko commented on AMBARI-15632: -- 25623 tests complete (34 seconds) 154 tests pending > Move wizard failed on Delete component operation if component is in MM > -- > > Key: AMBARI-15632 > URL: https://issues.apache.org/jira/browse/AMBARI-15632 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.2.2 > > Attachments: AMBARI-15632_branch-2.2.patch > > > On Move wizard for every component we have generic action of deleting host > component from source host. For success delete operation host component > should be in INSTALLED (stopped) state. But if source host is in maintenance > mode some host level or service level operations may be ignored for host > component (depending on maintenance mode level: host, service or component), > so Stop All Services or Stop Service operations may be ignored by host > components in MM, so delete operations for them will fail. We should add > additional request to stop components in MM, that we want to delete. > This jira should cover changes in Move Wizard for all movable components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15632) Move wizard failed on Delete component operation if component is in MM
[ https://issues.apache.org/jira/browse/AMBARI-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15632: - Status: Patch Available (was: Open) > Move wizard failed on Delete component operation if component is in MM > -- > > Key: AMBARI-15632 > URL: https://issues.apache.org/jira/browse/AMBARI-15632 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.2.2 > > Attachments: AMBARI-15632.patch, AMBARI-15632_branch-2.2.patch > > > On Move wizard for every component we have generic action of deleting host > component from source host. For success delete operation host component > should be in INSTALLED (stopped) state. But if source host is in maintenance > mode some host level or service level operations may be ignored for host > component (depending on maintenance mode level: host, service or component), > so Stop All Services or Stop Service operations may be ignored by host > components in MM, so delete operations for them will fail. We should add > additional request to stop components in MM, that we want to delete. > This jira should cover changes in Move Wizard for all movable components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15632) Move wizard failed on Delete component operation if component is in MM
[ https://issues.apache.org/jira/browse/AMBARI-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15632: - Attachment: AMBARI-15632.patch > Move wizard failed on Delete component operation if component is in MM > -- > > Key: AMBARI-15632 > URL: https://issues.apache.org/jira/browse/AMBARI-15632 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.2.2 > > Attachments: AMBARI-15632.patch, AMBARI-15632_branch-2.2.patch > > > On Move wizard for every component we have generic action of deleting host > component from source host. For success delete operation host component > should be in INSTALLED (stopped) state. But if source host is in maintenance > mode some host level or service level operations may be ignored for host > component (depending on maintenance mode level: host, service or component), > so Stop All Services or Stop Service operations may be ignored by host > components in MM, so delete operations for them will fail. We should add > additional request to stop components in MM, that we want to delete. > This jira should cover changes in Move Wizard for all movable components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15634) UI gets stuck on login
[ https://issues.apache.org/jira/browse/AMBARI-15634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218579#comment-15218579 ] Aleksandr Kovalenko commented on AMBARI-15634: -- +1 for the patch > UI gets stuck on login > -- > > Key: AMBARI-15634 > URL: https://issues.apache.org/jira/browse/AMBARI-15634 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15634.patch > > > User is unable to proceed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15632) Move wizard failed on Delete component operation if component is in MM
[ https://issues.apache.org/jira/browse/AMBARI-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218587#comment-15218587 ] Aleksandr Kovalenko commented on AMBARI-15632: -- committed to trunk and branch-2.2 > Move wizard failed on Delete component operation if component is in MM > -- > > Key: AMBARI-15632 > URL: https://issues.apache.org/jira/browse/AMBARI-15632 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.2.2 > > Attachments: AMBARI-15632.patch, AMBARI-15632_branch-2.2.patch > > > On Move wizard for every component we have generic action of deleting host > component from source host. For success delete operation host component > should be in INSTALLED (stopped) state. But if source host is in maintenance > mode some host level or service level operations may be ignored for host > component (depending on maintenance mode level: host, service or component), > so Stop All Services or Stop Service operations may be ignored by host > components in MM, so delete operations for them will fail. We should add > additional request to stop components in MM, that we want to delete. > This jira should cover changes in Move Wizard for all movable components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15601) HA Namenode Move failed on Delete disabled NameNode+ZKFC stage
[ https://issues.apache.org/jira/browse/AMBARI-15601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218591#comment-15218591 ] Aleksandr Kovalenko commented on AMBARI-15601: -- branch-2.2 local UT results after applying patch: 10488 tests complete (13 seconds) 121 tests pending trunk local UT results after applying patch: 25623 tests complete (34 seconds) 154 tests pending > HA Namenode Move failed on Delete disabled NameNode+ZKFC stage > -- > > Key: AMBARI-15601 > URL: https://issues.apache.org/jira/browse/AMBARI-15601 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15601.patch, AMBARI-15601_branch-2.2.patch > > > *STR:* > # On Nn ha environment, nn1 is on host1 and nn2 is on host2 > # Put host1 in maintenance mode > # Start "Move namenode wizard" > # Wizard will fail on last step "Delete disabled namenode+zkfc" because the > namenode to be deleted which was in maintenace mode never stopped as part of > wizard, and delete operation on a component in 'STARTED' state throws an > exception > # user ends up with 3 instances of namenode. > It is reasonable to expect that the source host is in maintenance mode (the > user is likely doing a move because the host is in bad state). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15632) Move wizard failed on Delete component operation if component is in MM
[ https://issues.apache.org/jira/browse/AMBARI-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218593#comment-15218593 ] Aleksandr Kovalenko commented on AMBARI-15632: -- branch-2.2 local UT results after applying patch: 10488 tests complete (13 seconds) 121 tests pending trunk local UT results after applying patch: 25623 tests complete (34 seconds) 154 tests pending > Move wizard failed on Delete component operation if component is in MM > -- > > Key: AMBARI-15632 > URL: https://issues.apache.org/jira/browse/AMBARI-15632 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.2.2 > > Attachments: AMBARI-15632.patch, AMBARI-15632_branch-2.2.patch > > > On Move wizard for every component we have generic action of deleting host > component from source host. For success delete operation host component > should be in INSTALLED (stopped) state. But if source host is in maintenance > mode some host level or service level operations may be ignored for host > component (depending on maintenance mode level: host, service or component), > so Stop All Services or Stop Service operations may be ignored by host > components in MM, so delete operations for them will fail. We should add > additional request to stop components in MM, that we want to delete. > This jira should cover changes in Move Wizard for all movable components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15632) Move wizard failed on Delete component operation if component is in MM
[ https://issues.apache.org/jira/browse/AMBARI-15632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15632: - Resolution: Fixed Status: Resolved (was: Patch Available) > Move wizard failed on Delete component operation if component is in MM > -- > > Key: AMBARI-15632 > URL: https://issues.apache.org/jira/browse/AMBARI-15632 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.2.2 > > Attachments: AMBARI-15632.patch, AMBARI-15632_branch-2.2.patch > > > On Move wizard for every component we have generic action of deleting host > component from source host. For success delete operation host component > should be in INSTALLED (stopped) state. But if source host is in maintenance > mode some host level or service level operations may be ignored for host > component (depending on maintenance mode level: host, service or component), > so Stop All Services or Stop Service operations may be ignored by host > components in MM, so delete operations for them will fail. We should add > additional request to stop components in MM, that we want to delete. > This jira should cover changes in Move Wizard for all movable components. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15389) Intermittent YARN service check failures during and post EU
[
https://issues.apache.org/jira/browse/AMBARI-15389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219940#comment-15219940
]
Aleksandr Kovalenko commented on AMBARI-15389:
--
+1 for patches
> Intermittent YARN service check failures during and post EU
> ---
>
> Key: AMBARI-15389
> URL: https://issues.apache.org/jira/browse/AMBARI-15389
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Dmitry Lysnichenko
>Assignee: Antonenko Alexander
> Fix For: 2.2.2
>
> Attachments: AMBARI-15389.patch, AMBARI-15389.patch,
> AMBARI-15389_2.2.patch
>
>
> Build # - Ambari 2.2.1.1 - #63
> Observed this issue in a couple of EU runs recently where YARN service check
> reports failure
> a. In one test, the EU ran from HDP 2.3.4.0 to 2.4.0.0 and YARN service check
> reported failure during EU itself; a retry of the operation led to service
> check being successful
> b. In another test post EU when YARN service check was run, it reported
> failure; afterwards when I ran it again - success
> Looks like there is some corner condition which causes this issue to be hit
> {code}
> stderr: /var/lib/ambari-agent/data/errors-822.txt
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
> line 142, in
> ServiceCheck().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 219, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/service_check.py",
> line 104, in service_check
> user=params.smokeuser,
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 70, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 92, in checked_call
> tries=tries, try_sleep=try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 140, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 291, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/kinit -kt
> /etc/security/keytabs/smokeuser.headless.keytab ambari...@example.com; yarn
> org.apache.hadoop.yarn.applications.distributedshell.Client -shell_command ls
> -num_containers 1 -jar
> /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-applications-distributedshell.jar'
> returned 2. Hortonworks #
> This is MOTD message, added for testing in qe infra
> 16/03/03 02:33:51 INFO impl.TimelineClientImpl: Timeline service address:
> http://host:8188/ws/v1/timeline/
> 16/03/03 02:33:51 INFO distributedshell.Client: Initializing Client
> 16/03/03 02:33:51 INFO distributedshell.Client: Running Client
> 16/03/03 02:33:51 INFO client.RMProxy: Connecting to ResourceManager at
> host-9-5.test/127.0.0.254:8050
> 16/03/03 02:33:53 INFO distributedshell.Client: Got Cluster metric info from
> ASM, numNodeManagers=3
> 16/03/03 02:33:53 INFO distributedshell.Client: Got Cluster node info from ASM
> 16/03/03 02:33:53 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=host:25454, nodeAddresshost:8042, nodeRackName/default-rack,
> nodeNumContainers1
> 16/03/03 02:33:53 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=host-9-5.test:25454, nodeAddresshost-9-5.test:8042,
> nodeRackName/default-rack, nodeNumContainers0
> 16/03/03 02:33:53 INFO distributedshell.Client: Got node report from ASM for,
> nodeId=host-9-1.test:25454, nodeAddresshost-9-1.test:8042,
> nodeRackName/default-rack, nodeNumContainers0
> 16/03/03 02:33:53 INFO distributedshell.Client: Queue info,
> queueName=default, queueCurrentCapacity=0.08336, queueMaxCapacity=1.0,
> queueApplicationCount=0, queueChildQueueCount=0
> 16/03/03 02:33:53 INFO distributedshell.Client: User ACL Info for Queue,
> queueName=root, userAcl=SUBMIT_APPLICATIONS
> 16/03/03 02:33:53 INFO distributedshell.Client: User ACL Info for Queue,
> queueName=default, userAcl=SUBMIT_APPLICATIONS
> 16/03/03 02:33:53 INFO distributedshell.Client: Max mem capabililty of
> resources in this cluster 10240
> 16/03/03 02:33:53 INFO distributedshell.Client: Max virtual cores capabililty
> of resources in this cluster 1
> 16/03/03 02:33:53 INFO distributedshell.Client: Copy App Master jar from
> local filesystem and add to local environment
> 16/03/03 02:33:53 INFO distributedshell.Client: Set the environment for the
> application master
> 16/03/03 02:33:53 INFO distributedshell.Client: Setting up app master command
> 16/03/03 02:33:53 INF
[jira] [Commented] (AMBARI-15649) Service Actions button is missing
[ https://issues.apache.org/jira/browse/AMBARI-15649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219953#comment-15219953 ] Aleksandr Kovalenko commented on AMBARI-15649: -- +1 for the patch > Service Actions button is missing > - > > Key: AMBARI-15649 > URL: https://issues.apache.org/jira/browse/AMBARI-15649 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15649.patch > > > After couple of seconds Service Actions button is hidden -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15670) Disable ability to open Edit Widget Wizard if Ambari Metrics is not installed
Aleksandr Kovalenko created AMBARI-15670: Summary: Disable ability to open Edit Widget Wizard if Ambari Metrics is not installed Key: AMBARI-15670 URL: https://issues.apache.org/jira/browse/AMBARI-15670 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.4.0 If Ambari Metrics is not installed, we are still able to run Edit Widget Wizard by clicking on clone or edit icons on widgets. We should either hide the whole section or disable buttons to clone/edit widgets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15670) Disable ability to open Edit Widget Wizard if Ambari Metrics is not installed
[ https://issues.apache.org/jira/browse/AMBARI-15670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15670: - Attachment: AMBARI-15670.patch 25602 tests complete (27 seconds) 154 tests pending > Disable ability to open Edit Widget Wizard if Ambari Metrics is not installed > -- > > Key: AMBARI-15670 > URL: https://issues.apache.org/jira/browse/AMBARI-15670 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15670.patch > > > If Ambari Metrics is not installed, we are still able to run Edit Widget > Wizard by clicking on clone or edit icons on widgets. > We should either hide the whole section or disable buttons to clone/edit > widgets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15670) Disable ability to open Edit Widget Wizard if Ambari Metrics is not installed
[ https://issues.apache.org/jira/browse/AMBARI-15670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15670: - Status: Patch Available (was: Open) > Disable ability to open Edit Widget Wizard if Ambari Metrics is not installed > -- > > Key: AMBARI-15670 > URL: https://issues.apache.org/jira/browse/AMBARI-15670 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15670.patch > > > If Ambari Metrics is not installed, we are still able to run Edit Widget > Wizard by clicking on clone or edit icons on widgets. > We should either hide the whole section or disable buttons to clone/edit > widgets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15670) Disable ability to open Edit Widget Wizard if Ambari Metrics is not installed
[ https://issues.apache.org/jira/browse/AMBARI-15670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221926#comment-15221926 ] Aleksandr Kovalenko commented on AMBARI-15670: -- committed to trunk > Disable ability to open Edit Widget Wizard if Ambari Metrics is not installed > -- > > Key: AMBARI-15670 > URL: https://issues.apache.org/jira/browse/AMBARI-15670 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15670.patch > > > If Ambari Metrics is not installed, we are still able to run Edit Widget > Wizard by clicking on clone or edit icons on widgets. > We should either hide the whole section or disable buttons to clone/edit > widgets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-14610) Sometimes Assign Slaves and Clients page works not properly
[ https://issues.apache.org/jira/browse/AMBARI-14610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224509#comment-15224509 ] Aleksandr Kovalenko commented on AMBARI-14610: -- +1 for the patch > Sometimes Assign Slaves and Clients page works not properly > --- > > Key: AMBARI-14610 > URL: https://issues.apache.org/jira/browse/AMBARI-14610 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.1 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0, 2.2.2 > > Attachments: AMBARI-14610.patch, AMBARI-14610_branch_2.2.patch > > > STR: > 1) Go to Assign Slaves and Clients page > 2) Click at "all", "none" and "all" links multiple times > Result: an error with "Your slave and client assignment has issues. Click for > details." message appears and disappears several times (delayed reaction) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15731) Host not expanding more than one field in host-name pattern
Aleksandr Kovalenko created AMBARI-15731:
Summary: Host not expanding more than one field in host-name
pattern
Key: AMBARI-15731
URL: https://issues.apache.org/jira/browse/AMBARI-15731
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.1.2
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
Fix For: 2.4.0
PROBLEM
FQDNs follow patterns such as cluster-[1-5].az[1-3].domain and potentially even
more complex patterns, the current wizard only supports expansion of the first
[a-b] pattern. This can be found in the file
/ambari/ambari-web/app/controllers/wizard/step2_controller.js
in the function parseHostNamesAsPatternExpression:
Processing additional expansion would be desirable. Failing that, searching for
further patterns and noting they aren't supported would be helpful. Or some
other mechanism to allow users to specify some pattern that is more complex
that the first [] pair would be helpful.
EXPECTED
hostname expansion behaves more like regex expressions, or supports several in
a hostname expression
ACTUAL
Only the first [ ] pair is expanded, based on the following code
parseHostNamesAsPatternExpression: function () {
337this.set('isPattern', false);
338var self = this;
339var hostNames = [];
340$.each(this.get('hostNameArr'), function (e, a) {
341 var start, end, extra = {0: ""};
342 if (/\[\d*\-\d*\]/.test(a)) {
343start = a.match(/\[\d*/);
344end = a.match(/\-\d*]/);
345
346start = start[0].substr(1);
347end = end[0].substr(1);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15731) Host not expanding more than one field in host-name pattern
[
https://issues.apache.org/jira/browse/AMBARI-15731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-15731:
-
Attachment: AMBARI-15737.patch
> Host not expanding more than one field in host-name pattern
> ---
>
> Key: AMBARI-15731
> URL: https://issues.apache.org/jira/browse/AMBARI-15731
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.1.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15737.patch
>
>
> PROBLEM
> FQDNs follow patterns such as cluster-[1-5].az[1-3].domain and potentially
> even more complex patterns, the current wizard only supports expansion of the
> first [a-b] pattern. This can be found in the file
> /ambari/ambari-web/app/controllers/wizard/step2_controller.js
> in the function parseHostNamesAsPatternExpression:
> Processing additional expansion would be desirable. Failing that, searching
> for further patterns and noting they aren't supported would be helpful. Or
> some other mechanism to allow users to specify some pattern that is more
> complex that the first [] pair would be helpful.
> EXPECTED
> hostname expansion behaves more like regex expressions, or supports several
> in a hostname expression
> ACTUAL
> Only the first [ ] pair is expanded, based on the following code
> parseHostNamesAsPatternExpression: function () {
> 337this.set('isPattern', false);
> 338var self = this;
> 339var hostNames = [];
> 340$.each(this.get('hostNameArr'), function (e, a) {
> 341 var start, end, extra = {0: ""};
> 342 if (/\[\d*\-\d*\]/.test(a)) {
> 343start = a.match(/\[\d*/);
> 344end = a.match(/\-\d*]/);
> 345
> 346start = start[0].substr(1);
> 347end = end[0].substr(1);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15731) Host not expanding more than one field in host-name pattern
[
https://issues.apache.org/jira/browse/AMBARI-15731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-15731:
-
Status: Patch Available (was: Open)
> Host not expanding more than one field in host-name pattern
> ---
>
> Key: AMBARI-15731
> URL: https://issues.apache.org/jira/browse/AMBARI-15731
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.1.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15737.patch
>
>
> PROBLEM
> FQDNs follow patterns such as cluster-[1-5].az[1-3].domain and potentially
> even more complex patterns, the current wizard only supports expansion of the
> first [a-b] pattern. This can be found in the file
> /ambari/ambari-web/app/controllers/wizard/step2_controller.js
> in the function parseHostNamesAsPatternExpression:
> Processing additional expansion would be desirable. Failing that, searching
> for further patterns and noting they aren't supported would be helpful. Or
> some other mechanism to allow users to specify some pattern that is more
> complex that the first [] pair would be helpful.
> EXPECTED
> hostname expansion behaves more like regex expressions, or supports several
> in a hostname expression
> ACTUAL
> Only the first [ ] pair is expanded, based on the following code
> parseHostNamesAsPatternExpression: function () {
> 337this.set('isPattern', false);
> 338var self = this;
> 339var hostNames = [];
> 340$.each(this.get('hostNameArr'), function (e, a) {
> 341 var start, end, extra = {0: ""};
> 342 if (/\[\d*\-\d*\]/.test(a)) {
> 343start = a.match(/\[\d*/);
> 344end = a.match(/\-\d*]/);
> 345
> 346start = start[0].substr(1);
> 347end = end[0].substr(1);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15731) Host not expanding more than one field in host-name pattern
[
https://issues.apache.org/jira/browse/AMBARI-15731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228171#comment-15228171
]
Aleksandr Kovalenko commented on AMBARI-15731:
--
25636 tests complete (33 seconds)
154 tests pending
> Host not expanding more than one field in host-name pattern
> ---
>
> Key: AMBARI-15731
> URL: https://issues.apache.org/jira/browse/AMBARI-15731
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.1.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15737.patch
>
>
> PROBLEM
> FQDNs follow patterns such as cluster-[1-5].az[1-3].domain and potentially
> even more complex patterns, the current wizard only supports expansion of the
> first [a-b] pattern. This can be found in the file
> /ambari/ambari-web/app/controllers/wizard/step2_controller.js
> in the function parseHostNamesAsPatternExpression:
> Processing additional expansion would be desirable. Failing that, searching
> for further patterns and noting they aren't supported would be helpful. Or
> some other mechanism to allow users to specify some pattern that is more
> complex that the first [] pair would be helpful.
> EXPECTED
> hostname expansion behaves more like regex expressions, or supports several
> in a hostname expression
> ACTUAL
> Only the first [ ] pair is expanded, based on the following code
> parseHostNamesAsPatternExpression: function () {
> 337this.set('isPattern', false);
> 338var self = this;
> 339var hostNames = [];
> 340$.each(this.get('hostNameArr'), function (e, a) {
> 341 var start, end, extra = {0: ""};
> 342 if (/\[\d*\-\d*\]/.test(a)) {
> 343start = a.match(/\[\d*/);
> 344end = a.match(/\-\d*]/);
> 345
> 346start = start[0].substr(1);
> 347end = end[0].substr(1);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15731) Host not expanding more than one field in host-name pattern
[
https://issues.apache.org/jira/browse/AMBARI-15731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228356#comment-15228356
]
Aleksandr Kovalenko commented on AMBARI-15731:
--
committed to trunk
> Host not expanding more than one field in host-name pattern
> ---
>
> Key: AMBARI-15731
> URL: https://issues.apache.org/jira/browse/AMBARI-15731
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.1.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15737.patch
>
>
> PROBLEM
> FQDNs follow patterns such as cluster-[1-5].az[1-3].domain and potentially
> even more complex patterns, the current wizard only supports expansion of the
> first [a-b] pattern. This can be found in the file
> /ambari/ambari-web/app/controllers/wizard/step2_controller.js
> in the function parseHostNamesAsPatternExpression:
> Processing additional expansion would be desirable. Failing that, searching
> for further patterns and noting they aren't supported would be helpful. Or
> some other mechanism to allow users to specify some pattern that is more
> complex that the first [] pair would be helpful.
> EXPECTED
> hostname expansion behaves more like regex expressions, or supports several
> in a hostname expression
> ACTUAL
> Only the first [ ] pair is expanded, based on the following code
> parseHostNamesAsPatternExpression: function () {
> 337this.set('isPattern', false);
> 338var self = this;
> 339var hostNames = [];
> 340$.each(this.get('hostNameArr'), function (e, a) {
> 341 var start, end, extra = {0: ""};
> 342 if (/\[\d*\-\d*\]/.test(a)) {
> 343start = a.match(/\[\d*/);
> 344end = a.match(/\-\d*]/);
> 345
> 346start = start[0].substr(1);
> 347end = end[0].substr(1);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15731) Host not expanding more than one field in host-name pattern
[
https://issues.apache.org/jira/browse/AMBARI-15731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-15731:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk
> Host not expanding more than one field in host-name pattern
> ---
>
> Key: AMBARI-15731
> URL: https://issues.apache.org/jira/browse/AMBARI-15731
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.1.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15737.patch
>
>
> PROBLEM
> FQDNs follow patterns such as cluster-[1-5].az[1-3].domain and potentially
> even more complex patterns, the current wizard only supports expansion of the
> first [a-b] pattern. This can be found in the file
> /ambari/ambari-web/app/controllers/wizard/step2_controller.js
> in the function parseHostNamesAsPatternExpression:
> Processing additional expansion would be desirable. Failing that, searching
> for further patterns and noting they aren't supported would be helpful. Or
> some other mechanism to allow users to specify some pattern that is more
> complex that the first [] pair would be helpful.
> EXPECTED
> hostname expansion behaves more like regex expressions, or supports several
> in a hostname expression
> ACTUAL
> Only the first [ ] pair is expanded, based on the following code
> parseHostNamesAsPatternExpression: function () {
> 337this.set('isPattern', false);
> 338var self = this;
> 339var hostNames = [];
> 340$.each(this.get('hostNameArr'), function (e, a) {
> 341 var start, end, extra = {0: ""};
> 342 if (/\[\d*\-\d*\]/.test(a)) {
> 343start = a.match(/\[\d*/);
> 344end = a.match(/\-\d*]/);
> 345
> 346start = start[0].substr(1);
> 347end = end[0].substr(1);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15731) Host not expanding more than one field in host-name pattern
[
https://issues.apache.org/jira/browse/AMBARI-15731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-15731:
-
Attachment: (was: AMBARI-15737.patch)
> Host not expanding more than one field in host-name pattern
> ---
>
> Key: AMBARI-15731
> URL: https://issues.apache.org/jira/browse/AMBARI-15731
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.1.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
>
> PROBLEM
> FQDNs follow patterns such as cluster-[1-5].az[1-3].domain and potentially
> even more complex patterns, the current wizard only supports expansion of the
> first [a-b] pattern. This can be found in the file
> /ambari/ambari-web/app/controllers/wizard/step2_controller.js
> in the function parseHostNamesAsPatternExpression:
> Processing additional expansion would be desirable. Failing that, searching
> for further patterns and noting they aren't supported would be helpful. Or
> some other mechanism to allow users to specify some pattern that is more
> complex that the first [] pair would be helpful.
> EXPECTED
> hostname expansion behaves more like regex expressions, or supports several
> in a hostname expression
> ACTUAL
> Only the first [ ] pair is expanded, based on the following code
> parseHostNamesAsPatternExpression: function () {
> 337this.set('isPattern', false);
> 338var self = this;
> 339var hostNames = [];
> 340$.each(this.get('hostNameArr'), function (e, a) {
> 341 var start, end, extra = {0: ""};
> 342 if (/\[\d*\-\d*\]/.test(a)) {
> 343start = a.match(/\[\d*/);
> 344end = a.match(/\-\d*]/);
> 345
> 346start = start[0].substr(1);
> 347end = end[0].substr(1);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-15731) Host not expanding more than one field in host-name pattern
[
https://issues.apache.org/jira/browse/AMBARI-15731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Kovalenko updated AMBARI-15731:
-
Attachment: AMBARI-15731.patch
> Host not expanding more than one field in host-name pattern
> ---
>
> Key: AMBARI-15731
> URL: https://issues.apache.org/jira/browse/AMBARI-15731
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.1.2
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15731.patch
>
>
> PROBLEM
> FQDNs follow patterns such as cluster-[1-5].az[1-3].domain and potentially
> even more complex patterns, the current wizard only supports expansion of the
> first [a-b] pattern. This can be found in the file
> /ambari/ambari-web/app/controllers/wizard/step2_controller.js
> in the function parseHostNamesAsPatternExpression:
> Processing additional expansion would be desirable. Failing that, searching
> for further patterns and noting they aren't supported would be helpful. Or
> some other mechanism to allow users to specify some pattern that is more
> complex that the first [] pair would be helpful.
> EXPECTED
> hostname expansion behaves more like regex expressions, or supports several
> in a hostname expression
> ACTUAL
> Only the first [ ] pair is expanded, based on the following code
> parseHostNamesAsPatternExpression: function () {
> 337this.set('isPattern', false);
> 338var self = this;
> 339var hostNames = [];
> 340$.each(this.get('hostNameArr'), function (e, a) {
> 341 var start, end, extra = {0: ""};
> 342 if (/\[\d*\-\d*\]/.test(a)) {
> 343start = a.match(/\[\d*/);
> 344end = a.match(/\-\d*]/);
> 345
> 346start = start[0].substr(1);
> 347end = end[0].substr(1);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15735) Check if persist data 'wizard-data' is removed upon exiting any wizard
[ https://issues.apache.org/jira/browse/AMBARI-15735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228394#comment-15228394 ] Aleksandr Kovalenko commented on AMBARI-15735: -- +1 for the patch > Check if persist data 'wizard-data' is removed upon exiting any wizard > -- > > Key: AMBARI-15735 > URL: https://issues.apache.org/jira/browse/AMBARI-15735 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.4.0 > > Attachments: AMBARI-15735.patch > > > Sometimes 'wizard-data' is not removed removed upon exiting any wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15763) Delete service: UX edits v2
[ https://issues.apache.org/jira/browse/AMBARI-15763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230371#comment-15230371 ] Aleksandr Kovalenko commented on AMBARI-15763: -- +1 for the patch > Delete service: UX edits v2 > --- > > Key: AMBARI-15763 > URL: https://issues.apache.org/jira/browse/AMBARI-15763 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15763.patch, minor-wording (1).pptx > > > Minor text edit to dependent service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15765) Improve config groups loading on wizard (part 2)
[ https://issues.apache.org/jira/browse/AMBARI-15765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230397#comment-15230397 ] Aleksandr Kovalenko commented on AMBARI-15765: -- +1 for the patch > Improve config groups loading on wizard (part 2) > > > Key: AMBARI-15765 > URL: https://issues.apache.org/jira/browse/AMBARI-15765 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-15765.patch > > > Use ServiceConfigGroups mapper to generate config groups on installer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15768) Ambari Widget should display metrics for available metrics even if some of the metrics it expects are not returned by API
[ https://issues.apache.org/jira/browse/AMBARI-15768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230487#comment-15230487 ] Aleksandr Kovalenko commented on AMBARI-15768: -- +1 for the patch > Ambari Widget should display metrics for available metrics even if some of > the metrics it expects are not returned by API > - > > Key: AMBARI-15768 > URL: https://issues.apache.org/jira/browse/AMBARI-15768 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15768.patch, AMBARI-15768_2.2.2.patch, Screen > Shot 2016-04-06 at 2.53.23 PM.png > > > For example, Namenode RPC widget requests 5 metrics from the backend. 2 of > the metrics' availability depends on a Namenode config to be present. In such > a case, the widget should display whatever metrics that are available. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15782) trunk deploy marks dfs.ha.fencing.methods as a required property
[ https://issues.apache.org/jira/browse/AMBARI-15782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232588#comment-15232588 ] Aleksandr Kovalenko commented on AMBARI-15782: -- +1 for the patch > trunk deploy marks dfs.ha.fencing.methods as a required property > > > Key: AMBARI-15782 > URL: https://issues.apache.org/jira/browse/AMBARI-15782 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15782.patch, Screen Shot 2016-04-07 at 9.10.08 > PM.png > > > See attached image. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15799) Validation issues popup should have "Continue Anyway" button is in green(success) color
[ https://issues.apache.org/jira/browse/AMBARI-15799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234793#comment-15234793 ] Aleksandr Kovalenko commented on AMBARI-15799: -- +1 for the patch > Validation issues popup should have "Continue Anyway" button is in > green(success) color > --- > > Key: AMBARI-15799 > URL: https://issues.apache.org/jira/browse/AMBARI-15799 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15799.patch > > > See attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15839) Wrong config group names after renaming and creating group with the same name
Aleksandr Kovalenko created AMBARI-15839: Summary: Wrong config group names after renaming and creating group with the same name Key: AMBARI-15839 URL: https://issues.apache.org/jira/browse/AMBARI-15839 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.4.0 STR: 1. Install Ambari. 2. Open Manager Config Groups popup, create cg with name "1" and save. 3. Open Manager Config Groups popup, rename config group "1" to "2". Do not save. 4. Create new group with name "1". After doing this steps you will have two groups with name "1". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15839) Wrong config group names after renaming and creating group with the same name
[ https://issues.apache.org/jira/browse/AMBARI-15839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15839: - Attachment: AMBARI-15839.patch > Wrong config group names after renaming and creating group with the same name > - > > Key: AMBARI-15839 > URL: https://issues.apache.org/jira/browse/AMBARI-15839 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15839.patch > > > STR: > 1. Install Ambari. > 2. Open Manager Config Groups popup, create cg with name "1" and save. > 3. Open Manager Config Groups popup, rename config group "1" to "2". Do not > save. > 4. Create new group with name "1". > After doing this steps you will have two groups with name "1". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15839) Wrong config group names after renaming and creating group with the same name
[ https://issues.apache.org/jira/browse/AMBARI-15839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237362#comment-15237362 ] Aleksandr Kovalenko commented on AMBARI-15839: -- 25637 tests complete (27 seconds) 154 tests pending > Wrong config group names after renaming and creating group with the same name > - > > Key: AMBARI-15839 > URL: https://issues.apache.org/jira/browse/AMBARI-15839 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15839.patch > > > STR: > 1. Install Ambari. > 2. Open Manager Config Groups popup, create cg with name "1" and save. > 3. Open Manager Config Groups popup, rename config group "1" to "2". Do not > save. > 4. Create new group with name "1". > After doing this steps you will have two groups with name "1". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15840) Sorting Alerts with ALERT NAMES in Alerts UI is not working as expected
[ https://issues.apache.org/jira/browse/AMBARI-15840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237415#comment-15237415 ] Aleksandr Kovalenko commented on AMBARI-15840: -- +1 for the patch > Sorting Alerts with ALERT NAMES in Alerts UI is not working as expected > --- > > Key: AMBARI-15840 > URL: https://issues.apache.org/jira/browse/AMBARI-15840 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.2.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.4.0 > > Attachments: AMBARI-15840.patch, Screen Shot 2016-04-07 at 10.41.58 > AM.png > > > System tests cases to test sorting Alerts with Alert names failing in the > following scenario > 1. Go to Alerts page > 2. Sort Alerts with Alert Names in Descending Order > 3. Expected to sort the table in descending order (lexicologically e.g > ZooKeeper Server Process,ZooKeeper Failover Controller Process, ...Ambari > Agent Heartbeat) > 4. Specific case failing is "NFS Gateway Process" should be displayed before > "NameNode Web UI" but as sort order is descending. But it's displayed the > other way -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15838) Kerberos : Referencing an identity across service's kerberos files is not honored and hangs at 'configure identities'.
[
https://issues.apache.org/jira/browse/AMBARI-15838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237420#comment-15237420
]
Aleksandr Kovalenko commented on AMBARI-15838:
--
+1 for the patch
> Kerberos : Referencing an identity across service's kerberos files is not
> honored and hangs at 'configure identities'.
> --
>
> Key: AMBARI-15838
> URL: https://issues.apache.org/jira/browse/AMBARI-15838
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15838.patch
>
>
> - Kerberos : Referencing an identity across service's kerberos files is not
> honored and hangs at 'configure identities'.
> - Scenario : I am creating reference in YARN/kerberos.json for existing
> "/HIVE/HIVE_SERVER/hive_server_hive".
> YARN/kerberos.json
> {code}
> "components": [
> {
> "name": "NODEMANAGER",
>
> .
>{
> "name": "/HIVE/HIVE_SERVER/hive_server_hive",
> "principal": {
> "configuration":
> "hive-interactive-site/hive.llap.daemon.service.principal"
> },
> "keytab": {
> "configuration":
> "hive-interactive-site/hive.llap.daemon.keytab.file"
> }
> },
> {code}
> and it hangs at configure identities while kerberizing.
> Trace :
> {code}
> app.js:65760 Uncaught TypeError: Cannot read property 'principal' of
> undefined(anonymous function) @
> app.js:65760App.AddSecurityConfigs.Em.Mixin.create.processConfigReferences @
> app.js:65757App.AddSecurityConfigs.Em.Mixin.create.createServicesStackDescriptorConfigs
> @ app.js:65598(anonymous function) @ app.js:10139o @ vendor.js:106p.fireWith
> @ vendor.js:106p.fire @ vendor.js:106successCallback @ app.js:10159o @
> vendor.js:106p.fireWith @ vendor.js:106w @ vendor.js:108d @ vendor.js:108
> app.js:51974 App.stackConfigPropertiesMapper execution time: 20.257ms
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-15833) ResourceManager quicklink goes to the wrong address
[ https://issues.apache.org/jira/browse/AMBARI-15833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237423#comment-15237423 ] Aleksandr Kovalenko commented on AMBARI-15833: -- +1 for the patch > ResourceManager quicklink goes to the wrong address > --- > > Key: AMBARI-15833 > URL: https://issues.apache.org/jira/browse/AMBARI-15833 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-15833.patch > > > The resourcemanager quick link goes to hostname:8188 instead of > hostname:8088. This has been around on Ambari 2.4 for some time. Not sure > which other versions it affects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15839) Wrong config group names after renaming and creating group with the same name
[ https://issues.apache.org/jira/browse/AMBARI-15839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237455#comment-15237455 ] Aleksandr Kovalenko commented on AMBARI-15839: -- committed to trunk > Wrong config group names after renaming and creating group with the same name > - > > Key: AMBARI-15839 > URL: https://issues.apache.org/jira/browse/AMBARI-15839 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15839.patch > > > STR: > 1. Install Ambari. > 2. Open Manager Config Groups popup, create cg with name "1" and save. > 3. Open Manager Config Groups popup, rename config group "1" to "2". Do not > save. > 4. Create new group with name "1". > After doing this steps you will have two groups with name "1". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15839) Wrong config group names after renaming and creating group with the same name
[ https://issues.apache.org/jira/browse/AMBARI-15839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15839: - Resolution: Fixed Status: Resolved (was: Patch Available) > Wrong config group names after renaming and creating group with the same name > - > > Key: AMBARI-15839 > URL: https://issues.apache.org/jira/browse/AMBARI-15839 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15839.patch > > > STR: > 1. Install Ambari. > 2. Open Manager Config Groups popup, create cg with name "1" and save. > 3. Open Manager Config Groups popup, rename config group "1" to "2". Do not > save. > 4. Create new group with name "1". > After doing this steps you will have two groups with name "1". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15839) Wrong config group names after renaming and creating group with the same name
[ https://issues.apache.org/jira/browse/AMBARI-15839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15839: - Status: Patch Available (was: Open) > Wrong config group names after renaming and creating group with the same name > - > > Key: AMBARI-15839 > URL: https://issues.apache.org/jira/browse/AMBARI-15839 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15839.patch > > > STR: > 1. Install Ambari. > 2. Open Manager Config Groups popup, create cg with name "1" and save. > 3. Open Manager Config Groups popup, rename config group "1" to "2". Do not > save. > 4. Create new group with name "1". > After doing this steps you will have two groups with name "1". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-15863) No label for custom property for config group
Aleksandr Kovalenko created AMBARI-15863: Summary: No label for custom property for config group Key: AMBARI-15863 URL: https://issues.apache.org/jira/browse/AMBARI-15863 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Fix For: 2.4.0 Go to created config group and try to add custom property. It will not have label right after adding it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15863) No label for custom property for config group
[ https://issues.apache.org/jira/browse/AMBARI-15863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15863: - Attachment: no_label.png > No label for custom property for config group > - > > Key: AMBARI-15863 > URL: https://issues.apache.org/jira/browse/AMBARI-15863 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: no_label.png > > > Go to created config group and try to add custom property. It will not have > label right after adding it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15863) No label for custom property for config group
[ https://issues.apache.org/jira/browse/AMBARI-15863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15863: - Attachment: AMBARI-15863.patch > No label for custom property for config group > - > > Key: AMBARI-15863 > URL: https://issues.apache.org/jira/browse/AMBARI-15863 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15863.patch, no_label.png > > > Go to created config group and try to add custom property. It will not have > label right after adding it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15863) No label for custom property for config group
[ https://issues.apache.org/jira/browse/AMBARI-15863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15863: - Status: Patch Available (was: Open) > No label for custom property for config group > - > > Key: AMBARI-15863 > URL: https://issues.apache.org/jira/browse/AMBARI-15863 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15863.patch, no_label.png > > > Go to created config group and try to add custom property. It will not have > label right after adding it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15863) No label for custom property for config group
[ https://issues.apache.org/jira/browse/AMBARI-15863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239378#comment-15239378 ] Aleksandr Kovalenko commented on AMBARI-15863: -- 25608 tests complete (27 seconds) 154 tests pending > No label for custom property for config group > - > > Key: AMBARI-15863 > URL: https://issues.apache.org/jira/browse/AMBARI-15863 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15863.patch, no_label.png > > > Go to created config group and try to add custom property. It will not have > label right after adding it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-15863) No label for custom property for config group
[ https://issues.apache.org/jira/browse/AMBARI-15863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-15863: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to trunk > No label for custom property for config group > - > > Key: AMBARI-15863 > URL: https://issues.apache.org/jira/browse/AMBARI-15863 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko > Fix For: 2.4.0 > > Attachments: AMBARI-15863.patch, no_label.png > > > Go to created config group and try to add custom property. It will not have > label right after adding it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-15889) Wrong overrides after Add Service Wizard
[ https://issues.apache.org/jira/browse/AMBARI-15889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241449#comment-15241449 ] Aleksandr Kovalenko commented on AMBARI-15889: -- +1 for the patch > Wrong overrides after Add Service Wizard > > > Key: AMBARI-15889 > URL: https://issues.apache.org/jira/browse/AMBARI-15889 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 2.4.0 > > Attachments: AMBARI-15889.patch > > > When saving more than one config group for one service which updates same > file name, overrides can be saved not properly -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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-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] [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] [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] [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] [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] [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] [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-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-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-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-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-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-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-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-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] [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] [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] [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] [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] [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] [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-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] [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] [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] [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] [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] [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] [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)
