[jira] [Commented] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142260#comment-16142260
]
Hudson commented on AMBARI-18574:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7945 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7945/])
AMBARI-18574. Set hbase.hregion.memstore.chunkpool.maxsize to 1.0 (Yao
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e399cb4a9d3169f40eb98c1bd193597ca75f05ba])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/HBASE/configuration/hbase-site.xml
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574_2.patch, AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142248#comment-16142248
]
Hudson commented on AMBARI-18574:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #68 (See
[https://builds.apache.org/job/Ambari-branch-2.6/68/])
AMBARI-18574. Set hbase.hregion.memstore.chunkpool.maxsize to 1.0 (Yao
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7f0e6567c1fcb32dc450f5c91b524d14468e7467])
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/services/HBASE/configuration/hbase-site.xml
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574_2.patch, AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-18574:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.6
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574_2.patch, AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142185#comment-16142185
]
Sumit Mohanty commented on AMBARI-18574:
LGTM, +1 to
https://issues.apache.org/jira/secure/attachment/12883663/AMBARI-18574_2.patch
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574_2.patch, AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21795) Auto fix service config mapping issue discovered during ambari-upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142137#comment-16142137 ] Hudson commented on AMBARI-21795: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7944 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7944/]) AMBARI-21795. Auto fix service config mapping issue discovered during (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ca5fd78778345d74d885cd547c44917cf0feb03f]) * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql > Auto fix service config mapping issue discovered during ambari-upgrade > -- > > Key: AMBARI-21795 > URL: https://issues.apache.org/jira/browse/AMBARI-21795 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21795.patch > > > If user has deleted services, after upgrade db consistency check will throw > warnings about unmapped configs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21795) Auto fix service config mapping issue discovered during ambari-upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21795: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk and branch-2.6 > Auto fix service config mapping issue discovered during ambari-upgrade > -- > > Key: AMBARI-21795 > URL: https://issues.apache.org/jira/browse/AMBARI-21795 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21795.patch > > > If user has deleted services, after upgrade db consistency check will throw > warnings about unmapped configs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21795) Auto fix service config mapping issue discovered during ambari-upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142086#comment-16142086 ] Hudson commented on AMBARI-21795: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #67 (See [https://builds.apache.org/job/Ambari-branch-2.6/67/]) AMBARI-21795. Auto fix service config mapping issue discovered during (vbrodetskyi: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=aff9629ae8e03b4fe635456b6ac332a5afceb6ae]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql > Auto fix service config mapping issue discovered during ambari-upgrade > -- > > Key: AMBARI-21795 > URL: https://issues.apache.org/jira/browse/AMBARI-21795 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21795.patch > > > If user has deleted services, after upgrade db consistency check will throw > warnings about unmapped configs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21822) Implement CodeCache related configuration change for HBase master
Ted Yu created AMBARI-21822: --- Summary: Implement CodeCache related configuration change for HBase master Key: AMBARI-21822 URL: https://issues.apache.org/jira/browse/AMBARI-21822 Project: Ambari Issue Type: Task Reporter: Ted Yu AMBARI-21326 applied the code cache directive to region server daemons. This issue is to apply the same fix to hbase master. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21777) Remove Ambiguous Repository Version When Creating Clusters via Blueprints
[
https://issues.apache.org/jira/browse/AMBARI-21777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141928#comment-16141928
]
Hudson commented on AMBARI-21777:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7943 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7943/])
AMBARI-21777 Remove Ambiguous Repository Version When Creating Clusters
(hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=698293d2d70d19f833e064dcb9c2c1775ce36d50])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterDeployWithStartOnlyTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartOnComponentLevelTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ProvisionClusterRequest.java
> Remove Ambiguous Repository Version When Creating Clusters via Blueprints
> -
>
> Key: AMBARI-21777
> URL: https://issues.apache.org/jira/browse/AMBARI-21777
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21777-2.6.patch, AMBARI-21777.patch
>
>
> When creating a new cluster via a blueprint, we currently use a combination
> of stack and version:
> {code}
> {
> "blueprint" : "foo",
> "repository_version": "2.5.0.0-1237",
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
> We lookup the repository using a query by stack/version. We could instead
> also take a repo ID which removes any ambiguity.
> Something like:
> {code}
> {
> "blueprint" : "foo",
> "repository_id": 1,
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21777) Remove Ambiguous Repository Version When Creating Clusters via Blueprints
[
https://issues.apache.org/jira/browse/AMBARI-21777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141926#comment-16141926
]
Hudson commented on AMBARI-21777:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #66 (See
[https://builds.apache.org/job/Ambari-branch-2.6/66/])
AMBARI-21777 Remove Ambiguous Repository Version When Creating Clusters
(hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3946ff677401e0324f8f632aac412b90ad662d82])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartOnComponentLevelTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterResourceProvider.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ProvisionClusterRequest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterDeployWithStartOnlyTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java
> Remove Ambiguous Repository Version When Creating Clusters via Blueprints
> -
>
> Key: AMBARI-21777
> URL: https://issues.apache.org/jira/browse/AMBARI-21777
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21777-2.6.patch, AMBARI-21777.patch
>
>
> When creating a new cluster via a blueprint, we currently use a combination
> of stack and version:
> {code}
> {
> "blueprint" : "foo",
> "repository_version": "2.5.0.0-1237",
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
> We lookup the repository using a query by stack/version. We could instead
> also take a repo ID which removes any ambiguity.
> Something like:
> {code}
> {
> "blueprint" : "foo",
> "repository_id": 1,
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21618) Admin View - Register Version should correctly display PATCH version
[ https://issues.apache.org/jira/browse/AMBARI-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141870#comment-16141870 ] Hudson commented on AMBARI-21618: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7942 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7942/]) AMBARI-21618 Admin View - Register Version should correctly display (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=eb9cce7e01f3ed3ea910f32bec0a241e56c82c20]) * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsEditCtrl.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/list.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html * (edit) ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js > Admin View - Register Version should correctly display PATCH version > > > Key: AMBARI-21618 > URL: https://issues.apache.org/jira/browse/AMBARI-21618 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21618.patch, register.png > > > # Change dropdown option "Add Version" to "Add Version or Hotfix..." > # List of services should contain only available(affected by patch upgrade) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21615) Add confirmation when installing PATCH version
[ https://issues.apache.org/jira/browse/AMBARI-21615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141869#comment-16141869 ] Hudson commented on AMBARI-21615: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7942 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7942/]) AMBARI-21615 Add confirmation when installing PATCH version. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f59305e387b561f7903b4ec6e1729b300021af54]) * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/messages.js * (edit) ambari-web/app/styles/stack_versions.less * (add) ambari-web/app/templates/common/modal_popups/install_repo_confirmation.hbs > Add confirmation when installing PATCH version > -- > > Key: AMBARI-21615 > URL: https://issues.apache.org/jira/browse/AMBARI-21615 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21615.patch, confirmation.png > > > See screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21777) Remove Ambiguous Repository Version When Creating Clusters via Blueprints
[
https://issues.apache.org/jira/browse/AMBARI-21777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-21777:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
To https://git-wip-us.apache.org/repos/asf/ambari.git
6588679df0..3946ff6774 branch-2.6 -> branch-2.6
eb9cce7e01..698293d2d7 trunk -> trunk
> Remove Ambiguous Repository Version When Creating Clusters via Blueprints
> -
>
> Key: AMBARI-21777
> URL: https://issues.apache.org/jira/browse/AMBARI-21777
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21777-2.6.patch, AMBARI-21777.patch
>
>
> When creating a new cluster via a blueprint, we currently use a combination
> of stack and version:
> {code}
> {
> "blueprint" : "foo",
> "repository_version": "2.5.0.0-1237",
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
> We lookup the repository using a query by stack/version. We could instead
> also take a repo ID which removes any ambiguity.
> Something like:
> {code}
> {
> "blueprint" : "foo",
> "repository_id": 1,
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21777) Remove Ambiguous Repository Version When Creating Clusters via Blueprints
[
https://issues.apache.org/jira/browse/AMBARI-21777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-21777:
-
Attachment: AMBARI-21777.patch
AMBARI-21777-2.6.patch
> Remove Ambiguous Repository Version When Creating Clusters via Blueprints
> -
>
> Key: AMBARI-21777
> URL: https://issues.apache.org/jira/browse/AMBARI-21777
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21777-2.6.patch, AMBARI-21777.patch
>
>
> When creating a new cluster via a blueprint, we currently use a combination
> of stack and version:
> {code}
> {
> "blueprint" : "foo",
> "repository_version": "2.5.0.0-1237",
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
> We lookup the repository using a query by stack/version. We could instead
> also take a repo ID which removes any ambiguity.
> Something like:
> {code}
> {
> "blueprint" : "foo",
> "repository_id": 1,
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21612) PATCH version should be attached right next to the STANDARD
[ https://issues.apache.org/jira/browse/AMBARI-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141830#comment-16141830 ] Hudson commented on AMBARI-21612: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7941 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7941/]) AMBARI-21612 PATCH version should be attached right next to the (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8e64bac3e767f09adbc69526c3552a6f23dcfbfb]) * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/mappers/repository_version_mapper.js * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/models/stack_version/service_simple.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_history_view.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/app/models/stack_version/repository_version.js * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_column.hbs > PATCH version should be attached right next to the STANDARD > --- > > Key: AMBARI-21612 > URL: https://issues.apache.org/jira/browse/AMBARI-21612 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21612.patch, patch > > > See screenshot. > Also, unaffected services should be grayed out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21818) Styling for the Stacks and Versions Page Repo Isn't Centered
[ https://issues.apache.org/jira/browse/AMBARI-21818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141822#comment-16141822 ] Hudson commented on AMBARI-21818: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #65 (See [https://builds.apache.org/job/Ambari-branch-2.6/65/]) AMBARI-21818. Styling for the Stacks and Versions Page Repo Isn't (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6588679df030f6731cc3c286084e89013e92a369]) * (edit) ambari-web/app/styles/stack_versions.less > Styling for the Stacks and Versions Page Repo Isn't Centered > > > Key: AMBARI-21818 > URL: https://issues.apache.org/jira/browse/AMBARI-21818 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21818.patch, Screen Shot 2017-08-24 at 12.18.51 > AM.png > > > When a repo is created with a display name which is slightly longer than the > standard HDP version, the alignment of the green down arrow is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[
https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qin Liu updated AMBARI-21821:
-
Description:
This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
authenticate".
In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
authentication.
2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
{
"metrics": [
{
"metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
"appid": "amssmoketestfake",
"hostname": "host.example.com",
"timestamp": 1503616424000,
"starttime": 1503616424000,
"metrics": {
"1503616424000": 0.164134766408,
"1503616425000": 1503616424000
}
}
]
}
2017-08-24 16:13:44,114 - Connecting (POST) to
amshost.example.com:6188/ws/v1/timeline/metrics/
2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
Authentication required
> Update Ambari Metrics service check to support HTTP SPNEGO authentication
> -
>
> Key: AMBARI-21821
> URL: https://issues.apache.org/jira/browse/AMBARI-21821
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
>Affects Versions: trunk
>Reporter: Qin Liu
>Assignee: Qin Liu
> Fix For: trunk
>
>
> This is a subtask of AMBARI-14384 "Ambari Metrics doesn't use SPNEGO to
> authenticate".
> In a Kerberos enabled cluster with SPNEGO enabled on Hadoop APIs, Ambari
> Metrics Collector web-console will be Kerberos HTTP SPNEGO enabled too. But
> Ambari Metrics service check currently does not support Kerberos HTTP SPNEGO
> authentication.
> 2017-08-24 16:13:44,078 - Ambari Metrics service check was started.
> 2017-08-24 16:13:44,109 - Generated metrics for host amshost.example.com :
> {
> "metrics": [
> {
> "metricname": "AMBARI_METRICS.SmokeTest.FakeMetric",
> "appid": "amssmoketestfake",
> "hostname": "host.example.com",
> "timestamp": 1503616424000,
> "starttime": 1503616424000,
> "metrics": {
> "1503616424000": 0.164134766408,
> "1503616425000": 1503616424000
> }
> }
> ]
> }
> 2017-08-24 16:13:44,114 - Connecting (POST) to
> amshost.example.com:6188/ws/v1/timeline/metrics/
> 2017-08-24 16:13:44,117 - Http response for host amshost.example.com: 401
> Authentication required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21618) Admin View - Register Version should correctly display PATCH version
[ https://issues.apache.org/jira/browse/AMBARI-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141788#comment-16141788 ] Andrii Tkach commented on AMBARI-21618: --- committed to trunk > Admin View - Register Version should correctly display PATCH version > > > Key: AMBARI-21618 > URL: https://issues.apache.org/jira/browse/AMBARI-21618 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21618.patch, register.png > > > # Change dropdown option "Add Version" to "Add Version or Hotfix..." > # List of services should contain only available(affected by patch upgrade) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21615) Add confirmation when installing PATCH version
[ https://issues.apache.org/jira/browse/AMBARI-21615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141781#comment-16141781 ] Andrii Tkach commented on AMBARI-21615: --- committed to trunk > Add confirmation when installing PATCH version > -- > > Key: AMBARI-21615 > URL: https://issues.apache.org/jira/browse/AMBARI-21615 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21615.patch, confirmation.png > > > See screenshot. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21795) Auto fix service config mapping issue discovered during ambari-upgrade
[
https://issues.apache.org/jira/browse/AMBARI-21795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141775#comment-16141775
]
Hadoop QA commented on AMBARI-21795:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883755/AMBARI-21795.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12070//console
This message is automatically generated.
> Auto fix service config mapping issue discovered during ambari-upgrade
> --
>
> Key: AMBARI-21795
> URL: https://issues.apache.org/jira/browse/AMBARI-21795
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21795.patch
>
>
> If user has deleted services, after upgrade db consistency check will throw
> warnings about unmapped configs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[ https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141772#comment-16141772 ] Hudson commented on AMBARI-21819: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #64 (See [https://builds.apache.org/job/Ambari-branch-2.6/64/]) AMBARI-21819 Info icon for services should not show for CURRENT repos. (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ed27e3386fbce28258c10144a6a64d604363a6ae]) * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js > Info icon for services should not show for CURRENT repos > > > Key: AMBARI-21819 > URL: https://issues.apache.org/jira/browse/AMBARI-21819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21819.patch, Screen Shot 2017-08-23 at 9.12.32 > PM.png > > > See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information > about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21612) PATCH version should be attached right next to the STANDARD
[ https://issues.apache.org/jira/browse/AMBARI-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141771#comment-16141771 ] Andrii Tkach commented on AMBARI-21612: --- committed to trunk > PATCH version should be attached right next to the STANDARD > --- > > Key: AMBARI-21612 > URL: https://issues.apache.org/jira/browse/AMBARI-21612 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21612.patch, patch > > > See screenshot. > Also, unaffected services should be grayed out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21795) Auto fix service config mapping issue discovered during ambari-upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21795: --- Attachment: AMBARI-21795.patch > Auto fix service config mapping issue discovered during ambari-upgrade > -- > > Key: AMBARI-21795 > URL: https://issues.apache.org/jira/browse/AMBARI-21795 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21795.patch > > > If user has deleted services, after upgrade db consistency check will throw > warnings about unmapped configs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21781) Error: Repositories for os type redhat-ppc7 are not defined during package installation
[ https://issues.apache.org/jira/browse/AMBARI-21781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141770#comment-16141770 ] Hudson commented on AMBARI-21781: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7940 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7940/]) AMBARI-21781. Error: Repositories for os type redhat-ppc7 are not (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=733c78b9da84d72c847ed54515c99425ac4ca6b6]) * (edit) contrib/version-builder/version_builder.py * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java > Error: Repositories for os type redhat-ppc7 are not defined during package > installation > --- > > Key: AMBARI-21781 > URL: https://issues.apache.org/jira/browse/AMBARI-21781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21781.patch > > > When repos and hosts are reporting PPC as the architecture, hackaround code > was formulating the wrong os_family, and repositories were not being resolved > correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21795) Auto fix service config mapping issue discovered during ambari-upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitaly Brodetskyi updated AMBARI-21795: --- Status: Patch Available (was: Open) > Auto fix service config mapping issue discovered during ambari-upgrade > -- > > Key: AMBARI-21795 > URL: https://issues.apache.org/jira/browse/AMBARI-21795 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vitaly Brodetskyi >Assignee: Vitaly Brodetskyi >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21795.patch > > > If user has deleted services, after upgrade db consistency check will throw > warnings about unmapped configs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[ https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu reassigned AMBARI-21821: Assignee: Qin Liu > Update Ambari Metrics service check to support HTTP SPNEGO authentication > - > > Key: AMBARI-21821 > URL: https://issues.apache.org/jira/browse/AMBARI-21821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[ https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21821: - Component/s: ambari-metrics > Update Ambari Metrics service check to support HTTP SPNEGO authentication > - > > Key: AMBARI-21821 > URL: https://issues.apache.org/jira/browse/AMBARI-21821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Qin Liu >Assignee: Qin Liu > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[ https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21821: - Fix Version/s: trunk > Update Ambari Metrics service check to support HTTP SPNEGO authentication > - > > Key: AMBARI-21821 > URL: https://issues.apache.org/jira/browse/AMBARI-21821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Qin Liu > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[ https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21821: - Affects Version/s: trunk > Update Ambari Metrics service check to support HTTP SPNEGO authentication > - > > Key: AMBARI-21821 > URL: https://issues.apache.org/jira/browse/AMBARI-21821 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Affects Versions: trunk >Reporter: Qin Liu > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21821) Update Ambari Metrics service check to support HTTP SPNEGO authentication
[ https://issues.apache.org/jira/browse/AMBARI-21821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qin Liu updated AMBARI-21821: - Summary: Update Ambari Metrics service check to support HTTP SPNEGO authentication (was: Update Ambari Metrics ) > Update Ambari Metrics service check to support HTTP SPNEGO authentication > - > > Key: AMBARI-21821 > URL: https://issues.apache.org/jira/browse/AMBARI-21821 > Project: Ambari > Issue Type: Bug >Reporter: Qin Liu > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21821) Update Ambari Metrics
Qin Liu created AMBARI-21821: Summary: Update Ambari Metrics Key: AMBARI-21821 URL: https://issues.apache.org/jira/browse/AMBARI-21821 Project: Ambari Issue Type: Bug Reporter: Qin Liu -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21818) Styling for the Stacks and Versions Page Repo Isn't Centered
[ https://issues.apache.org/jira/browse/AMBARI-21818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21818: - Resolution: Fixed Status: Resolved (was: Patch Available) > Styling for the Stacks and Versions Page Repo Isn't Centered > > > Key: AMBARI-21818 > URL: https://issues.apache.org/jira/browse/AMBARI-21818 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21818.patch, Screen Shot 2017-08-24 at 12.18.51 > AM.png > > > When a repo is created with a display name which is slightly longer than the > standard HDP version, the alignment of the green down arrow is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21818) Styling for the Stacks and Versions Page Repo Isn't Centered
[ https://issues.apache.org/jira/browse/AMBARI-21818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141744#comment-16141744 ] Antonenko Alexander commented on AMBARI-21818: -- committed to branch-2.6 > Styling for the Stacks and Versions Page Repo Isn't Centered > > > Key: AMBARI-21818 > URL: https://issues.apache.org/jira/browse/AMBARI-21818 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21818.patch, Screen Shot 2017-08-24 at 12.18.51 > AM.png > > > When a repo is created with a display name which is slightly longer than the > standard HDP version, the alignment of the green down arrow is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21820) Force Regeneration of Cached RCO After Upgrade
Jonathan Hurley created AMBARI-21820: Summary: Force Regeneration of Cached RCO After Upgrade Key: AMBARI-21820 URL: https://issues.apache.org/jira/browse/AMBARI-21820 Project: Ambari Issue Type: Bug Affects Versions: 2.6.0 Reporter: Jonathan Hurley Assignee: Jonathan Hurley Priority: Critical Fix For: 2.6.0 After the stack upgrade has completed, force the RCO to clear and reinitialize. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21757) Allow for keytab regeneration to be filtered for hosts
[ https://issues.apache.org/jira/browse/AMBARI-21757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141716#comment-16141716 ] Hudson commented on AMBARI-21757: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #63 (See [https://builds.apache.org/job/Ambari-branch-2.6/63/]) AMBARI-21757. Allow for keytab regeneration to be filtered for hosts (echekanskiy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=30ad7910090540a13c6ce2abfbddcd01f3ba5ee2]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelperImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/api/resources/ClusterResourceDefinition.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/KerberosHelper.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/KerberosHelperTest.java > Allow for keytab regeneration to be filtered for hosts > -- > > Key: AMBARI-21757 > URL: https://issues.apache.org/jira/browse/AMBARI-21757 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0, 2.6.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0, 2.6.0 > > Attachments: AMBARI-21757-trunk-2.patch, AMBARI-21757-trunk-3.patch, > AMBARI-21757-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21818) Styling for the Stacks and Versions Page Repo Isn't Centered
[
https://issues.apache.org/jira/browse/AMBARI-21818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141712#comment-16141712
]
Hadoop QA commented on AMBARI-21818:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883726/AMBARI-21818.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12069//console
This message is automatically generated.
> Styling for the Stacks and Versions Page Repo Isn't Centered
>
>
> Key: AMBARI-21818
> URL: https://issues.apache.org/jira/browse/AMBARI-21818
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21818.patch, Screen Shot 2017-08-24 at 12.18.51
> AM.png
>
>
> When a repo is created with a display name which is slightly longer than the
> standard HDP version, the alignment of the green down arrow is off.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[ https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141695#comment-16141695 ] Andrii Tkach commented on AMBARI-21819: --- committed to branch-2.6 > Info icon for services should not show for CURRENT repos > > > Key: AMBARI-21819 > URL: https://issues.apache.org/jira/browse/AMBARI-21819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21819.patch, Screen Shot 2017-08-23 at 9.12.32 > PM.png > > > See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information > about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[ https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21819: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Info icon for services should not show for CURRENT repos > > > Key: AMBARI-21819 > URL: https://issues.apache.org/jira/browse/AMBARI-21819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21819.patch, Screen Shot 2017-08-23 at 9.12.32 > PM.png > > > See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information > about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[ https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141690#comment-16141690 ] Aleksandr Kovalenko commented on AMBARI-21819: -- +1 for the patch > Info icon for services should not show for CURRENT repos > > > Key: AMBARI-21819 > URL: https://issues.apache.org/jira/browse/AMBARI-21819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21819.patch, Screen Shot 2017-08-23 at 9.12.32 > PM.png > > > See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information > about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21781) Error: Repositories for os type redhat-ppc7 are not defined during package installation
[ https://issues.apache.org/jira/browse/AMBARI-21781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141674#comment-16141674 ] Hudson commented on AMBARI-21781: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #62 (See [https://builds.apache.org/job/Ambari-branch-2.6/62/]) AMBARI-21781. Error: Repositories for os type redhat-ppc7 are not (ncole: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e16eb8c085d98e3c538316df85c8b8baa904ef3f]) * (edit) contrib/version-builder/version_builder.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java > Error: Repositories for os type redhat-ppc7 are not defined during package > installation > --- > > Key: AMBARI-21781 > URL: https://issues.apache.org/jira/browse/AMBARI-21781 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Blocker > Fix For: 2.5.2 > > Attachments: AMBARI-21781.patch > > > When repos and hosts are reporting PPC as the architecture, hackaround code > was formulating the wrong os_family, and repositories were not being resolved > correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[
https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141658#comment-16141658
]
Hadoop QA commented on AMBARI-21819:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883737/AMBARI-21819.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12068//console
This message is automatically generated.
> Info icon for services should not show for CURRENT repos
>
>
> Key: AMBARI-21819
> URL: https://issues.apache.org/jira/browse/AMBARI-21819
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21819.patch, Screen Shot 2017-08-23 at 9.12.32
> PM.png
>
>
> See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information
> about Storm not being upgraded makes no sense in this context.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21814) On installation of new services on Ambari, Zeppelin should configure new interpreters
[
https://issues.apache.org/jira/browse/AMBARI-21814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141656#comment-16141656
]
Hadoop QA commented on AMBARI-21814:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883700/AMBARI-21814_trunk_v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 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:red}-1 core tests{color}. The test build failed in
[ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12067//artifact/patch-work/testrun_ambari-server.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12067//console
This message is automatically generated.
> On installation of new services on Ambari, Zeppelin should configure new
> interpreters
> -
>
> Key: AMBARI-21814
> URL: https://issues.apache.org/jira/browse/AMBARI-21814
> Project: Ambari
> Issue Type: Bug
> Components: ambari-views
>Reporter: Prabhjyot Singh
>Assignee: Prabhjyot Singh
> Attachments: AMBARI-21814_trunk_v1.patch
>
>
> In current scenario, Ambari doesn't configure any interpreters that are
> installed after installation. For example, if Livy was not present when
> Zeppelin was installed, then Zeppelin's livy interpreter will never get
> configured.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21757) Allow for keytab regeneration to be filtered for hosts
[ https://issues.apache.org/jira/browse/AMBARI-21757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-21757: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Allow for keytab regeneration to be filtered for hosts > -- > > Key: AMBARI-21757 > URL: https://issues.apache.org/jira/browse/AMBARI-21757 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0, 2.6.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0, 2.6.0 > > Attachments: AMBARI-21757-trunk-2.patch, AMBARI-21757-trunk-3.patch, > AMBARI-21757-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21757) Allow for keytab regeneration to be filtered for hosts
[ https://issues.apache.org/jira/browse/AMBARI-21757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-21757: --- Affects Version/s: 2.6.0 > Allow for keytab regeneration to be filtered for hosts > -- > > Key: AMBARI-21757 > URL: https://issues.apache.org/jira/browse/AMBARI-21757 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0, 2.6.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0, 2.6.0 > > Attachments: AMBARI-21757-trunk-2.patch, AMBARI-21757-trunk-3.patch, > AMBARI-21757-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21757) Allow for keytab regeneration to be filtered for hosts
[ https://issues.apache.org/jira/browse/AMBARI-21757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141647#comment-16141647 ] Eugene Chekanskiy commented on AMBARI-21757: e16eb8c..30ad791 branch-2.6 -> branch-2.6 > Allow for keytab regeneration to be filtered for hosts > -- > > Key: AMBARI-21757 > URL: https://issues.apache.org/jira/browse/AMBARI-21757 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0, 2.6.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0, 2.6.0 > > Attachments: AMBARI-21757-trunk-2.patch, AMBARI-21757-trunk-3.patch, > AMBARI-21757-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21757) Allow for keytab regeneration to be filtered for hosts
[ https://issues.apache.org/jira/browse/AMBARI-21757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-21757: --- Fix Version/s: 2.6.0 > Allow for keytab regeneration to be filtered for hosts > -- > > Key: AMBARI-21757 > URL: https://issues.apache.org/jira/browse/AMBARI-21757 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0, 2.6.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0, 2.6.0 > > Attachments: AMBARI-21757-trunk-2.patch, AMBARI-21757-trunk-3.patch, > AMBARI-21757-trunk.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21806) Repository Entities Which Can't Be Removed Should Be Hide-able
[
https://issues.apache.org/jira/browse/AMBARI-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141626#comment-16141626
]
Hudson commented on AMBARI-21806:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7939 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7939/])
AMBARI-21806 - Repository Entities Which Can't Be Removed Should Be (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8b133e499ebf9b1596ac835a1250ff8c4e904b0e])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryVersionEntity.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
> Repository Entities Which Can't Be Removed Should Be Hide-able
> --
>
> Key: AMBARI-21806
> URL: https://issues.apache.org/jira/browse/AMBARI-21806
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21806.patch
>
>
> Many tables have begun referencing {{repo_version}} since a simple
> {{version}} string is no longer sufficient to properly identify a repository.
> However, we allow a {{RepsitoryVersionEntity}} to be removed if it is in the
> following states:
> - {{INIT}}
> - {{INSTALL_FAILED}}
> - {{OUT_OF_SYNC}}
> The issue with removing the entities is that this would also force us to
> remove things like upgrades, service component versions, etc. Here are some
> options:
> # Allow repository versions in {{INIT}} and {{INSTALL_FAILED}} to be removed,
> but for other states we'd need to keep it in the DB for history and perhaps
> add a {{hidden}} column. This would keep the referential integrity.
> # Allow the removal of repository versions, but warn that it will also remove
> things like upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21806) Repository Entities Which Can't Be Removed Should Be Hide-able
[
https://issues.apache.org/jira/browse/AMBARI-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141624#comment-16141624
]
Hudson commented on AMBARI-21806:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #61 (See
[https://builds.apache.org/job/Ambari-branch-2.6/61/])
AMBARI-21806 - Repository Entities Which Can't Be Removed Should Be (jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=952b8cad8c6f20b3cc6547982e952e32fbceba52])
* (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog260Test.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/RepositoryVersionEntity.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
> Repository Entities Which Can't Be Removed Should Be Hide-able
> --
>
> Key: AMBARI-21806
> URL: https://issues.apache.org/jira/browse/AMBARI-21806
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21806.patch
>
>
> Many tables have begun referencing {{repo_version}} since a simple
> {{version}} string is no longer sufficient to properly identify a repository.
> However, we allow a {{RepsitoryVersionEntity}} to be removed if it is in the
> following states:
> - {{INIT}}
> - {{INSTALL_FAILED}}
> - {{OUT_OF_SYNC}}
> The issue with removing the entities is that this would also force us to
> remove things like upgrades, service component versions, etc. Here are some
> options:
> # Allow repository versions in {{INIT}} and {{INSTALL_FAILED}} to be removed,
> but for other states we'd need to keep it in the DB for history and perhaps
> add a {{hidden}} column. This would keep the referential integrity.
> # Allow the removal of repository versions, but warn that it will also remove
> things like upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[ https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21819: -- Status: Patch Available (was: Open) > Info icon for services should not show for CURRENT repos > > > Key: AMBARI-21819 > URL: https://issues.apache.org/jira/browse/AMBARI-21819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21819.patch, Screen Shot 2017-08-23 at 9.12.32 > PM.png > > > See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information > about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[ https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21819: -- Attachment: AMBARI-21819.patch > Info icon for services should not show for CURRENT repos > > > Key: AMBARI-21819 > URL: https://issues.apache.org/jira/browse/AMBARI-21819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21819.patch, Screen Shot 2017-08-23 at 9.12.32 > PM.png > > > See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information > about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21406) Refresh configurations without restarting components
[
https://issues.apache.org/jira/browse/AMBARI-21406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141623#comment-16141623
]
Hadoop QA commented on AMBARI-21406:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883714/AMBARI-21406-v4.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 4 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
org.apache.ambari.server.state.ConfigHelperTest
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12066//console
This message is automatically generated.
> Refresh configurations without restarting components
>
>
> Key: AMBARI-21406
> URL: https://issues.apache.org/jira/browse/AMBARI-21406
> Project: Ambari
> Issue Type: Task
> Components: ambari-agent, ambari-server
>Reporter: Sandor Magyari
>Assignee: Sandor Magyari
> Fix For: 3.0.0
>
> Attachments: AMBARI-21406-v1.patch, AMBARI-21406-v2.patch,
> AMBARI-21406-v3.patch, AMBARI-21406-v4.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[ https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21819: -- Attachment: Screen Shot 2017-08-23 at 9.12.32 PM.png > Info icon for services should not show for CURRENT repos > > > Key: AMBARI-21819 > URL: https://issues.apache.org/jira/browse/AMBARI-21819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: Screen Shot 2017-08-23 at 9.12.32 PM.png > > > See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information > about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[ https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21819: -- Attachment: (was: AMBARI-21819.patch) > Info icon for services should not show for CURRENT repos > > > Key: AMBARI-21819 > URL: https://issues.apache.org/jira/browse/AMBARI-21819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: Screen Shot 2017-08-23 at 9.12.32 PM.png > > > See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information > about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[ https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141620#comment-16141620 ] Andrii Tkach commented on AMBARI-21819: --- 30465 passing (24s) 157 pending > Info icon for services should not show for CURRENT repos > > > Key: AMBARI-21819 > URL: https://issues.apache.org/jira/browse/AMBARI-21819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21819.patch > > > See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information > about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21819) Info icon for services should not show for CURRENT repos
[ https://issues.apache.org/jira/browse/AMBARI-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21819: -- Attachment: AMBARI-21819.patch > Info icon for services should not show for CURRENT repos > > > Key: AMBARI-21819 > URL: https://issues.apache.org/jira/browse/AMBARI-21819 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21819.patch > > > See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information > about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21818) Styling for the Stacks and Versions Page Repo Isn't Centered
[ https://issues.apache.org/jira/browse/AMBARI-21818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21818: Assignee: Antonenko Alexander > Styling for the Stacks and Versions Page Repo Isn't Centered > > > Key: AMBARI-21818 > URL: https://issues.apache.org/jira/browse/AMBARI-21818 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21818.patch, Screen Shot 2017-08-24 at 12.18.51 > AM.png > > > When a repo is created with a display name which is slightly longer than the > standard HDP version, the alignment of the green down arrow is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21818) Styling for the Stacks and Versions Page Repo Isn't Centered
[ https://issues.apache.org/jira/browse/AMBARI-21818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21818: - Status: Patch Available (was: Open) > Styling for the Stacks and Versions Page Repo Isn't Centered > > > Key: AMBARI-21818 > URL: https://issues.apache.org/jira/browse/AMBARI-21818 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21818.patch, Screen Shot 2017-08-24 at 12.18.51 > AM.png > > > When a repo is created with a display name which is slightly longer than the > standard HDP version, the alignment of the green down arrow is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21819) Info icon for services should not show for CURRENT repos
Andrii Tkach created AMBARI-21819: - Summary: Info icon for services should not show for CURRENT repos Key: AMBARI-21819 URL: https://issues.apache.org/jira/browse/AMBARI-21819 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.6.0 See screenshot. 2.6.0.3-8 is marked as CURRENT, therefore the information about Storm not being upgraded makes no sense in this context. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21818) Styling for the Stacks and Versions Page Repo Isn't Centered
[ https://issues.apache.org/jira/browse/AMBARI-21818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21818: - Attachment: AMBARI-21818.patch > Styling for the Stacks and Versions Page Repo Isn't Centered > > > Key: AMBARI-21818 > URL: https://issues.apache.org/jira/browse/AMBARI-21818 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21818.patch, Screen Shot 2017-08-24 at 12.18.51 > AM.png > > > When a repo is created with a display name which is slightly longer than the > standard HDP version, the alignment of the green down arrow is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21818) Styling for the Stacks and Versions Page Repo Isn't Centered
[ https://issues.apache.org/jira/browse/AMBARI-21818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21818: - Attachment: Screen Shot 2017-08-24 at 12.18.51 AM.png > Styling for the Stacks and Versions Page Repo Isn't Centered > > > Key: AMBARI-21818 > URL: https://issues.apache.org/jira/browse/AMBARI-21818 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: Screen Shot 2017-08-24 at 12.18.51 AM.png > > > When a repo is created with a display name which is slightly longer than the > standard HDP version, the alignment of the green down arrow is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21818) Styling for the Stacks and Versions Page Repo Isn't Centered
Antonenko Alexander created AMBARI-21818: Summary: Styling for the Stacks and Versions Page Repo Isn't Centered Key: AMBARI-21818 URL: https://issues.apache.org/jira/browse/AMBARI-21818 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Antonenko Alexander Priority: Critical Fix For: 2.6.0 When a repo is created with a display name which is slightly longer than the standard HDP version, the alignment of the green down arrow is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21815) Repository Version Listing Has Alignment Problems if Display Name is Too Long
[ https://issues.apache.org/jira/browse/AMBARI-21815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141582#comment-16141582 ] Hudson commented on AMBARI-21815: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #60 (See [https://builds.apache.org/job/Ambari-branch-2.6/60/]) AMBARI-21815 Repository Version Listing Has Alignment Problems if (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f9f6de1425958e7242d926f998bcec6c7b94d37e]) * (edit) ambari-web/app/styles/stack_versions.less > Repository Version Listing Has Alignment Problems if Display Name is Too Long > - > > Key: AMBARI-21815 > URL: https://issues.apache.org/jira/browse/AMBARI-21815 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21815.patch, Screen Shot 2017-08-24 at 11.16.03 > AM.png > > > When there are several repository versions defined and the display name of > one repository is longer than the others, then the alignment of the service > versions is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21806) Repository Entities Which Can't Be Removed Should Be Hide-able
[
https://issues.apache.org/jira/browse/AMBARI-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-21806:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Repository Entities Which Can't Be Removed Should Be Hide-able
> --
>
> Key: AMBARI-21806
> URL: https://issues.apache.org/jira/browse/AMBARI-21806
> Project: Ambari
> Issue Type: Task
>Affects Versions: 2.6.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21806.patch
>
>
> Many tables have begun referencing {{repo_version}} since a simple
> {{version}} string is no longer sufficient to properly identify a repository.
> However, we allow a {{RepsitoryVersionEntity}} to be removed if it is in the
> following states:
> - {{INIT}}
> - {{INSTALL_FAILED}}
> - {{OUT_OF_SYNC}}
> The issue with removing the entities is that this would also force us to
> remove things like upgrades, service component versions, etc. Here are some
> options:
> # Allow repository versions in {{INIT}} and {{INSTALL_FAILED}} to be removed,
> but for other states we'd need to keep it in the DB for history and perhaps
> add a {{hidden}} column. This would keep the referential integrity.
> # Allow the removal of repository versions, but warn that it will also remove
> things like upgrades.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21817) Icon for Revert should not be a trash can
[ https://issues.apache.org/jira/browse/AMBARI-21817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21817: - Resolution: Fixed Status: Resolved (was: Patch Available) > Icon for Revert should not be a trash can > - > > Key: AMBARI-21817 > URL: https://issues.apache.org/jira/browse/AMBARI-21817 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21817.patch, Screen Shot 2017-08-23 at 5.11.06 > PM.png > > > See screenshot. A trash can implies you're deleting it, which isn't quite > true. Can we use some kind of arrow from font-awesome instead? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21817) Icon for Revert should not be a trash can
[ https://issues.apache.org/jira/browse/AMBARI-21817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141557#comment-16141557 ] Antonenko Alexander commented on AMBARI-21817: -- committed to branch-2.6 > Icon for Revert should not be a trash can > - > > Key: AMBARI-21817 > URL: https://issues.apache.org/jira/browse/AMBARI-21817 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21817.patch, Screen Shot 2017-08-23 at 5.11.06 > PM.png > > > See screenshot. A trash can implies you're deleting it, which isn't quite > true. Can we use some kind of arrow from font-awesome instead? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21817) Icon for Revert should not be a trash can
[ https://issues.apache.org/jira/browse/AMBARI-21817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141551#comment-16141551 ] Andrii Tkach commented on AMBARI-21817: --- +1 for the patch > Icon for Revert should not be a trash can > - > > Key: AMBARI-21817 > URL: https://issues.apache.org/jira/browse/AMBARI-21817 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21817.patch, Screen Shot 2017-08-23 at 5.11.06 > PM.png > > > See screenshot. A trash can implies you're deleting it, which isn't quite > true. Can we use some kind of arrow from font-awesome instead? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21817) Icon for Revert should not be a trash can
[ https://issues.apache.org/jira/browse/AMBARI-21817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21817: - Attachment: AMBARI-21817.patch > Icon for Revert should not be a trash can > - > > Key: AMBARI-21817 > URL: https://issues.apache.org/jira/browse/AMBARI-21817 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21817.patch, Screen Shot 2017-08-23 at 5.11.06 > PM.png > > > See screenshot. A trash can implies you're deleting it, which isn't quite > true. Can we use some kind of arrow from font-awesome instead? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21817) Icon for Revert should not be a trash can
[ https://issues.apache.org/jira/browse/AMBARI-21817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21817: - Affects Version/s: 2.6.0 Status: Patch Available (was: Open) > Icon for Revert should not be a trash can > - > > Key: AMBARI-21817 > URL: https://issues.apache.org/jira/browse/AMBARI-21817 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21817.patch, Screen Shot 2017-08-23 at 5.11.06 > PM.png > > > See screenshot. A trash can implies you're deleting it, which isn't quite > true. Can we use some kind of arrow from font-awesome instead? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21817) Icon for Revert should not be a trash can
[ https://issues.apache.org/jira/browse/AMBARI-21817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reassigned AMBARI-21817: Assignee: Antonenko Alexander > Icon for Revert should not be a trash can > - > > Key: AMBARI-21817 > URL: https://issues.apache.org/jira/browse/AMBARI-21817 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: Screen Shot 2017-08-23 at 5.11.06 PM.png > > > See screenshot. A trash can implies you're deleting it, which isn't quite > true. Can we use some kind of arrow from font-awesome instead? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21817) Icon for Revert should not be a trash can
[ https://issues.apache.org/jira/browse/AMBARI-21817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21817: - Attachment: Screen Shot 2017-08-23 at 5.11.06 PM.png > Icon for Revert should not be a trash can > - > > Key: AMBARI-21817 > URL: https://issues.apache.org/jira/browse/AMBARI-21817 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: Screen Shot 2017-08-23 at 5.11.06 PM.png > > > See screenshot. A trash can implies you're deleting it, which isn't quite > true. Can we use some kind of arrow from font-awesome instead? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21815) Repository Version Listing Has Alignment Problems if Display Name is Too Long
[ https://issues.apache.org/jira/browse/AMBARI-21815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21815: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Repository Version Listing Has Alignment Problems if Display Name is Too Long > - > > Key: AMBARI-21815 > URL: https://issues.apache.org/jira/browse/AMBARI-21815 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21815.patch, Screen Shot 2017-08-24 at 11.16.03 > AM.png > > > When there are several repository versions defined and the display name of > one repository is longer than the others, then the alignment of the service > versions is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21815) Repository Version Listing Has Alignment Problems if Display Name is Too Long
[ https://issues.apache.org/jira/browse/AMBARI-21815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141542#comment-16141542 ] Andrii Tkach commented on AMBARI-21815: --- committed to branch-2.6 > Repository Version Listing Has Alignment Problems if Display Name is Too Long > - > > Key: AMBARI-21815 > URL: https://issues.apache.org/jira/browse/AMBARI-21815 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21815.patch, Screen Shot 2017-08-24 at 11.16.03 > AM.png > > > When there are several repository versions defined and the display name of > one repository is longer than the others, then the alignment of the service > versions is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21817) Icon for Revert should not be a trash can
Antonenko Alexander created AMBARI-21817: Summary: Icon for Revert should not be a trash can Key: AMBARI-21817 URL: https://issues.apache.org/jira/browse/AMBARI-21817 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Antonenko Alexander Fix For: 2.6.0 See screenshot. A trash can implies you're deleting it, which isn't quite true. Can we use some kind of arrow from font-awesome instead? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21406) Refresh configurations without restarting components
[ https://issues.apache.org/jira/browse/AMBARI-21406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandor Magyari updated AMBARI-21406: Attachment: AMBARI-21406-v4.patch > Refresh configurations without restarting components > > > Key: AMBARI-21406 > URL: https://issues.apache.org/jira/browse/AMBARI-21406 > Project: Ambari > Issue Type: Task > Components: ambari-agent, ambari-server >Reporter: Sandor Magyari >Assignee: Sandor Magyari > Fix For: 3.0.0 > > Attachments: AMBARI-21406-v1.patch, AMBARI-21406-v2.patch, > AMBARI-21406-v3.patch, AMBARI-21406-v4.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21815) Repository Version Listing Has Alignment Problems if Display Name is Too Long
[
https://issues.apache.org/jira/browse/AMBARI-21815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141531#comment-16141531
]
Hadoop QA commented on AMBARI-21815:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883711/AMBARI-21815.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12065//console
This message is automatically generated.
> Repository Version Listing Has Alignment Problems if Display Name is Too Long
> -
>
> Key: AMBARI-21815
> URL: https://issues.apache.org/jira/browse/AMBARI-21815
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
> Fix For: 2.6.0
>
> Attachments: AMBARI-21815.patch, Screen Shot 2017-08-24 at 11.16.03
> AM.png
>
>
> When there are several repository versions defined and the display name of
> one repository is longer than the others, then the alignment of the service
> versions is off.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21816) test_kms_server timing issue
Doroszlai, Attila created AMBARI-21816:
--
Summary: test_kms_server timing issue
Key: AMBARI-21816
URL: https://issues.apache.org/jira/browse/AMBARI-21816
Project: Ambari
Issue Type: Bug
Components: ambari-server
Reporter: Doroszlai, Attila
Priority: Minor
Fix For: 3.0.0, 2.6.0
Python unit test in {{test_kms_server}} occasionally fails due to timing.
Expected and actual output use two separate calls to get current time, which
may be different if happens to be executed around the turn of a second.
{noformat}
FAIL: test_start_secured (test_kms_server.TestRangerKMS)
--
Traceback (most recent call last):
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py",
line 522, in test_start_secured
mode = 0644
File
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 330, in assertResourceCalled
self.assertEquals(kwargs, resource.arguments)
AssertionError: {'owner': 'kms', 'content': '\n2017-08-25
11:02:46\n< [truncated]... != {'content':
'\n2017-08-25 11:02:45\n', 'owne
[truncated]...
- {'content': '\n2017-08-25 11:02:46\n',
? ^
+ {'content': '\n2017-08-25 11:02:45\n',
? ^
- 'group': 'kms',
+ 'group': u'kms',
? +
'mode': 420,
- 'owner': 'kms'}
+ 'owner': u'kms'}
? +
{noformat}
Affected code: {{test_start_default}} and {{test_start_secured}} in
{{ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21815) Repository Version Listing Has Alignment Problems if Display Name is Too Long
[ https://issues.apache.org/jira/browse/AMBARI-21815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141514#comment-16141514 ] Aleksandr Kovalenko commented on AMBARI-21815: -- +1 for the patch > Repository Version Listing Has Alignment Problems if Display Name is Too Long > - > > Key: AMBARI-21815 > URL: https://issues.apache.org/jira/browse/AMBARI-21815 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21815.patch, Screen Shot 2017-08-24 at 11.16.03 > AM.png > > > When there are several repository versions defined and the display name of > one repository is longer than the others, then the alignment of the service > versions is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21815) Repository Version Listing Has Alignment Problems if Display Name is Too Long
[ https://issues.apache.org/jira/browse/AMBARI-21815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21815: -- Attachment: AMBARI-21815.patch > Repository Version Listing Has Alignment Problems if Display Name is Too Long > - > > Key: AMBARI-21815 > URL: https://issues.apache.org/jira/browse/AMBARI-21815 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21815.patch, Screen Shot 2017-08-24 at 11.16.03 > AM.png > > > When there are several repository versions defined and the display name of > one repository is longer than the others, then the alignment of the service > versions is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21815) Repository Version Listing Has Alignment Problems if Display Name is Too Long
[ https://issues.apache.org/jira/browse/AMBARI-21815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141513#comment-16141513 ] Andrii Tkach commented on AMBARI-21815: --- 30465 passing (26s) 157 pending > Repository Version Listing Has Alignment Problems if Display Name is Too Long > - > > Key: AMBARI-21815 > URL: https://issues.apache.org/jira/browse/AMBARI-21815 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21815.patch, Screen Shot 2017-08-24 at 11.16.03 > AM.png > > > When there are several repository versions defined and the display name of > one repository is longer than the others, then the alignment of the service > versions is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21815) Repository Version Listing Has Alignment Problems if Display Name is Too Long
[ https://issues.apache.org/jira/browse/AMBARI-21815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21815: -- Status: Patch Available (was: Open) > Repository Version Listing Has Alignment Problems if Display Name is Too Long > - > > Key: AMBARI-21815 > URL: https://issues.apache.org/jira/browse/AMBARI-21815 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: AMBARI-21815.patch, Screen Shot 2017-08-24 at 11.16.03 > AM.png > > > When there are several repository versions defined and the display name of > one repository is longer than the others, then the alignment of the service > versions is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141375#comment-16141375
]
Yao Lei edited comment on AMBARI-18574 at 8/25/17 11:41 AM:
Hi [~sumitmohanty] ,
Thanks for your review. Please see updated patch [^AMBARI-18574_2.patch] .
hbase.hregion.memstore.chunkpool.maxsize will be added as part of a stack
upgrade to HDP 2.6.
Tested in a real cluster. It works.
was (Author: yaolei):
Hi [~sumitmohanty] ,
Thanks for your review. Please see updated patch [^AMBARI-18574_2.patch] .
hbase.hregion.memstore.chunkpool.maxsize will be added as part of a upgrade to
stack HDP 2.6.
Tested in a real cluster. It works.
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574_2.patch, AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21815) Repository Version Listing Has Alignment Problems if Display Name is Too Long
[ https://issues.apache.org/jira/browse/AMBARI-21815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21815: -- Attachment: Screen Shot 2017-08-24 at 11.16.03 AM.png > Repository Version Listing Has Alignment Problems if Display Name is Too Long > - > > Key: AMBARI-21815 > URL: https://issues.apache.org/jira/browse/AMBARI-21815 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.6.0 > > Attachments: Screen Shot 2017-08-24 at 11.16.03 AM.png > > > When there are several repository versions defined and the display name of > one repository is longer than the others, then the alignment of the service > versions is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21815) Repository Version Listing Has Alignment Problems if Display Name is Too Long
Andrii Tkach created AMBARI-21815: - Summary: Repository Version Listing Has Alignment Problems if Display Name is Too Long Key: AMBARI-21815 URL: https://issues.apache.org/jira/browse/AMBARI-21815 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.6.0 When there are several repository versions defined and the display name of one repository is longer than the others, then the alignment of the service versions is off. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21813) Finalize for MAINT upgrade should not mention revert
[ https://issues.apache.org/jira/browse/AMBARI-21813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141508#comment-16141508 ] Hudson commented on AMBARI-21813: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #59 (See [https://builds.apache.org/job/Ambari-branch-2.6/59/]) AMBARI-21813 Finalize for MAINT upgrade should not mention revert. (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0d529b9f24dac14fa948e5077f072d6912c0ef84]) * (edit) ambari-web/test/controllers/main/service/reassign/step1_controller_test.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_wizard_view.js > Finalize for MAINT upgrade should not mention revert > > > Key: AMBARI-21813 > URL: https://issues.apache.org/jira/browse/AMBARI-21813 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21813.patch, Screen Shot 2017-08-23 at 5.33.38 > PM.png, Screen Shot 2017-08-23 at 5.34.33 PM.png > > > There are two issues: > * Finalize screen for MAINT should not indicate that a revert is possible. > * After completing Finalize, we should not allow Revert of MAINT (only > patches can revert). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21804) Add configurable management endpoints to Log Search
[ https://issues.apache.org/jira/browse/AMBARI-21804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141489#comment-16141489 ] Hudson commented on AMBARI-21804: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7938 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7938/]) AMBARI-21804. Add configurable management endpoints to Log Search (oleewere: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f7d10f437535aebcef05cbbbe458fb7e8264ade5]) * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/ApplicationConfig.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/health/SolrAuditLogsHealthIndicator.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/doc/DocConstants.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/health/SolrEventHistoryHealthIndicator.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/rest/InfoResource.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/resources/info.properties * (edit) ambari-logsearch/ambari-logsearch-server/pom.xml * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/manager/InfoManager.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SecurityConfig.java * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/health/AbstractSolrHealthIndicator.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/resources/default.properties * (add) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/health/SolrServiceLogsHealthIndicator.java > Add configurable management endpoints to Log Search > --- > > Key: AMBARI-21804 > URL: https://issues.apache.org/jira/browse/AMBARI-21804 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141486#comment-16141486
]
Hadoop QA commented on AMBARI-18574:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883663/AMBARI-18574_2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 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-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12064//console
This message is automatically generated.
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Yao Lei
> Fix For: 2.6.0
>
> Attachments: AMBARI-18574_2.patch, AMBARI-18574.patch
>
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21813) Finalize for MAINT upgrade should not mention revert
[ https://issues.apache.org/jira/browse/AMBARI-21813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141481#comment-16141481 ] Andrii Tkach commented on AMBARI-21813: --- committed to branch-2.6 > Finalize for MAINT upgrade should not mention revert > > > Key: AMBARI-21813 > URL: https://issues.apache.org/jira/browse/AMBARI-21813 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21813.patch, Screen Shot 2017-08-23 at 5.33.38 > PM.png, Screen Shot 2017-08-23 at 5.34.33 PM.png > > > There are two issues: > * Finalize screen for MAINT should not indicate that a revert is possible. > * After completing Finalize, we should not allow Revert of MAINT (only > patches can revert). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21813) Finalize for MAINT upgrade should not mention revert
[ https://issues.apache.org/jira/browse/AMBARI-21813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21813: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Finalize for MAINT upgrade should not mention revert > > > Key: AMBARI-21813 > URL: https://issues.apache.org/jira/browse/AMBARI-21813 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21813.patch, Screen Shot 2017-08-23 at 5.33.38 > PM.png, Screen Shot 2017-08-23 at 5.34.33 PM.png > > > There are two issues: > * Finalize screen for MAINT should not indicate that a revert is possible. > * After completing Finalize, we should not allow Revert of MAINT (only > patches can revert). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21813) Finalize for MAINT upgrade should not mention revert
[ https://issues.apache.org/jira/browse/AMBARI-21813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141474#comment-16141474 ] Aleksandr Kovalenko commented on AMBARI-21813: -- +1 for the patch > Finalize for MAINT upgrade should not mention revert > > > Key: AMBARI-21813 > URL: https://issues.apache.org/jira/browse/AMBARI-21813 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21813.patch, Screen Shot 2017-08-23 at 5.33.38 > PM.png, Screen Shot 2017-08-23 at 5.34.33 PM.png > > > There are two issues: > * Finalize screen for MAINT should not indicate that a revert is possible. > * After completing Finalize, we should not allow Revert of MAINT (only > patches can revert). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21814) On installation of new services on Ambari, Zeppelin should configure new interpreters
[ https://issues.apache.org/jira/browse/AMBARI-21814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21814: - Attachment: AMBARI-21814_trunk_v1.patch > On installation of new services on Ambari, Zeppelin should configure new > interpreters > - > > Key: AMBARI-21814 > URL: https://issues.apache.org/jira/browse/AMBARI-21814 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-21814_trunk_v1.patch > > > In current scenario, Ambari doesn't configure any interpreters that are > installed after installation. For example, if Livy was not present when > Zeppelin was installed, then Zeppelin's livy interpreter will never get > configured. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21814) On installation of new services on Ambari, Zeppelin should configure new interpreters
[ https://issues.apache.org/jira/browse/AMBARI-21814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21814: - Status: Patch Available (was: Open) > On installation of new services on Ambari, Zeppelin should configure new > interpreters > - > > Key: AMBARI-21814 > URL: https://issues.apache.org/jira/browse/AMBARI-21814 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > > In current scenario, Ambari doesn't configure any interpreters that are > installed after installation. For example, if Livy was not present when > Zeppelin was installed, then Zeppelin's livy interpreter will never get > configured. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21814) On installation of new services on Ambari, Zeppelin should configure new interpreters
Prabhjyot Singh created AMBARI-21814: Summary: On installation of new services on Ambari, Zeppelin should configure new interpreters Key: AMBARI-21814 URL: https://issues.apache.org/jira/browse/AMBARI-21814 Project: Ambari Issue Type: Bug Components: ambari-views Reporter: Prabhjyot Singh Assignee: Prabhjyot Singh In current scenario, Ambari doesn't configure any interpreters that are installed after installation. For example, if Livy was not present when Zeppelin was installed, then Zeppelin's livy interpreter will never get configured. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21813) Finalize for MAINT upgrade should not mention revert
[
https://issues.apache.org/jira/browse/AMBARI-21813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141467#comment-16141467
]
Hadoop QA commented on AMBARI-21813:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883699/AMBARI-21813.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12063//console
This message is automatically generated.
> Finalize for MAINT upgrade should not mention revert
>
>
> Key: AMBARI-21813
> URL: https://issues.apache.org/jira/browse/AMBARI-21813
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21813.patch, Screen Shot 2017-08-23 at 5.33.38
> PM.png, Screen Shot 2017-08-23 at 5.34.33 PM.png
>
>
> There are two issues:
> * Finalize screen for MAINT should not indicate that a revert is possible.
> * After completing Finalize, we should not allow Revert of MAINT (only
> patches can revert).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-21804) Add configurable management endpoints to Log Search
[
https://issues.apache.org/jira/browse/AMBARI-21804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó resolved AMBARI-21804.
---
Resolution: Fixed
committed to trunk:
{code:java}
commit f7d10f437535aebcef05cbbbe458fb7e8264ade5
Author: oleewere
Date: Wed Aug 23 18:12:11 2017 +0200
AMBARI-21804. Add configurable management endpoints to Log Search (oleewere)
{code}
> Add configurable management endpoints to Log Search
> ---
>
> Key: AMBARI-21804
> URL: https://issues.apache.org/jira/browse/AMBARI-21804
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 3.0.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21813) Finalize for MAINT upgrade should not mention revert
[ https://issues.apache.org/jira/browse/AMBARI-21813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141454#comment-16141454 ] Andrii Tkach commented on AMBARI-21813: --- 30465 passing (26s) 157 pending > Finalize for MAINT upgrade should not mention revert > > > Key: AMBARI-21813 > URL: https://issues.apache.org/jira/browse/AMBARI-21813 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21813.patch, Screen Shot 2017-08-23 at 5.33.38 > PM.png, Screen Shot 2017-08-23 at 5.34.33 PM.png > > > There are two issues: > * Finalize screen for MAINT should not indicate that a revert is possible. > * After completing Finalize, we should not allow Revert of MAINT (only > patches can revert). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21813) Finalize for MAINT upgrade should not mention revert
[ https://issues.apache.org/jira/browse/AMBARI-21813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21813: -- Status: Patch Available (was: Open) > Finalize for MAINT upgrade should not mention revert > > > Key: AMBARI-21813 > URL: https://issues.apache.org/jira/browse/AMBARI-21813 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21813.patch, Screen Shot 2017-08-23 at 5.33.38 > PM.png, Screen Shot 2017-08-23 at 5.34.33 PM.png > > > There are two issues: > * Finalize screen for MAINT should not indicate that a revert is possible. > * After completing Finalize, we should not allow Revert of MAINT (only > patches can revert). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21813) Finalize for MAINT upgrade should not mention revert
[ https://issues.apache.org/jira/browse/AMBARI-21813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21813: -- Attachment: AMBARI-21813.patch > Finalize for MAINT upgrade should not mention revert > > > Key: AMBARI-21813 > URL: https://issues.apache.org/jira/browse/AMBARI-21813 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21813.patch, Screen Shot 2017-08-23 at 5.33.38 > PM.png, Screen Shot 2017-08-23 at 5.34.33 PM.png > > > There are two issues: > * Finalize screen for MAINT should not indicate that a revert is possible. > * After completing Finalize, we should not allow Revert of MAINT (only > patches can revert). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21813) Finalize for MAINT upgrade should not mention revert
[ https://issues.apache.org/jira/browse/AMBARI-21813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-21813: -- Attachment: Screen Shot 2017-08-23 at 5.34.33 PM.png Screen Shot 2017-08-23 at 5.33.38 PM.png > Finalize for MAINT upgrade should not mention revert > > > Key: AMBARI-21813 > URL: https://issues.apache.org/jira/browse/AMBARI-21813 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.6.0 > > Attachments: Screen Shot 2017-08-23 at 5.33.38 PM.png, Screen Shot > 2017-08-23 at 5.34.33 PM.png > > > There are two issues: > * Finalize screen for MAINT should not indicate that a revert is possible. > * After completing Finalize, we should not allow Revert of MAINT (only > patches can revert). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21813) Finalize for MAINT upgrade should not mention revert
Andrii Tkach created AMBARI-21813: - Summary: Finalize for MAINT upgrade should not mention revert Key: AMBARI-21813 URL: https://issues.apache.org/jira/browse/AMBARI-21813 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Priority: Critical Fix For: 2.6.0 There are two issues: * Finalize screen for MAINT should not indicate that a revert is possible. * After completing Finalize, we should not allow Revert of MAINT (only patches can revert). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21812) Installing mpack with .tgz extension fails with global name 'path' is not defined
[
https://issues.apache.org/jira/browse/AMBARI-21812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-21812:
---
Summary: Installing mpack with .tgz extension fails with global name 'path'
is not defined (was: installing mpack with .tgz extension fails with global
name 'path' is not defined)
> Installing mpack with .tgz extension fails with global name 'path' is not
> defined
> -
>
> Key: AMBARI-21812
> URL: https://issues.apache.org/jira/browse/AMBARI-21812
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
> Fix For: 3.0.0
>
>
> Running:
> {code}
> ambari-server install-mpack --mpack=/path/to/mympack.tgz --verbose
> {code}
> Fails with:
> {code}
> Traceback (most recent call last):
> File "/usr/sbin/ambari-server.py", line 754, in
> mainBody()
> File "/usr/sbin/ambari-server.py", line 725, in mainBody
> main(options, args, parser)
> File "/usr/sbin/ambari-server.py", line 678, in main
> action_obj.execute()
> File "/usr/sbin/ambari-server.py", line 69, in execute
> self.fn(*self.args, **self.kwargs)
> File "/usr/lib/python2.6/site-packages/ambari_server/setupMpacks.py", line
> 764, in install_mpack
> (mpack_metadata, mpack_name, mpack_version, mpack_staging_dir,
> mpack_archive_path) = _install_mpack(options, replay_mode)
> File "/usr/lib/python2.6/site-packages/ambari_server/setupMpacks.py", line
> 620, in _install_mpack
> tmp_root_dir = expand_mpack(tmp_archive_path)
> File "/usr/lib/python2.6/site-packages/ambari_server/setupMpacks.py", line
> 139, in expand_mpack
> archive_root_dir = get_archive_root_dir(archive_path)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/tar_archive.py",
> line 70, in get_archive_root_dir
> if archive.endswith('.tar.gz') or path.endswith('.tgz'):
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
