[jira] [Commented] (AMBARI-22220) Should be able to switch the extension version to which a stack version is linked
[ https://issues.apache.org/jira/browse/AMBARI-0?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265530#comment-16265530 ] Hudson commented on AMBARI-0: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #482 (See [https://builds.apache.org/job/Ambari-branch-2.6/482/]) AMBARI-0 - Should be able to switch the extension version to which a (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=5fab8ff3d768c2edf8408361feba87bc09b02bf2]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementController.java * (add) ambari-server/src/test/resources/extensions/EXT/0.4/metainfo.xml * (add) ambari-server/src/test/resources/extensions/EXT/0.4/services/OOZIE2/metainfo.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerExtensionTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ExtensionHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ExtensionLinkResourceProvider.java * (edit) ambari-server/src/test/resources/extensions/EXT/0.2/metainfo.xml * (add) ambari-server/src/test/resources/extensions/EXT/0.4/services/OOZIE2/themes/broken_theme.json > Should be able to switch the extension version to which a stack version is > linked > -- > > Key: AMBARI-0 > URL: https://issues.apache.org/jira/browse/AMBARI-0 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.5.0, 2.6.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-0.patch > > > Currently the only way to switch the extension version to which a stack > version is linked is to perform the following actions: > * Stop the extension services > * Reregister (delete) the extension services > * Unlink the old extension version > * Link the new extension version > * Add the extension services back > The REST API should allow us to do an update action on the extension link. > In this manner, if we were running an upgrade from HDP 2.6.1 to 2.6.3 (or > something similar) which both use the HDP 2.6 stack version then we could > perform the extension link switch as a manual step during the upgrade process. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22137) Different stack versions should be able to link to different extension versions
[ https://issues.apache.org/jira/browse/AMBARI-22137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265529#comment-16265529 ] Hudson commented on AMBARI-22137: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #482 (See [https://builds.apache.org/job/Ambari-branch-2.6/482/]) AMBARI-22137 - Different stack versions should be able to link to (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d7b25eec2629822f90cac6de510f806b1004a8f7]) * (edit) ambari-server/src/test/resources/extensions/EXT/0.2/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/HBASE/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/HDFS/configuration/hdfs-site.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/HIVE/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementHelper.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/HDFS/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/repos/repoinfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ExtensionHelper.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerExtensionTest.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/HDFS/configuration/hadoop-env.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/HDFS/configuration/hdfs-log4j.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/MAPREDUCE/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/HDFS/configuration/global.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/HDFS/configuration/hbase-site.xml * (edit) ambari-server/src/test/resources/extensions/EXT/0.3/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/ZOOKEEPER/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.4/services/HDFS/package/dummy-script.py > Different stack versions should be able to link to different extension > versions > --- > > Key: AMBARI-22137 > URL: https://issues.apache.org/jira/browse/AMBARI-22137 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-22137.patch > > > Currently if you have extension version 0.1 linked to HDP 2.5, you can't link > extension version 0.2 to HDP 2.6. > Attempting to make that link will fail with an exception stating that the > services included in extension version 0.2 are already in HDP 2.6 (inherited > from HDP 2.5 via the 0.1 version of the extension). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22515) Fix validators tests in feature branch
[ https://issues.apache.org/jira/browse/AMBARI-22515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi resolved AMBARI-22515. Resolution: Fixed Committed to branch-feature-AMBARI-14714 > Fix validators tests in feature branch > -- > > Key: AMBARI-22515 > URL: https://issues.apache.org/jira/browse/AMBARI-22515 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22515.patch > > > Fix validators tests in feature branch -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22515) Fix validators tests in feature branch
Vitaly Brodetskyi created AMBARI-22515: -- Summary: Fix validators tests in feature branch Key: AMBARI-22515 URL: https://issues.apache.org/jira/browse/AMBARI-22515 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Vitaly Brodetskyi Assignee: Vitaly Brodetskyi Priority: Critical Fix For: 3.0.0 Fix validators tests in feature branch -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22515) Fix validators tests in feature branch
[ https://issues.apache.org/jira/browse/AMBARI-22515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-22515: --- Attachment: AMBARI-22515.patch > Fix validators tests in feature branch > -- > > Key: AMBARI-22515 > URL: https://issues.apache.org/jira/browse/AMBARI-22515 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22515.patch > > > Fix validators tests in feature branch -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-20891) Allow extensions to auto-link with supported stack versions
[ https://issues.apache.org/jira/browse/AMBARI-20891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265519#comment-16265519 ] Hudson commented on AMBARI-20891: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #481 (See [https://builds.apache.org/job/Ambari-branch-2.6/481/]) AMBARI-20891 - Allow extensions to auto-link with supported stack (tthorpe: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7c56924a952358127dd80eef7e8c9dfeac0aa8b0]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackManager.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java * (add) ambari-server/src/test/resources/extensions/EXT/0.3/metainfo.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ExtensionLinkEntity.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/configuration/hdfs-site.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerExtensionTest.java * (add) ambari-server/src/test/resources/extensions/EXT/0.3/services/OOZIE2/themes/broken_theme.json * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/repos/repoinfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/stack/ExtensionMetainfoXml.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerCommonServicesTest.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HIVE/metainfo.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerMock.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HBASE/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/MAPREDUCE/metainfo.xml * (edit) ambari-server/src/test/resources/extensions/EXT/0.2/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/package/dummy-script.py * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/configuration/hadoop-env.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/StackModule.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/StackInfo.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/metainfo.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerTest.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/metainfo.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/ZOOKEEPER/metainfo.xml * (add) ambari-server/src/test/resources/extensions/EXT/0.3/services/OOZIE2/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ExtensionLinkDAO.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/configuration/hbase-site.xml * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/configuration/hdfs-log4j.xml * (edit) ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerMiscTest.java * (edit) ambari-server/src/test/resources/extensions/EXT/0.1/metainfo.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/stack/ExtensionModule.java * (add) ambari-server/src/test/resources/stacks_with_extensions/HDP/0.3/services/HDFS/configuration/global.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ExtensionInfo.java > Allow extensions to auto-link with supported stack versions > --- > > Key: AMBARI-20891 > URL: https://issues.apache.org/jira/browse/AMBARI-20891 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-20891.patch > > > It would possible to link extensions to supported stack versions while > parsing the stacks, extensions and common-services directories. > This would allow extensions to avoid making rest API calls to set up the link. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22220) Should be able to switch the extension version to which a stack version is linked
[ https://issues.apache.org/jira/browse/AMBARI-0?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-0: Fix Version/s: 2.6.1 > Should be able to switch the extension version to which a stack version is > linked > -- > > Key: AMBARI-0 > URL: https://issues.apache.org/jira/browse/AMBARI-0 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk, 2.5.0, 2.6.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-0.patch > > > Currently the only way to switch the extension version to which a stack > version is linked is to perform the following actions: > * Stop the extension services > * Reregister (delete) the extension services > * Unlink the old extension version > * Link the new extension version > * Add the extension services back > The REST API should allow us to do an update action on the extension link. > In this manner, if we were running an upgrade from HDP 2.6.1 to 2.6.3 (or > something similar) which both use the HDP 2.6 stack version then we could > perform the extension link switch as a manual step during the upgrade process. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20891) Allow extensions to auto-link with supported stack versions
[ https://issues.apache.org/jira/browse/AMBARI-20891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-20891: Fix Version/s: 2.6.1 > Allow extensions to auto-link with supported stack versions > --- > > Key: AMBARI-20891 > URL: https://issues.apache.org/jira/browse/AMBARI-20891 > Project: Ambari > Issue Type: New Feature > Components: ambari-server >Affects Versions: trunk >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-20891.patch > > > It would possible to link extensions to supported stack versions while > parsing the stacks, extensions and common-services directories. > This would allow extensions to avoid making rest API calls to set up the link. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22137) Different stack versions should be able to link to different extension versions
[ https://issues.apache.org/jira/browse/AMBARI-22137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Thorpe updated AMBARI-22137: Fix Version/s: 2.6.1 > Different stack versions should be able to link to different extension > versions > --- > > Key: AMBARI-22137 > URL: https://issues.apache.org/jira/browse/AMBARI-22137 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Tim Thorpe >Assignee: Tim Thorpe > Fix For: trunk, 2.6.1 > > Attachments: AMBARI-22137.patch > > > Currently if you have extension version 0.1 linked to HDP 2.5, you can't link > extension version 0.2 to HDP 2.6. > Attempting to make that link will fail with an exception stating that the > services included in extension version 0.2 are already in HDP 2.6 (inherited > from HDP 2.5 via the 0.1 version of the extension). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22510) Handle new error type from Stack Advisor
[ https://issues.apache.org/jira/browse/AMBARI-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22510: - Resolution: Fixed Status: Resolved (was: Patch Available) > Handle new error type from Stack Advisor > > > Key: AMBARI-22510 > URL: https://issues.apache.org/jira/browse/AMBARI-22510 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22510.patch, AMBARI-22510_branch-2.6.patch > > > 1. Handle the new error type by displaying the error message with a new style > 2. Stop the user from proceeding to the next step if this error type is > encountered. > Use Case: > When the user did not agree to GPL terms, but > *io.compression.codec.lzo.class* in *core-site.xml* contains > *com.hadoop.compression.lzo.LzoCodec*, we need to throw a hard error that > prevents the user from proceeding. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22510) Handle new error type from Stack Advisor
[ https://issues.apache.org/jira/browse/AMBARI-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265440#comment-16265440 ] Aleksandr Kovalenko commented on AMBARI-22510: -- committed to trunk and branch-2.6 > Handle new error type from Stack Advisor > > > Key: AMBARI-22510 > URL: https://issues.apache.org/jira/browse/AMBARI-22510 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22510.patch, AMBARI-22510_branch-2.6.patch > > > 1. Handle the new error type by displaying the error message with a new style > 2. Stop the user from proceeding to the next step if this error type is > encountered. > Use Case: > When the user did not agree to GPL terms, but > *io.compression.codec.lzo.class* in *core-site.xml* contains > *com.hadoop.compression.lzo.LzoCodec*, we need to throw a hard error that > prevents the user from proceeding. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22510) Handle new error type from Stack Advisor
[ https://issues.apache.org/jira/browse/AMBARI-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265419#comment-16265419 ] Hudson commented on AMBARI-22510: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8440 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8440/]) AMBARI-22510. Handle new error type from Stack Advisor (akovalenko) (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c5fe6cb96a6530d0fc44c4ffced2ec46db97233b]) * (edit) ambari-web/app/mixins/common/serverValidator.js * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/views/common/modal_popups/config_validation/config_validation_popup.js * (edit) ambari-web/app/templates/common/modal_popups/config_recommendation_popup.hbs * (edit) ambari-web/app/messages.js * (edit) ambari-web/test/mixins/common/serverValidator_test.js > Handle new error type from Stack Advisor > > > Key: AMBARI-22510 > URL: https://issues.apache.org/jira/browse/AMBARI-22510 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22510.patch, AMBARI-22510_branch-2.6.patch > > > 1. Handle the new error type by displaying the error message with a new style > 2. Stop the user from proceeding to the next step if this error type is > encountered. > Use Case: > When the user did not agree to GPL terms, but > *io.compression.codec.lzo.class* in *core-site.xml* contains > *com.hadoop.compression.lzo.LzoCodec*, we need to throw a hard error that > prevents the user from proceeding. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22510) Handle new error type from Stack Advisor
[ https://issues.apache.org/jira/browse/AMBARI-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265408#comment-16265408 ] Hudson commented on AMBARI-22510: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #480 (See [https://builds.apache.org/job/Ambari-branch-2.6/480/]) AMBARI-22510. Handle new error type from Stack Advisor (akovalenko) (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0e2e711e0616ea00e8d7bac1f375977e019e6e77]) * (edit) ambari-web/test/mixins/common/serverValidator_test.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/views/common/modal_popups/config_validation/config_validation_popup.js * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/mixins/common/serverValidator.js * (edit) ambari-web/app/templates/common/modal_popups/config_recommendation_popup.hbs > Handle new error type from Stack Advisor > > > Key: AMBARI-22510 > URL: https://issues.apache.org/jira/browse/AMBARI-22510 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22510.patch, AMBARI-22510_branch-2.6.patch > > > 1. Handle the new error type by displaying the error message with a new style > 2. Stop the user from proceeding to the next step if this error type is > encountered. > Use Case: > When the user did not agree to GPL terms, but > *io.compression.codec.lzo.class* in *core-site.xml* contains > *com.hadoop.compression.lzo.LzoCodec*, we need to throw a hard error that > prevents the user from proceeding. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22510) Handle new error type from Stack Advisor
[ https://issues.apache.org/jira/browse/AMBARI-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265380#comment-16265380 ] Andrii Babiichuk commented on AMBARI-22510: --- +1 for the patch > Handle new error type from Stack Advisor > > > Key: AMBARI-22510 > URL: https://issues.apache.org/jira/browse/AMBARI-22510 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22510.patch, AMBARI-22510_branch-2.6.patch > > > 1. Handle the new error type by displaying the error message with a new style > 2. Stop the user from proceeding to the next step if this error type is > encountered. > Use Case: > When the user did not agree to GPL terms, but > *io.compression.codec.lzo.class* in *core-site.xml* contains > *com.hadoop.compression.lzo.LzoCodec*, we need to throw a hard error that > prevents the user from proceeding. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22510) Handle new error type from Stack Advisor
[
https://issues.apache.org/jira/browse/AMBARI-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265378#comment-16265378
]
Aleksandr Kovalenko commented on AMBARI-22510:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12899136/AMBARI-22510.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12730//console
This message is automatically generated.
> Handle new error type from Stack Advisor
>
>
> Key: AMBARI-22510
> URL: https://issues.apache.org/jira/browse/AMBARI-22510
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22510.patch, AMBARI-22510_branch-2.6.patch
>
>
> 1. Handle the new error type by displaying the error message with a new style
> 2. Stop the user from proceeding to the next step if this error type is
> encountered.
> Use Case:
> When the user did not agree to GPL terms, but
> *io.compression.codec.lzo.class* in *core-site.xml* contains
> *com.hadoop.compression.lzo.LzoCodec*, we need to throw a hard error that
> prevents the user from proceeding.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22513) Make yumrpm.py functions to use global defined commands
[
https://issues.apache.org/jira/browse/AMBARI-22513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265359#comment-16265359
]
Hudson commented on AMBARI-22513:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8439 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8439/])
AMBARI-22513 Make yumrpm.py functions to use global defined commands
(hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0249073469de5cd11f032705d609f8cb19ff28c0])
* (edit)
ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py
> Make yumrpm.py functions to use global defined commands
> ---
>
> Key: AMBARI-22513
> URL: https://issues.apache.org/jira/browse/AMBARI-22513
> Project: Ambari
> Issue Type: Bug
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Attachments: AMBARI-22513.patch
>
>
> At the global space of yumrmp we defining the list of command available for
> the module:
> {code}
> ALL_INSTALLED_PACKAGES_CMD = [AMBARI_SUDO_BINARY, "yum", "list", "installed",
> "--noplugins"]
> ALL_AVAILABLE_PACKAGES_CMD = [AMBARI_SUDO_BINARY, "yum", "list", "available",
> "--noplugins"]
> {code}
> but not using them at the functions:
> - _get_installed_packages
> - _get_available_packages
> What makes them to ignore changes made in command definition constants
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22513) Make yumrpm.py functions to use global defined commands
[
https://issues.apache.org/jira/browse/AMBARI-22513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265355#comment-16265355
]
Hudson commented on AMBARI-22513:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #479 (See
[https://builds.apache.org/job/Ambari-branch-2.6/479/])
AMBARI-22513 Make yumrpm.py functions to use global defined commands
(hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=54bc2a2e38a022356f1c405f755ac1b000450b3a])
* (edit)
ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py
> Make yumrpm.py functions to use global defined commands
> ---
>
> Key: AMBARI-22513
> URL: https://issues.apache.org/jira/browse/AMBARI-22513
> Project: Ambari
> Issue Type: Bug
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Attachments: AMBARI-22513.patch
>
>
> At the global space of yumrmp we defining the list of command available for
> the module:
> {code}
> ALL_INSTALLED_PACKAGES_CMD = [AMBARI_SUDO_BINARY, "yum", "list", "installed",
> "--noplugins"]
> ALL_AVAILABLE_PACKAGES_CMD = [AMBARI_SUDO_BINARY, "yum", "list", "available",
> "--noplugins"]
> {code}
> but not using them at the functions:
> - _get_installed_packages
> - _get_available_packages
> What makes them to ignore changes made in command definition constants
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22513) Make yumrpm.py functions to use global defined commands
[
https://issues.apache.org/jira/browse/AMBARI-22513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22513:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed:
c57e243d2d..54bc2a2e38 branch-2.6 -> branch-2.6
99b19e5805..0249073469 trunk -> trunk
> Make yumrpm.py functions to use global defined commands
> ---
>
> Key: AMBARI-22513
> URL: https://issues.apache.org/jira/browse/AMBARI-22513
> Project: Ambari
> Issue Type: Bug
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Blocker
> Attachments: AMBARI-22513.patch
>
>
> At the global space of yumrmp we defining the list of command available for
> the module:
> {code}
> ALL_INSTALLED_PACKAGES_CMD = [AMBARI_SUDO_BINARY, "yum", "list", "installed",
> "--noplugins"]
> ALL_AVAILABLE_PACKAGES_CMD = [AMBARI_SUDO_BINARY, "yum", "list", "available",
> "--noplugins"]
> {code}
> but not using them at the functions:
> - _get_installed_packages
> - _get_available_packages
> What makes them to ignore changes made in command definition constants
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22514) Infra Manager: Schedulable document deletion & archiving for Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-22514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-22514: -- Summary: Infra Manager: Schedulable document deletion & archiving for Infra Solr (was: Schedulable document deletion & archiving for Infra Solr) > Infra Manager: Schedulable document deletion & archiving for Infra Solr > --- > > Key: AMBARI-22514 > URL: https://issues.apache.org/jira/browse/AMBARI-22514 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 3.0.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Critical > Fix For: 3.0.0 > > Original Estimate: 240h > Remaining Estimate: 240h > > If the data size is too big, and the max retention is not good enough, we > should delete the latest logs from solr, but of course we need the data > itself, so we should archive the data somewhere else (like s3 or hdfs) > This feature should also provide support for configurable policies that users > can configure in order to determine how long data is held and/or archived. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22514) Schedulable document deletion & archiving for Infra Solr
[ https://issues.apache.org/jira/browse/AMBARI-22514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-22514: -- Priority: Critical (was: Major) > Schedulable document deletion & archiving for Infra Solr > > > Key: AMBARI-22514 > URL: https://issues.apache.org/jira/browse/AMBARI-22514 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 3.0.0 >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Critical > Fix For: 3.0.0 > > Original Estimate: 240h > Remaining Estimate: 240h > > If the data size is too big, and the max retention is not good enough, we > should delete the latest logs from solr, but of course we need the data > itself, so we should archive the data somewhere else (like s3 or hdfs) > This feature should also provide support for configurable policies that users > can configure in order to determine how long data is held and/or archived. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22509) Fix DatabaseConsistencyCheckHelper in branch-feature-AMBARI-14714 branch
[
https://issues.apache.org/jira/browse/AMBARI-22509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Sen resolved AMBARI-22509.
-
Resolution: Fixed
> Fix DatabaseConsistencyCheckHelper in branch-feature-AMBARI-14714 branch
>
>
> Key: AMBARI-22509
> URL: https://issues.apache.org/jira/browse/AMBARI-22509
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 3.0.0
>
>
> {noformat:title=/var/log/ambari-server/ambari-server-check-database.log}
> 2017-11-06 22:00:54,125 INFO - Executing query 'GET_SERVICES_WITHOUT_CONFIGS'
> 2017-11-06 22:00:54,129 WARN - Exception occurred during complex service
> check procedure:
> org.postgresql.util.PSQLException: ERROR: column sc.service_name does not
> exist
> Position: 214
> at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
> at
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
> at
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:403)
> at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:283)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:945)
> at
> org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.runAllDBChecks(DatabaseConsistencyCheckHelper.java:192)
> at
> org.apache.ambari.server.controller.AmbariServer.runDatabaseConsistencyCheck(AmbariServer.java:699)
> at
> org.apache.ambari.server.controller.AmbariServer.run(AmbariServer.java:325)
> at
> org.apache.ambari.server.controller.AmbariServer.main(AmbariServer.java:1101)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22510) Handle new error type from Stack Advisor
[ https://issues.apache.org/jira/browse/AMBARI-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22510: - Status: Patch Available (was: Open) > Handle new error type from Stack Advisor > > > Key: AMBARI-22510 > URL: https://issues.apache.org/jira/browse/AMBARI-22510 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22510.patch, AMBARI-22510_branch-2.6.patch > > > 1. Handle the new error type by displaying the error message with a new style > 2. Stop the user from proceeding to the next step if this error type is > encountered. > Use Case: > When the user did not agree to GPL terms, but > *io.compression.codec.lzo.class* in *core-site.xml* contains > *com.hadoop.compression.lzo.LzoCodec*, we need to throw a hard error that > prevents the user from proceeding. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22510) Handle new error type from Stack Advisor
[ https://issues.apache.org/jira/browse/AMBARI-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22510: - Attachment: AMBARI-22510.patch > Handle new error type from Stack Advisor > > > Key: AMBARI-22510 > URL: https://issues.apache.org/jira/browse/AMBARI-22510 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22510.patch, AMBARI-22510_branch-2.6.patch > > > 1. Handle the new error type by displaying the error message with a new style > 2. Stop the user from proceeding to the next step if this error type is > encountered. > Use Case: > When the user did not agree to GPL terms, but > *io.compression.codec.lzo.class* in *core-site.xml* contains > *com.hadoop.compression.lzo.LzoCodec*, we need to throw a hard error that > prevents the user from proceeding. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22510) Handle new error type from Stack Advisor
[ https://issues.apache.org/jira/browse/AMBARI-22510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22510: - Attachment: AMBARI-22510_branch-2.6.patch > Handle new error type from Stack Advisor > > > Key: AMBARI-22510 > URL: https://issues.apache.org/jira/browse/AMBARI-22510 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.6.1 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 2.6.1 > > Attachments: AMBARI-22510_branch-2.6.patch > > > 1. Handle the new error type by displaying the error message with a new style > 2. Stop the user from proceeding to the next step if this error type is > encountered. > Use Case: > When the user did not agree to GPL terms, but > *io.compression.codec.lzo.class* in *core-site.xml* contains > *com.hadoop.compression.lzo.LzoCodec*, we need to throw a hard error that > prevents the user from proceeding. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22511) Broken links to archived releases
[ https://issues.apache.org/jira/browse/AMBARI-22511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-22511: --- Component/s: documentation > Broken links to archived releases > - > > Key: AMBARI-22511 > URL: https://issues.apache.org/jira/browse/AMBARI-22511 > Project: Ambari > Issue Type: Bug > Components: documentation >Reporter: Sebb >Assignee: Doroszlai, Attila > > The links to releases on the home page are mostly broken. > Once the release is archived, the link should be updated to point to the > archive server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22511) Broken links to archived releases
[ https://issues.apache.org/jira/browse/AMBARI-22511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila resolved AMBARI-22511. Resolution: Fixed I have updated the broken links for 2.4.2, 2.1.1, and 2.1.0. Links for other releases are OK. > Broken links to archived releases > - > > Key: AMBARI-22511 > URL: https://issues.apache.org/jira/browse/AMBARI-22511 > Project: Ambari > Issue Type: Bug > Components: documentation >Reporter: Sebb >Assignee: Doroszlai, Attila > > The links to releases on the home page are mostly broken. > Once the release is archived, the link should be updated to point to the > archive server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-22511) Broken links to archived releases
[ https://issues.apache.org/jira/browse/AMBARI-22511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila reassigned AMBARI-22511: -- Assignee: Doroszlai, Attila > Broken links to archived releases > - > > Key: AMBARI-22511 > URL: https://issues.apache.org/jira/browse/AMBARI-22511 > Project: Ambari > Issue Type: Bug >Reporter: Sebb >Assignee: Doroszlai, Attila > > The links to releases on the home page are mostly broken. > Once the release is archived, the link should be updated to point to the > archive server. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22514) Schedulable document deletion & archiving for Infra Solr
Krisztian Kasa created AMBARI-22514: --- Summary: Schedulable document deletion & archiving for Infra Solr Key: AMBARI-22514 URL: https://issues.apache.org/jira/browse/AMBARI-22514 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 3.0.0 Reporter: Krisztian Kasa Assignee: Krisztian Kasa Fix For: 3.0.0 If the data size is too big, and the max retention is not good enough, we should delete the latest logs from solr, but of course we need the data itself, so we should archive the data somewhere else (like s3 or hdfs) This feature should also provide support for configurable policies that users can configure in order to determine how long data is held and/or archived. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22507) Ambari UI changes to support Isilon OneFS
[ https://issues.apache.org/jira/browse/AMBARI-22507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-22507: --- Status: Patch Available (was: Open) > Ambari UI changes to support Isilon OneFS > - > > Key: AMBARI-22507 > URL: https://issues.apache.org/jira/browse/AMBARI-22507 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22507) Ambari UI changes to support Isilon OneFS
[ https://issues.apache.org/jira/browse/AMBARI-22507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-22507: --- Attachment: AMBARI-22507.patch > Ambari UI changes to support Isilon OneFS > - > > Key: AMBARI-22507 > URL: https://issues.apache.org/jira/browse/AMBARI-22507 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Attila Magyar >Assignee: Attila Magyar > Fix For: 3.0.0 > > Attachments: AMBARI-22507.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
